reviewed on 10/04/2026 based on 8.0.0.220
to do: add potential links highlighted in purple
Purpose
As the smallest instance, Products form the data basis of Articles, and thus for other components of the Service Data management. End users receive specific data streams or services by subscribing to articles containing specific products, after passing authentication and authorization checks from SBC.
The Products are seperated into two pages:
-
Real-Time Products. They relate directly to GNSS Spider Network Server RT Products configuration.
-
Other Products. This includes three product types: GNSS Spider Status, GNSS Post-Processing, and Customized products.
Real-Time Products
This section shows all RT Products configured on the GNSS Spider Network Server (NWS) connected to SBC. It updates automatically when RT Products change or new ones are created. RT Products that have been deleted on the NWS are indicated accordingly.
RT Product Overview
The overview page displays all RT products configured on the GNSS Spider NWS. The overview table displays only a subset of the most important properties, which are:
-
Status
-
Network Server name
-
Network Server host
-
RT Product name
-
RTK server host
-
Type
-
Message type
-
Mount point
and are highlighted in the tables below.
RT Product Details
The real-time product’s properties are organised into groups. Depending on the configuration some properties will be empty.
Infrastructure Setup
|
Parameter |
Description |
|---|---|
|
RT Product name |
The name of the RT product as configured on the GNSS Spider NWS. |
|
Network server host |
The hostname, IP address or DNS name of the machine running GNSS Spider NWS. The displayed information depends on the local configuration of the GNSS Spider NWS host. |
|
Network Server name |
The locally defined GNSS Spider NWS name. Only visible in the overview table. The displayed information depends on the local configuration of the GNSS Spider NWS host. By default this will often be “Local Network Server”. When connecting multiple Network Servers to one SBC, it is recommended to use some meaningful name, e.g., “Primary System NWS”. |
|
Status |
Current state of the RT product in NWS displayed via SBC:
Note: If products were deleted from SBC, both active and inactive products reappear after the next sync, while deleted products are permanently removed. |
|
RTK server host |
The hostname, IP address, or DNS name of the machine hosting the GNSS Spider RTK Proxy Server. |
|
TCP port |
The TCP port used by the RT product, e.g. when provided via Ntrip or TCP/IP. |
|
Mount point |
The Ntrip mount point of the RT Product from NWS. Displayed only for RT products configured as Ntrip; otherwise, it remains empty. |
Real Time Product Settings
|
Parameter |
Description |
|---|---|
|
Site/Cell/Rover user name |
Name of the reference site, cell, or rover, depending on the selected Type. |
|
Authentication |
The type of authentication required for the user to access the data stream (e.g. “Ntrip” or “GPUID”). |
|
Message type |
The selected Message Type of the RT Product from NWS, including Network RTK method descriptor, message format, RTCM version, and main message type numbers for RTCM message formats. |
|
RTCM version |
The version of the RTCM standard used by this product (for example, 2.x or 3.x). |
|
Target coordinate system |
The coordinate system for which RTCM transformation messages are sent to the rover with the correction stream. |
|
Type |
The RT product type: Single site, Nearest site, Multiple sites, Single cell, Automatic cell, and Single rover (NMEA redirect). |
|
Send real time message to |
Data channel used to send the RT product data stream (e.g., “Ntrip-Client”). |
|
Maximum distance to provide corrections |
Maximum allowed distance between rover and reference site. Corrections are denied if the limit is exceeded. |
|
Prevent search during rover connection |
When selected, the search for the master site (Automatic Cell) or nearest site (Nearest Site RT Products) occurs only at connection start, not during the connection, when, e.g., satellite availability changes. |
|
Fallback when network is not available |
Switches to a single-site solution when network RTK quality is insufficient and the single site provides better satellite availability. |
|
Send NULLANTENNA |
Indicates if corrections for this real time product are reduced to the antenna reference point (ARP) of the reference station antenna. If this is the case, the rovers must choose NULLANTENNA as the reference station antenna. This option is forced for all network correction methods (MAX, i-MAX, Virtual RS and FKP) and Nearest Site. |
|
Re-check if rover moves more than |
Distance threshold that triggers re-evaluation of the selected nearest site or automatic cell. Prevents frequent switching when the rover is near equal distances between sites. |
|
Fallback when rover-master distance is shorter |
Switches to a single-site solution when the rover is within a defined distance of the master site, where single-site RTK is more suitable than Network RTK. |
|
Fallforward enabled |
Automatically switches back to the network RTK solution once it becomes available or reaches sufficient quality. If disabled, the rover remains on the single-site solution after a fallback. |
|
Code smoothing |
Indicated if code smoothing is activated for the RT Product. |
|
Satellite system |
Lists enabled satellite constellations (GPS, GLONASS, BeiDou, Galileo, QZSS). |
|
Coordinate reference frame |
The coordinate reference frame to which corrections refer to. |
|
Emulate Leica receiver |
If checked, corrections for this real-time product are adapted to emulate a Leica manufactured receiver. This setting does support all rover equipment that is capable of handling Leica reference station data, but might not be capable to handle some of the other manufacturers receivers present in an inhomogeneous network, to make full benefit of GPS and GLONASS data. |
|
Reference frame distortion smoothing |
When this setting is enabled, distortions between reference frames of Physical and Product Marker coordinates are smoothed. |
RT Product Update & Deletion
Editing or updating RT Product details is not possible. You cannot create an RT product. The information shown on this page is the synchronised data as exchanged with the GNSS Spider Network Server. Any change of a real-time product has to be done on the NWS itself.
Deletion has restrictions: a product assigned to an article cannot be deleted. For more details, see also the “Status” section in https://hexagon.atlassian.net/wiki/spaces/GSOH/pages/46049656917/Products#RT-Product-Overview.
Deleting Real-Time Products in SBC does not affect their existence on a Network Server.
Product to Article assignment
You can assign a real-time product to an Article from the properties dialogue of the real-time product.
On the Articles tab, click the “Select articles” icon at the top right of the page to assign or unassign this product to/from Articles. From here, you can:
-
Assign this product to one or several articles:
-
Click the “Select articles” icon to open the full Article list. The list shows headers: Status, Article Name, Article Number, Subscription Period, Consumption Limit, etc.
-
Select one or more products, then click “Close” to confirm.
-
-
Unassign this product from one or several articles:
-
Click the “Delete” icon on the right to remove a product.
-
Other Products
These products include all products not listed in Real-Time Products. They include Spider NWS reference site status, rover real-time status, post-processing services, and custom services.
These products control access to specific pages or menus in the SBC user portal. Without them, the related UI elements for this product use remain hidden from end users.
Product Overview & Details
|
Parameter |
Description |
|---|---|
|
Status |
Following status available:
|
|
Product Type |
Defines the category of the product (GNSS Spider Status, GNSS Post-Processing, Customized). |
|
Product Name |
Name of the product as shown throughout SBC. |
|
Description |
Short description explaining the purpose or functionality of the product. |
Product Types
Below are detailed explanations of the differnt types of products.
GNSS Spider Status
|
Product Name |
Description |
|---|---|
|
Site Status |
|
|
Rover Status |
|
|
Network Processing Status |
|
GNSS Post-Processing
|
Product Name |
Description |
|---|---|
|
RINEX Data Access (Basic) |
|
|
RINEX Data Access |
|
|
Virtual RINEX Access |
|
|
Coordinate Computation KINEMATIC |
|
|
Coordinate Computation STATIC |
|
|
Coordinate Transformation |
|
Customized
Customized products can be configured by the SBC Administrator. These products are mainly used to build up a connection to non-Spider products, with the product name as link between SBC and external services for example a 24 hour support hot-line. Customized products are not connected to any data.
Other Product Creation & Update & Deletion
Creation applies only to customized products. You can create and update any customized product except its type and status, which are fixed as “Customized” and Active
Updates are limited to descriptions if the product type belongs to GNSS Spider status or GNSS Post-Processing. Product-to-article assignments exist for all three types and matchhttps://hexagon.atlassian.net/wiki/spaces/GSOH/pages/46049656917/Products#Product-to-Article-assignment.
Deletion rules depend on the product type:
-
GNSS Spider Status: cannot be deleted
-
GNSS Post-Processing: cannot be deleted
-
Customized: can be deleted if unassigned to an article
Remove a product from Articles before deleting.