IQSS / IQSS/dataverse

Geographic Metadata Extents - order displayed

Open
#7,878 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature: Geospatial Type: Suggestion User Role: Depositor
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

I've been adding extents to the geographic metadata. I just realized that the ESRI convention (also used in QGIS) is to list extents: top, bottom, left, right. (example here: https://desktop.arcgis.com/en/arcmap/10.3/map/page-layouts/customizing-your-map-extent.htm) Dataverse geographic metadata lists: West, East, North and South Latitudes, which are not labeled after the metadata is saved. Saved looks like this:
Geographic Bounding Box | -1969770.9130000006407499 -116606.7336999997496605 -2045789.3686999995261431 -178888.8761999998241663
You have to click on the '?' to know what order the extents are in.

In QGIS the same extent display is: -2045789.3686999995261431,-178888.8761999998241663 : -1969770.9130000006407499,-116606.7336999997496605

Without labels I think this could lead to some confusion. I could complain to ESRI but I think the extent order they use could be considered convention.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not identify a file, test, or entry point. Start by locating the geographic metadata display and reviewing how the saved bounding-box values are ordered; done means the displayed extents are labeled or follow a clearly documented convention, with coverage for the resulting presentation.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.