-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
QGIS Server GetFeatureInfo request should take attribute sort order into account #48742
Comments
I'm not sure I understand, can you please add some details? |
@gioman I think this should have the feedback label or be closed. |
@tudorbarascu my feature request concerns the sorting of the features in a GetFeatureInfo request and not the sorting/reordering of the attributes/fields. |
Maybe the attribute place is not the right place to configure the sort order for features in GetFeatureInfo response but AFAIK there is no way to configure it in QGIS or via a parameter in the request. It seems GetFeatureInfo request is missing a Anyone can confirm? |
@nboisteault The attribute table column configuration affects the visibility and order of the attributes, so why not use the sort order of the table as the default sort order for the GetFeatureInfo query? |
I can confirm, there is no way to order the results. I would add that there is not a simple way we can add this functionality: the request can query multiple layers and we should specify the ordering criteria for all of them independently. WFS and OAPIF on the contrary can filter and order results, because they operate on a single layer for each request. Perhaps we could add a sort by option for each layer in the server configuration panel, I am not convinced that the attribute table is the right place for this configuration: the attribute table is oriented to the desktop data visualization. |
We can use w/ WFS GetFeature, several For a GetFeatureInfo request, would it be possible to have several |
Feature description
QGIS Server 3.24.2-1 (Windows): GetFeatureInfo request takes over the column aliases but not the configured attribute sort order.
Additional context
No response
The text was updated successfully, but these errors were encountered: