search

OpenWaterFoundation / owf-app-infomapper-ng

Open Water Foundation InfoMapper web application for menu-driven maps and visualizations, using Angular
GNU General Public License v3.0
1 stars 2 forks source link

Need to be able to configure radio buttons for polygon layers in a group #242

Closed smalers closed 3 years ago

smalers commented 4 years ago

I added a Political - Legislative Districts map to the Poudre Basin Information website. There are layer views for House and Senate districts for 2011 and there will be new districts this year or next. Because the districts cover the entire state and use transparency, there is confusion if more than one layer is on at the same time. The map configuration file specification supports a design to indicate if the layer views in a group should only allow one on at a time, similar to background layers. I need confirmation that this has been implemented for other than background and I can try.

I'm going to to have to figure out how to handle federal and county legislative districts, with similar issues.

smalers commented 3 years ago

I found an example on an Esri site that illustrates this requirement:

Water Districts

image

smalers commented 3 years ago

I previously documented GeoLayerViewGroup properties that describe how this might be configured.

Nightsphere commented 3 years ago

Two major pushes were merged with new properties being supported. The selectBehavior property has now been implemented for a geoLayerViewGroup in the geoMap. When non-existent or set to Any, any and all layers in the group can be turned off and on at will.

When set to Single, at most one layer can be turned on at a time. By default, the top most layer in the group will be toggled on, but can be any layer if a user specifies for each layer in the group to be turned off except for the desired layer. All layers can also be turned off as well. Clicking on a toggled off layer while another in the group is being shown will toggle off the shown layer and display the clicked layer.

The solution to this issue also needed Issue #148 to be completed, which was done as well. Closing this issue.