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
Author Name: Bernd Vogelgesang (Bernd Vogelgesang)
Original Redmine Issue: 12890
Redmine category:map_legend
When using a Filter/Feature subset/Query on a layer, the user or other users reusing the same project can't see immediately, that the layer is filtered and does not provide the whole data set. This can lead to a lot of confusion, when suddenly some data is "gone".
Especially with ESRI-Shape files, which become uneditable when filtered, users may think that something is broken cause the layer does not behave as expected.
Of course one can see the filtered state when hovering over the layer name, but especially for novices the statements might not be interpretable.
So it would be nice to add e.g a funnel symbol behind the layer name to indicate that it is filtered.
The same symbol might be added to the context menu before "Filter...", so users easily learn what the symbol means.
Author Name: Bernd Vogelgesang (Bernd Vogelgesang)
Original Redmine Issue: 12890
Redmine category:map_legend
When using a Filter/Feature subset/Query on a layer, the user or other users reusing the same project can't see immediately, that the layer is filtered and does not provide the whole data set. This can lead to a lot of confusion, when suddenly some data is "gone".
Especially with ESRI-Shape files, which become uneditable when filtered, users may think that something is broken cause the layer does not behave as expected.
Of course one can see the filtered state when hovering over the layer name, but especially for novices the statements might not be interpretable.
So it would be nice to add e.g a funnel symbol behind the layer name to indicate that it is filtered.
The same symbol might be added to the context menu before "Filter...", so users easily learn what the symbol means.
Cheers
Bernd
Related issue(s): #24277 (duplicates)
Redmine related issue(s): 16367
The text was updated successfully, but these errors were encountered: