Introduction to Skyline software SFS Service

The SFS server can transmit the feature layer (WFS) or map image data (WMS) to the client application through a network stream. WMS obtains map image data from terragate terrain service. WFS reads feature layer data from the shape file and Oracle database, SQL Server database, postgis and ArcSDE server.

SFS is used to publish and manage WFS and WMS compliant with OGC specifications. It introduces the map service cache mechanism and significantly improves the access speed of the map service by establishing static and dynamic caches.

 

SFSBenefits

1. SFS can release WFS and WMS compliant with OGC Specifications

One of the most important standards for OGC service interfaces is the WFS and WMS interface service specifications. By defining WMS and WFS specifications, users can access the map service that meets the requirements in a unified way through a browser, without considering the differences of the underlying GIS. Through the combined application of these interfaces, You can integrate the geographic information of remote heterogeneous data sources to achieve GIS application interoperability in a true sense and share spatial information data and services. This is of great significance for the construction of the information sharing platform and the provision of distributed services.

2. The access speed to the map service is greatly improved

SFS introduces the map service cache mechanism and significantly improves the access speed of the map service by establishing static and dynamic caches. The static cache mechanism generates geographic "slices" based on the map service in blocks, significantly improving the implementation efficiency of the map service. This mechanism allows the user terminal to directly read vector data and raster data from the cached data, instead of sending requests to the server as in the traditional mode, you can dynamically generate the required data.

SFS service includes the following three services:

Web Feature Service (WFS)

Web Map Service (WMS)

Web (CS-W)

1.1 web feature service

Web Feature Service (WFS)-Read layer data from SHP files, Oracle databases, SQL Server databases, postgis, and ArcSDE servers or read data created by cache creator (Cache creation tool, and transmitted in stream mode.

Any application that can read the ogc wfs protocol can read the feature layer through the web feature service, including points, lines, and surfaces. WFS can read feature layer data from SHP files, Oracle, SQL Server, postgis, and ArcSDE databases. WFS has several subsystems that can respond to requests that process multi-source data streams. Layer data is returned to the WFS service, converted to the standard WFS format, and then sent to the client application.

WFS uses a caching mechanism to achieve efficient performance and advanced scalability. WFS reduces the loading process from a slow data source by calling the cache, such as ArcSDE or Oracle, and can create a cache in advance and transmit data (such as SHP files) in a stream ). V6 also supports reading source data directly from the shape file without creating a cache.

Input Format:

Oracle Database (with spatial extension)

ESRI ArcSDE Server

SQL Server 2008

PostgreSQL/postgis

ESRI shape file (*. SHP)

Output Format:

Standard WFS data block

Scrambled and compressed data block

Web feature service features

L manage and transmit the feature layer in streaming mode, including SHP file points, lines, and surfaces, Oracle databases, SQL Server databases, and ArcSDE servers;

L provide OGC Web Feature Service (WFS) for other applications );

L can pre-cache data or directly connect to the source data. Through caching, SFS reduces the loading process from slow data sources, such as ArcSDE or Oracle, and is able to pre-create cache and then transmit data (such as SHP files) in streaming mode );

L create a cache on the server to efficiently transmit data in streaming mode;

L pre-configure data caching for the entire layer or create data based on each request in real time;

L can be upgraded to meet the data access requests of a large number of users (SFS cluster );

L automatic refresh mechanism, which can be automatically refreshed when layer data is updated;

L it can mark the expiration time of each cache slice;

L cache at each layer is stored in three different levels of detail to achieve the optimal performance;

L effectively process multi-user requests on each server;

L a network-based management system that can define the data source and vector layer and set the cache. Efficient processing of a large number of databases without data volume restrictions.

1.2 Web Map Service

Web Map Service (WMS)-Read spatial map data from the terrain cache and transmit it as a stream.

Any application that can read the ogc wms protocol can read skyline map raster data through TG Web Map Service. The terrain service reads data from the terrain dataset (MPT file) or creates data blocks through the direct connect module, and then returns the data to the WMS service, convert to the standard WMS format and send it to the client application.

The image and elevation formats supported by WMS include JPEG (signed 8 bit) and PNG (unsigned 16 bit ).

Web Map Service Features

L provides the OGC Web Map Service (WMS) interface for the terragate terrain dataset;

L output image and elevation layer;

L outputs raster data in JPEG and PNG formats;

L can be upgraded to meet the data access requests of a large number of users (SFS cluster );

L effectively process multi-user requests on each server;

L a network-based management system that can define the data source and vector layer and set the cache. Efficient processing of a large number of databases without data volume restrictions.

1.3 catalog service-Web

Catalog service-web (CSW) is an OGC standard (for details, see:

Http://www.opengeospatial.org/standards/cat), which supports publishing and searching of geospatial datasets. The CSW released by SFS, a standard CSW client, including the terraexplorer client, can use geographic metadata to query the Valid feature layer (WFS) and raster layer (WMS) in the terragate service) and 3D terrain data (TG ).

Based on these query results, the client can connect to these geographic source data.

The feature of the terraexplorer client is enhanced by allowing real-time release of source data without pre-release. For example, you can search for the catalog on the server side, find the SHP file, and send a request to connect to it. The file is then automatically transferred through the SFS-WFS service.

 

*************

As a developer or tester, they are more concerned with how to request Services released by SFs. The following describes common request service formats. In fact, they are all strictly formulated according to OGC standards, if you want to make better use of the SFS service, I hope you will spend more time learning about the WFS and WMS services provided by the OGC standard;

 

WFS:

Http: // skyzh/SFS/streamer. ashx? Request = getfeature & service = WFS & typename = dc_ff_parks

 

WMS:

Http: // skyzh/SFS/streamer. ashx? Request = getmap & version = 1.1.1 & service = WMS & SRS = epsg: 4326 & layers = sample. i. MPT & styles = & format = image/JPEG & bBox = 135.000000, 22.500000, 157.500000, 45.000000 & width = 256 & Height = 256