跳到主要内容

Connection

Datasource Public ID

The Datasource Public ID functions as a unique identifier for Datasources, facilitating the identification and interaction with specific map layers by external systems. The public ID is utilized, for example, in the postMessage API. When external systems embed the HxGN Smart Sites Client, they specify the publicId within the datasourceId field of the postMessage API messages, indicating the intended Datasource for the communication.

Datasource Title

The Datasource Title is the name used to identify the Datasource for end users.

Datasource Description

The Datasource Description is the optional text used to describe the Datasource for end users.

Datasource Protocol

The Datasource Protocol defines how the HxGN Smart Sites interprets the Datasource URL to establish the connection. The Datasource Protocol unlocks protocol-specific capabilities.

HxGN Smart Sites relies on OGC services to connect to the Datasource.

The supported protocols are:

  • WFS, for vector data services
  • WMS, for raster data services
  • WMTS, for tiled raster data services
  • HSPC, for HxGN Smart Point Clouds
  • OGC 3D Tiles, for 3D models
  • OGC 3D Tiles Collection, an extension of the OGC 3D Tiles protocal specific to HxGN Smart Sites.
  • LTS, Luciad Tile Service
  • Tianditu
  • Google 3D Tiles
  • Panorama, for panoramic images

Datasource URL

The Datasource URL is used to connect to the underlying service.

Panorama: Datasource URL

For the panorama protocol the datasource URL points to a WFS service that servers the locations of the panoramic images.

Security Options

The security options define how credentials are used to connect to the Datasource. The available options are:

  • Token. Forwards the user’s access token as a Bearer token in the Authorization header.
  • Basic Auth. Forwards the provided username and password in the Authorization header.
  • Api Key. Only available for TIANDITU and Google 3D Tiles Datasources. The provided API key is injected in the service URL.
备注

The LuciadFusion Server installed with HxGN Smart Sites requires authentication from users for access to any data. Make sure to select Token if your Datasource is hosted there.

Datasource Options

Datasource connections might require protocol-specific options:

WMS: GetFeatureInfo

Enables or disables the GetFeatureInfo functionality for the layers of this Datasource. If this is enabled, WMS layers of the Datasource marked as queryable by the underlying WMS service may be queried in the HxGN Smart Sites Client. This means that the Datasource layers are clickable, and information about the clicked location or object will be shown in the Properties Panel.

备注

This setting has no effect if the WMS layer is not advertised as queryable by the WMS Server.

WMS: Layers

WMS Layers define which layers, published by the underlying WMS service, are used. One or more layers can be configured by choosing from a drop-down list. Use the icons next to the list to remove the layer or change the layer order. The later layers in the list are painted on top of and cover previous ones.

WMTS: Layer

WMTS Layer defines which layer, published by the underlying WMTS service, is used. Only one layer can be configured. Ensure that the values align with the name of the layer revealed in the capabilities of the underlying WMTS service.

WFS: Feature Type

The Feature Type configures which vector object is visualized when connecting to a WFS Datasource.

WFS: Prefer GML

This toggle configures whether to request the features of a WFS Datasource in output format GML or GeoJSON.

WFS: Realtime Channel ID

The Channel ID indicates that the Datasource supports realtime data. The Channel ID refers to the ActiveMQ topic and the WebSocket channel where the realtime data is emitted.

The Channel ID unlocks the realtime capability of the HxGN Smart Sites Client. Where users toggle the "Realtime Mode", the HxGN Smart Sites Client starts listening for incoming realtime events for display.

备注

The LuciadFusion Server installed with HxGN Smart Sites listens to ActiveMQ topics and pushes the data to the corresponding WebSocket channels.

LTS: Coverage ID

The Coverage ID identifies the coverage that is published by the underlying LTS service.

Tianditu: Layer

The layer used in the Tianditu map service.

The input options map to the actual Tianditu layer are as follows:

OptionTianditu layer
Rasterized vector datavec
Background imageryimg
Labelscva

Panorama: Images Base URL

The URL used by the HSS client application to access the panoramic images. The HSS client application will use this base URL to construct the full URL to the panoramic images.

For instance, given the base URL https://hss/panos, the application constructs image URLs in this format: https://hss/panos/{output}/{id}/{face}-{x}-{y}-{z}.jpg with the following parameters:

  • output: the output folder specified in the panorama converter tool
  • id: the id of the panorama feature
  • face: The specific face of the panorama cube (e.g., front, back, left, right, top, bottom)
  • x: The x-coordinate the tile within the face
  • y: The y-coordinate of the tile within the face
  • z: The z-coordinate of the tile within the face

Panorama: Icon Height Offset

Initially, panorama icons are shown at the height where the camera captured the image. The icon height offset property allows users to adjust the vertical position of these icons in the HSS client application. Using this property, you can shift the icons vertically by a number of meters.

This property is especially useful when panoramas are captured from elevated positions. For example, if panoramas are taken with a sensor mounted approximately 2.5 meters above the ground (such as on top of a car), the icon height offset can be set to lower the icons to ground level.

Options for OGC 3D Tiles collections

备注

An OGC 3D Tiles Collection is a collection of OGC 3D Tiles models that, together, form a cohesive dataset and share the same metadata. HxGN Smart Sites will only show the elements in the collection when the user's view point is close enough.

An OGC 3D Tiles Collection is generated by the BIM Processor Tool which ships with HxGN Smart Sites. The tool divides a 3D model and creates a sub-model for each provided spatial extent. The tool also creates a replacement block model. The elements of the block model, the individual sub-models and the spatial extents are correlated by a unique ID. HxGN Smart Sites will replace elements of the 3D model with elements of the block model based on the unique ID.

Template URL

备注

The collection is defined by an index file which list the collection items by ID. The index file is generated by the BIM Processor Tool delivered with HxGN Smart Sites. It lists the IDs and spatial extents of the generated tilesets.

HxGN Smart Sites will use the value of Template URL and the IDs listed in the index file to resolve the URL to the individual OGC 3D Tiles models.

Template URL should:

  • be a valid URL
  • contains the placeholder "{ID}" to inject the item ID
  • refer to a root "tileset.json" file.

Block model

The block model is a low resolution representation of the collection.

The geometries of the block model are delivered over WFS.

  • Chose Enable fallback data to enable the replacement mechanism in HxGN Smart Sites. When disabled, the hidden elements will not be replaced.
  • URL refers to the WFS endpoint.
  • Feature Type Name refers to the WFS's feature type.
  • Security define the security mechanism enforced by the WFS, see Security Options.

Google 2D Tiles: Map Type

This option determines the type of the base map to use. It can be one of three options: