You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The properties and skipGeometry filters are applied when querying /items but are ignored when retrieving a single item via the /items/{id} endpoint. Extending this functionality would improve consistency and efficiency when retrieving specific attributes for a single feature.
Describe the solution you'd like
I would like to be able to use pygeoapi to return minimal bytes possible when doing a transaction. Say I want to use the id of pygeoapi demo Lakes collections to resolve it's wikipedia url. The following query allows me to return only the pertinent information: https://demo.pygeoapi.io/master/collections/lakes/items?f=json&properties=name_alt&skipGeometry=true&id=0
However, when making the same request for a single item, there is no way to minimize the size of the payload: https://demo.pygeoapi.io/master/collections/lakes/items/0?f=json&properties=name_alt&skipGeometry=true
Describe alternatives you've considered
It is possible to configure geometry and properties via pygeoapi configuration, but I would like to make these values conditionally available.
Additional context
Naively you could implement the this within pygeoapi/api/itemtypes.py but that feels like an incorrect solution. A variety of providers have a flexible enough implementation of the select properties and skipGeometry options it might be easy to port the logic used in p.query(select_properties=[], skip_geometry=False): logic into p.get(identifier, select_properties=[], skip_geometry=False, **kwargs):
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The properties and skipGeometry filters are applied when querying
/items
but are ignored when retrieving a single item via the/items/{id
} endpoint. Extending this functionality would improve consistency and efficiency when retrieving specific attributes for a single feature.Describe the solution you'd like
I would like to be able to use pygeoapi to return minimal bytes possible when doing a transaction. Say I want to use the id of pygeoapi demo Lakes collections to resolve it's wikipedia url. The following query allows me to return only the pertinent information:
https://demo.pygeoapi.io/master/collections/lakes/items?f=json&properties=name_alt&skipGeometry=true&id=0
However, when making the same request for a single item, there is no way to minimize the size of the payload:
https://demo.pygeoapi.io/master/collections/lakes/items/0?f=json&properties=name_alt&skipGeometry=true
Describe alternatives you've considered
It is possible to configure geometry and properties via pygeoapi configuration, but I would like to make these values conditionally available.
Additional context
Naively you could implement the this within
pygeoapi/api/itemtypes.py
but that feels like an incorrect solution. A variety of providers have a flexible enough implementation of the select properties and skipGeometry options it might be easy to port the logic used inp.query(select_properties=[], skip_geometry=False):
logic intop.get(identifier, select_properties=[], skip_geometry=False, **kwargs):
The text was updated successfully, but these errors were encountered: