3D services cache configuration |
Compared to map service, 3D service has larger data, and data transmission and scene rendering face greater pressure when client is accessing server. Therefore using cache for 3D service is more necessary. Generating cache for data such as image, model, vector, topography and map of 3D scene can effectively improve 3D service performance.
SuperMap iServer takes a series of measures to improve the efficiency of 3D service access. For 3D service, you can: Enable HTTP cache,enable request cache that covers all service type, generate 3D cache file for data such as image, model, vector, topography and map of 3D scene. See detail: Cache strategy of 3D service.
SuperMap iServer 3D service supports data type and cache format ,including: image cache, topography cache, vector cache, vector model cache, 2D and 3D map cache and the whole 3D scene cache, see detail: 3D cache's storage format.
There are two ways of producing and using 3D cache: using the distributed tile service of iDesktop or iServer, the former can produce all common used 3D data cache, and the latter can distributively produce and store (MongoDB) 3D image and 3D topography tile.
When using iDesktop to make 3D cache, you can "create scene cache" for single data layer as well as create complete cache for whole 3D scene in advance.Put the generated cache in cache directory of 3D service([SuperMap iServer installation directory]\webapps\iserver\output\{scene}). When client is accessing 3D service, server will use cache data mentioned above. The advantage of using 3D scene cache is that one operation in SuperMap iDesktop can cache all data in the scene, and also stores cache of whole scene in 3D service cache directory, which more likely to ensure the integrity of file name and directory of every data cache file.
Besides, for map in 3D scene, although the default dynamically generated scene when browsing scene is scene cache (*.sci3d format), but if the cache file stored in advance is map cache file of SuperMap UGC v5.0 global subdivision (*.sci), when client is browsing map in scene, 3D service can also recognize and use it.
SuperMap iServer's distributed tiling model supports tiling scene image, topography layer of published 3D service into 3D tile and storing them in MongoDB.
After making and publishing 3D data, you can tile 3D layer into 3D tile through iServer distributed tiling model, and quickly publish it as 3D service. After tile is published as service, you can see data through datas resource of 3D service. Client can browse in 3D scene directly through data 3D description.
The procedure that tiling 3D tile by using distributed tiling service is almost similar to tiling 2D tile, the small difference is in creation of tiling task.