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

Support OGC-Features-API "Feature" endpoint #60584

Open
ashleysommer opened this issue Feb 13, 2025 · 0 comments
Open

Support OGC-Features-API "Feature" endpoint #60584

ashleysommer opened this issue Feb 13, 2025 · 0 comments

Comments

@ashleysommer
Copy link

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 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants