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

resolve extents to OGC API - Common, Collections, make optional #84

Merged
merged 7 commits into from
Feb 11, 2021

Conversation

tomkralidis
Copy link
Contributor

Updated extents schema reference. I also made extents optional, seeing that the extents schema itself has no required properties, which may end up allowing things like:

extents:

...just so documents can pass schema validation without added value?

@cportele
Copy link
Member

cportele commented Feb 5, 2021

+1 to making extent optional. If there is no extent there is no point in having an empty object.

@tomkralidis
Copy link
Contributor Author

tomkralidis commented Feb 9, 2021

UPDATE 2021-02-08: since rebasing from @pvretano 's recent updates, this PR now updates the record model and example per #70, and adds a feature collection schema for Records responses.

@pvretano pvretano merged commit 338e959 into opengeospatial:master Feb 11, 2021
@tomkralidis tomkralidis deleted the record-schema branch February 11, 2021 15:23
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

Successfully merging this pull request may close these issues.

3 participants