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

Metadata structures and support #133

Closed
chris-little opened this issue Oct 8, 2020 · 3 comments
Closed

Metadata structures and support #133

chris-little opened this issue Oct 8, 2020 · 3 comments

Comments

@chris-little
Copy link
Contributor

What metadata needs to be identified beyond tht required by OGC API-Common Parts Core and Collections? Such as identified in
API-Records Issue 42

@chris-little
Copy link
Contributor Author

My first take on what we should consider from API-Records Core:
Properties:

Queryable Requirement Description
title M A human-readable name given to the resource.
description M A free-text description of the resource.
keywords M A list of keywords or tags describing the resource.
type M The nature or genre of the resource.
formats O A list of available distribution formats for the resource.
extent O The spatio-temporal coverage of the resource.

Query parameters:

Query Parameter Description
bbox A bounding box. If the spatial extent of the record intersects the specified bounding box then the record shall be presented in the response document.
datetime A time instance or time period. If the temporal extent of the record intersects the specified data/time value then the record shall be presented in the response document.
type A resource type. Only records of the specified type shall be presented in the response document.
q A space-separated list of search terms. If any server-chosen text field in the record contains 1 or more of the terms listed then this records hall appear in the response set.

@dblodgett-usgs
Copy link
Contributor

Is this documentation or future work?

@chris-little
Copy link
Contributor Author

Agreed to close at meeting 35. This is future work, including alignment with OGC API Records and other APIs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants