 |
|
|
WHAT’S NEW IN TERRAGATE® RELEASE 4.1.1
|
|
Upgrade your TerraGate to the latest v4.1.1 release
|
Stream Imagery and Elevation Layers to TerraExplorer
Terrain databases can now be streamed to a TerraExplorer client as an Imagery or Elevation layer. This is achieved by the two index files (*.mIdx and *.strmi) which provide direct access to the MPT files.
Streaming Feature Server Component
The Streaming Feature Server component has the ability to efficiently stream across a network complex feature data layers, from a variety of sources. Supported sources include Oracle Spatial, ArcSDE and Shape files. The Streaming Feature Server uses a cache mechanism allowing ultra high-speed performance and high-level scalability.
The ability to pre-cache data enhances applications that utilize very large static feature layers where performance is crucial. The Streaming Feature Server stores and streams feature data in Web Feature Service (WFS) or scrambled protocol to feed feature data to TerraExplorer clients.
Key Features:
The SFS streams feature data directly from Shape files, Oracle database or ArcSDE server
Stores cached data as standard WFS or in a scrambled format to better secure your data.
Creates a cache on the server for high-performance streamed data and efficient handling of large number of users.
The data cache can be configured in advance for an entire layer or created on-the-fly per request.
Auto-refresh mechanism can be set to active when a layer is updated
Ability to mark each cache tile data with an expiration time
Stores each layer's cache in three different detail levels for better optimization
Optimized to handle a high number of requests per server
Web-based management system to define the data sources, layers, and cache settings
Changes made in version 4.0
TerraGate with DirectConnect Major Performance Improvement
Larger terrain databases, shorter update intervals and a higher number of concurrent users are the rewards for introducing an improved DirectConnect mechanism. The added functionality for pre-processed cache files and its supporting mechanisms make it possible to achieve a remarkable performance gain in serving high-availability projects.
In previous versions, the project cache for all project sources was stored in a single file. With the new mechanism, a separate cache file is used for each source and a different cache is dedicated for each geographical area to which multiple sources jointly contribute.
Multiple Source Caching
Reading native files of multiple formats and processing data on-the-fly requires valuable server-side resources. This new approach of creating a separate cache file for each source boosts performance as each cache can be pre-compiled separately. These pre-compiled cache files are built as standard MPT files.
A separate cache file is dynamically created for each native source file accessed by a DirectConnect project. Each cache file is compiled according to the unique coordinate system and source manipulation parameters of its source file.
To optimize delivery time and reduce the burden on server-side resources, MPT source files in a DirectConnect project are served to the client without fuser processing. The removal of fuser processing was achieved by the introduction of two index files (*.mIdx and *.strmi) which provide direct random access to the MPT files.
The introduction of the new caching mechanism have resulted in a considerable performance gain to the effect that DirectConnect projects can be delivered as efficiently as stand-alone MPT file projects.
A separate cache for areas generated out of multiple sources
Areas in a DirectConnect project that are compiled out of multiple sources are stored in an independent cache store. A new version of the cache file is created whenever changes are introduced to the project.
Purge Cache
A new Purge Cache mechanism simplifies identification and deletion of unneeded cache files.
New Aliasing Functionality
The new aliasing mechanism enables the definition of aliases for for terrain databases to provide easy access for your clients. In addition, seamlessly update an alias by assigning it to a new or updated version of the terrain database.
|
|
|