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
Provide a clear and concise description of what you want to happen.
In many cases, admin_level_data layers represent categorical variables. For example, in RBD, the ifpri_conflict_2023 layer uses the data field ACI_value which range from 1-4. The numeric values have a concept of ranking, but not of a real value.
When a user clicks on the map, the tooltip shows the numeric value (i.e. '1', '2', '3', '4'). I want to be able to optionally configure admin_level_data to use label instead of value in the tooltip. We can do this using feature_info_props by adding an attribute such as source. See the example below
A side note - the term feature_info_props is pretty abstract. If we can look into changing this to tooltip or something more clear, that would be appreciated too!
Is there anything else you can add about the proposal? You might want to link to related issues here, if you haven't already.
No response
The text was updated successfully, but these errors were encountered:
Provide a clear and concise description of what you want to happen.
In many cases,
admin_level_data
layers represent categorical variables. For example, in RBD, theifpri_conflict_2023
layer uses the data fieldACI_value
which range from 1-4. The numeric values have a concept of ranking, but not of a real value.When a user clicks on the map, the tooltip shows the numeric value (i.e. '1', '2', '3', '4'). I want to be able to optionally configure
admin_level_data
to uselabel
instead ofvalue
in the tooltip. We can do this usingfeature_info_props
by adding an attribute such assource
. See the example belowThis would then make use of the label associated with each value configured in the legend of this layer:
The change mentioned above should show this:
A side note - the term
feature_info_props
is pretty abstract. If we can look into changing this totooltip
or something more clear, that would be appreciated too!Is there anything else you can add about the proposal? You might want to link to related issues here, if you haven't already.
No response
The text was updated successfully, but these errors were encountered: