IQSS / IQSS/dataverse

Link bounding boxes to geographic coverage

Open
#7,455 10 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Feature Request Summary

Users as well as indexes such as the Canadian[ Geodisy]((https://geo.frdr-dfdr.ca/) would benefit from having DV link bounding box metadata to geographic coverage metadata. Both fields are repeatable but there is no relationship between the them. This means that datasets with multiple boxes or coverage fields risk having unlinked and potentially messy geo metadata. Being able to link place names to a corresponding bounding box would add context to the user and enable further geospatial discovery down the line.

As an example, see this dataset. https://doi.org/10.5683/SP2/4E6LGS. The dataset features 30+ unique locations. Presently, if we were to add bounding boxes for each location, there would be no association to the free-text geographic coverage metadata fields. We would get only a long list of bounding boxes, And one list would not have the context that the other could provide. As a stopgap, we instead created one massive bounding box that covers all the place names, but that doesn't reflect the data well.

It would be great if we could associate a unique bounding box with each of these unique locations rather than using 1 large bounding box that covers all, as the vast space between the unique locations has almost no bearing on the data collections at the locations themselves.

Thanks,

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 names no implementation files, tests, or entry points. Start by tracing how Dataverse currently represents bounding-box and geographic-coverage metadata, using the linked example dataset to clarify the required association. Done should include an agreed relationship model and coverage for datasets with multiple locations.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.