Customer geodata typically is split into two types concerning data update:

1.Static geodata does not change permanently (day by day). It gets fully (not incrementally) updated in a cyclic manner (from time to time, i.e. every year etc.)

2.Dynamic geodata does change permanently, e.g. it gets frequently (day by day or minute by minute) updated (incrementally).

 

The first type of data is perfectly fit to be represented in a map cache for quick an efficient delivery of high quality maps.

The second type of data can only be rendered dynamically and is not applicable for map caches.

WebOffice 10.9 R4 was designed to provide optimum support for displaying static as well as dynamic at one point of time:

1.You just need to put your static base data into a map document which will be published as a cached service,

2.You just need to put your dynamic data into a map document which will be published as a dynamic service.

 

Both services get added to the Map Collection of a WebOffice 10.9 R4 project and get displayed simultaneously in a Map View at a point of time.

 

 

As the static base data service is cached it will quickly deliver map cache tiles. As the dynamic service will be light weight (because the count of dynamic geographic datasets (feature classes) compared to static geographic datasets is typically very low) and rendered fast it will quickly deliver dynamic maps.

 

Both maps get displayed one on top of the other by WebOffice 10.9 R4. Result is a good performing combination of cached and dynamic maps, representing both static base data as well as dynamic data in the WebOffice 10.9 R4 clients simultaneously.

 

 

If you want to enable in WebOffice 10.9 R4 clients with table of content (TOC) to dynamically change the appearance and behavior of the layer display in the map service in, you can activate dynamic workspaces in the map service. Dynamic layers can increase the level of interaction for your users in WebOffice core client.