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
It appears the current behaviour of QGIS is to hit the /collections/{collection-id}/items endpoint (with filters) to get a listing of geospatial features to render in a layer.
When I click on a Feature with the info tool to see its properties, QGIS currently shows just the properties that were present on the Feature in the listing's response.
I have an OGC Features API that delivers a lot more detail about a Feature if you query the individual feature on the "Feature" endpoint like: /collections/{collection-id}/items/{feature-id}.
Does it make sense that QGIS could send an additional request to the "Feature" endpoint, for more details about a given geospatial feature when required?
Additional context
Our /collections/{collection-id}/items endpoint returns a FeatureCollection GeoJSON document with a list of features matching the given bbox/cql filters, where each of the Features contains only very basic attributes, eg, type, title, id, geometry, and small properties map with description, time.
Our /collections/{collection-id}/items/{feature-id} endpoint returns a single Feature GeoJSON document with all of the known details of the Feature, with a properties map with potentially with hundreds of properties, which aren't needed and aren't included in the FeaturesCollection view.
The text was updated successfully, but these errors were encountered:
Feature description
It appears the current behaviour of QGIS is to hit the
/collections/{collection-id}/items
endpoint (with filters) to get a listing of geospatial features to render in a layer.When I click on a Feature with the info tool to see its properties, QGIS currently shows just the properties that were present on the Feature in the listing's response.
I have an OGC Features API that delivers a lot more detail about a Feature if you query the individual feature on the "Feature" endpoint like:
/collections/{collection-id}/items/{feature-id}
.Does it make sense that QGIS could send an additional request to the "Feature" endpoint, for more details about a given geospatial feature when required?
Additional context
Our
/collections/{collection-id}/items
endpoint returns aFeatureCollection
GeoJSON document with a list of features matching the given bbox/cql filters, where each of the Features contains only very basic attributes, eg,type
,title
,id
, geometry, and small properties map withdescription
,time
.Our
/collections/{collection-id}/items/{feature-id}
endpoint returns a singleFeature
GeoJSON document with all of the known details of the Feature, with aproperties
map with potentially with hundreds of properties, which aren't needed and aren't included in theFeaturesCollection
view.The text was updated successfully, but these errors were encountered: