Opened 15 years ago
Last modified 14 years ago
#9 closed defect
Feature highlighting — at Version 1
| Reported by: | yvesm | Owned by: | adube |
|---|---|---|---|
| Priority: | major | Milestone: | First milestone |
| Component: | widgets | Version: | 0.7 |
| Keywords: | queryonclick, recenter, initialview | Cc: | jlacroix |
Description (last modified by )
Feature highlighting is necessary for users to see where a specific feature is. There are currently two use cases that users would need highlighting for :
- query
When a user clicks on "i" (queryonclick widget; GetFeatureinfo) a list of results is returned usually in an Ext grid (see resultextgrid widget). However, it is impossible for a user to know where he clicked as none of the features returned in the grid are highlighted on the map.
A solution is to add a marker on a vector layer. However that is a bit cumbersome as the size of the marker may be either much larger than the bbox of the features returned (e.g. low zoomLevel and small tolerance) or the other way around. It would be useful to be able to configure the queryonclick widget to also allow for feature highlighting (in replacement of/combination with using a marker).
- shortcut/recenter/initialview
A shorcut widget (or its dynamic version, the recenter widget) can be used to zoom in on a feature. In their current implementations, it is impossible for the user to know which is the feature zoomed to except in the very obvious case of one big central feature. The reason for that is that the zoomTo action will zoom with the selected feature in the center of the viewport. In most cases however, the multiplicity of features makes it impossible to know which is the one zoomed to. The same applies to the initialview widget.
All widgets that provide zoomTo type features should have a provision to highlight the feature(s) zoomed to.
See also #12
