-
-
Notifications
You must be signed in to change notification settings - Fork 261
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
collection itemType can contain multiple types? #581
Comments
itemType as an array of types
As I understand it:
Based on this, the first |
Thanx Tom, yes if itemType is a string (and not adopted by all OGC API's), then we don't have much options I guess the open api document will be leading to api developers in exploring the API. However other users, such as incidental human beings, search engine crawlers, traditional GIS clients, etc may arrive at a collection endpoint without being aware of the open api document (or how to consume it). I find the follow-the-links a bit too technical and loose for ease-of-use. Even with OGC-API-Coverage not supporting the itemType parameter at the collection level (because they expect to have collections supporting both coverage as well as a feature output), the spec doesn't indicate that we can't add it as a vendor parameter... closing this for now |
when implementing #579 i was surprised to find only "features" as collection itemType.
Then i found that itemType is calculated from the 'default provider' at
pygeoapi/pygeoapi/api.py
Line 340 in 48d00d6
In case a dataset is exposed as features and maps (typical behaviour?) i'd expect both types to be available in collection-itemType
I suggest we allow collection.itemType to contain an array of types.
The text was updated successfully, but these errors were encountered: