Split Operational Layers Across Multiple Dekho Maps

Although it is possible to publish all operational layers within one dynamic map service and publish alongside a basemap as one Dekho map. It is recommended that the operational layers are separated into logical themes within business data, and published as separate Dekho maps (see figure 4).

This offers two clear advantages:

§ Allows for easier allocation of Dekho Maps to specific Dekho Roles that require access to the themed maps.

§ Avoid having a bloated dynamic map service containing all operational layers which will have an impact on performance.

If a user needs to print, they can only print layers from one Dekho map and not a combination of layers from different Dekho Maps.  Select by selection and measurements between layers in different maps are also not possible.  Common layers can be duplicated across the multiple Dekho maps to get around this problem.

 

 

With data split across different themed Dekho Maps, users can still toggle between the different Maps and the extent can be retained so that the user retains focus on only their area of interest.

 

 

 

Figure 5 - Split content across multiple themed Dekho Maps.

 

If business requirements call for a large number of operational layers within a single Dekho Map, along with adhering to best practice for map service authoring, a good approach is to:

§ Publish the service with the majority of the lesser-used layers turned off by default.  This avoids unnecessary wait times on initialising Dekho.

§ Don’t spread the layers across multiple dynamic map services within the same Dekho Map, but consolidate them into a single dynamic map service.  One request is sent to the GIS Server, one SOC process will draw the map, and one image is sent over the network.  This will scale better than spreading the load across multiple dynamic services.


Layer Description Tags