Server Name

The server name as reported to clients. According to the WFS/WMS standard, some of the requests arriving to the server require the SGS to include the server name and title in its reply. This has no practical impact on the functioning of SGS.

Note:   This setting is only displayed for super administrators.

Server Title

The server description as reported to clients. According to the WFS/WMS standard, some of the requests arriving to the server require the SGS to include the server name and title in its reply. This has no practical effect on SGS operation.

Note:   This setting is only displayed for super administrators.

Language

Select the language for the SGS Manager’s user interface and error messages.

Enable Auto-Scan

Switch on to enable auto-scan for all data sources that have been set for auto-scan. All data sources except SG Upload have an Auto-Scan setting in their property sheet. See "Adding Data Sources" in the "Working with Data Sources" chapter for more information.

Note:   This setting is only displayed for super administrators.

Enable CORS

Switch on to enable Cross Origin Resource Sharing (CORS), allowing requests from pages hosted on domains other than the SGS domain.

Note:   Enabling CORS may also be necessary if you have multiple domain names that point to your SkylineGlobe Server.

Note:   This setting is only displayed for super administrators.

SameSite Cookies

Controls when the browser sends the SGS session cookie with requests originating from other sites.. Cookies are required for accessing non-public layers, i.e., layers with restricted view and edit access. A session cookie is sent when a user logs in to SGS via the GUI or API or using an access token. Select one of the following options:

§  Strict – Cookies will only be sent with same-site requests. Requests originating from another site do not include the cookie and therefore cannot access non-public SGS resources. This is the default and most restrictive option.

§  Lax – Cookies will be sent for same-site requests and top-level navigation requests from external sites. Use this option when using SSO authentication, i.e., when users log in through a third-party identity provider and are then redirected to your SGS domain.

§  None – Cookies will also be sent with cross-site requests, allowing an application hosted on another site to access non-public SGS resources. The recommended default for this option is that all browser requests must be secure, i.e., follow the HTTPS protocol. If you want to allow streaming over a non-secure HTTP connection (e.g., for internal testing), clear the Secure option and in the client-side browser, disable the setting that limits non-SameSite cookies to secure connections.

Note:   If SameSite Cookies was set to None and Secure (i.e., to use HTTPS protocol), but SGS cannot be accessed over HTTPS, your browser may not send the session cookie and you may be unable to open SGS Manager to correct the settings. To temporarily open SGS Manager using the Lax setting, append samesitelax=1 to the URL. Use ?samesitelax=1 if the URL does not already contain query parameters, or &samesitelax=1 if it does. E.g., https://skylineglobe.com?samesitelax=1

Note:   This setting is only displayed for super administrators.

SG Services Configuration File

A file configuring the address search provider and the available OSM feature and map layers in TerraExplorer Desktop.

This field should contain only the file name, e.g., SGServices.json, and not the full path. SGS looks for the file in the SharedConfigurations folder. See “Settings” in the “Getting Started” chapter for more information.

When SGS 8.5 starts, it automatically creates SGServices.json in the SharedConfigurations folder if the file does not already exist.

Note:   Changes can be made to the file by editing the file on disk. If working with a cluster and using a local path, the edited file should be copied to the same local path on all servers in the cluster.

Note:   This setting is only displayed for super administrators.

Cache Folder

Sets the folder where SGS stores its cache. When requests are made to an SGS layer, it caches the request so that SGS can serve subsequent requests efficiently without reloading or reprocessing the source data. Cache is only created for 3D Tiles, feature layers in database data sources (Oracle Spatial, SQL Server, or PostgreSQL), and DirectConnect projects.

By default, the cache folder is located in the DynamicCache directory under the main SGS configuration folder.

The cache folder is very important to the work of the SGS. For best performance, this folder should be located on a high-speed storage device. For better cache management of a cluster, it is recommended to store the cache on a shared network drive.

Note:   In a DirectConnect project, cache files are automatically located in TBP_Cache under the Cache Folder.

Note:   This setting is only displayed for super administrators.

Use Draco Compression

Switch this option on to serve 3D Tiles in GLB format with Draco compression, for reduced size and better streaming.

Enable Categories Mechanism

Switch this option on to enable the category mechanism. See "Enabling Layer Categories" in the "Working with Layers" chapter for more information.

Display Categories for Anonymous Users

Switch this option on to display the categories panel in the Layers dialog also for users who are not logged in. See "Enabling Layer Categories" in the "Working with Layers" chapter for more information.

Servers

The names and IP addresses of each of the servers in your server cluster.

Public WMS/WFS URL

URL that WFS/WMS clients use to connect to SGS (Read-only).

Maximum WFS Response Size

Maximum size for WFS feature requests, from 1 to 100 MB.

JPEG Quality

Move the slider to adjust JPEG quality.

Note:   This setting is only displayed for super administrators.

Image Quality

Move the slider to adjust image quality.

Note:   This setting is only displayed for super administrators.

Maximum WMS Image Size

Maximum WMS image response size, from 256 to 2048 pixels.

Note:   This setting is only displayed for super administrators.

Add New Configuration

Click Add New Configuration to set TerraExplorer Fusion Settings. The TerraExplorer Fusion Settings dialog is displayed. See "Configuring Your TerraExplorer Fusion" in the "Customizing TerraExplorer Fusion" chapter for information.

TBP Connection Timeout Duration

Determines the time (in minutes) that the TerraBuilder resources remain connected to a project after last accessing it.

Note:    The two most recently accessed projects are always kept active. This timeout applies only to any additional projects beyond those two.

Minimum Number of TBP Connections to Keep Alive

Determines the minimum number of TBP connections SkylineGlobe Server should maintain alive (even when a TBP is not being accessed).

By default, SkylineGlobe Server automatically shuts down the connection when a TBP is no longer being accessed, after the time set in the TBP Connection Timeout Duration parameter. Keeping some connections live minimizes the startup time for subsequent accesses to the same project, but also uses up memory on each of the computers allocated resources for DirectConnect processing.

Maximum Number of Threads per TBP

Sets the number of threads on each host that will serve each TBP.