Is there a limit on the number of map overlay layers supported by the map application ?
In my use case i’ve around 7500 kml files that need to be displayed in googlemap. It seems that the map app is stuck when parsing the config file with all these layers
Is there a way to declare layers only when the user ask to display it to limit the size of the config file ?
There’s no hard coded limit on this, but 7500 layers won’t be really workable…
To better understand your use-case, why are there so many?
It’s possible to configure which layers are initially visible, and to display them in the dropdown boxes:
<Layer sourceType=”table” refresh=”5000″ name=”Cable Modems” visible=”false” allowToggle=”true” toggleGroup=”Layers” minZoom=”13″ maxZoom=”15″ limitToBounds=”true”>
- visible (true/false): if the layer needs to be loaded initially (default = true)
- allowToggle (true/false): if the layer should be added to the UI to let the user toggle the layer on or off (default = false)
- toggleGroup (string): if allowToggle is true, contains the name of the toggle group to which the layer belongs to. The group name will be used as button text which shows/hides the toggle controls (default = “Layers”)
Hi Wim,
In my use case I’ve one kml layer per dvb-t transmitter.
I already set the visible=”false” allowToggle=”true” toggleGroup=”Layers” so these layers are not displayed by default but the map app seems stuck to load the config xml with all these layers definition