Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Make horizontal accuracy 'required' for geospatial data #78

Closed
billgeo opened this issue Sep 30, 2021 · 4 comments
Closed
Labels
enhancement New feature or request

Comments

@billgeo
Copy link
Contributor

billgeo commented Sep 30, 2021

Is your feature request related to a problem? Please describe.
Horizontal accuracy should be mandatory for all collections where there is geospatial data.

Options to determine if data is Geospatial:

  1. Use some other STAC metadata, i.e linz:geospatial_type or the spatial object?
  2. Scan the data to determine if it has a geospatial element

Describe the solution you'd like
Add the two horizontal accuracy fields to this (+ some tests).

"required": ["quality:lineage"],

Describe alternatives you've considered
Part of LINZ metadata review decisions

@billgeo billgeo added the enhancement New feature or request label Sep 30, 2021
@billgeo
Copy link
Contributor Author

billgeo commented Sep 30, 2021

Creasted draft PR here #77

@billgeo
Copy link
Contributor Author

billgeo commented Oct 5, 2021

Check if this makes sense for all datasets.

@billgeo
Copy link
Contributor Author

billgeo commented Oct 6, 2021

Have clarified that this should only be mandsatory for 'geospatial' datasets, so it would have to be conditional on some other metadata, perhaps the linz 'geospatial_type' field, or else detected from the dataset itself. Either of those would require some significant development, so we've decide to leave it optional for now and will review later.

@billgeo billgeo changed the title Feature request: Make horizontal accuracy 'required' Feature request: Make horizontal accuracy 'required' for geospatial data Oct 6, 2021
@billgeo
Copy link
Contributor Author

billgeo commented Jun 7, 2022

Duplicate of #100 . Closing.

@billgeo billgeo closed this as completed Jun 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant