We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://github.com/stac-utils/stac-geoparquet/blob/main/spec/stac-geoparquet-spec.md#including-a-stac-collection-json-in-a-stac-geoparquet-collection
I think we'd support this on the way in either by:
Way out would be similar-ish, where if we didn't do it on an item collection we'd just hit the parquet file twice, which seems bad.
Probably just add a collection field to an ItemCollection, eh?
collection
ItemCollection
The text was updated successfully, but these errors were encountered:
It should probably be a collections array field rather than singular to accommodate geoparquet that may have Items from multiple collections.
Sorry, something went wrong.
@bitner should we update the spec to reflect this? It seems to suggest that only a single collection should be included.
Successfully merging a pull request may close this issue.
https://github.com/stac-utils/stac-geoparquet/blob/main/spec/stac-geoparquet-spec.md#including-a-stac-collection-json-in-a-stac-geoparquet-collection
I think we'd support this on the way in either by:
Way out would be similar-ish, where if we didn't do it on an item collection we'd just hit the parquet file twice, which seems bad.
Probably just add a
collection
field to anItemCollection
, eh?The text was updated successfully, but these errors were encountered: