The Usage menu provides the following sub menus:
The Site Status View displays within a map all Reference Sites locations configured in GNSS Spider. It is designed to be displayed to Administrators of SBC and to customers (privilege: User) who have a corresponding subscription. The Site Status update depends on the received site raw data status. This requires a continuous connection to the GNSS Spider Network Server.
In the Site Status View there is an action bar 
placed at the top right side of the Map View. It provides the functionality to display or hide the sites layer, and the regions layer. By default, the “Display site layer” action button is active and shows all sites configured in GNSS Spider Site Server. The “Display region layer” is not active by default.
The following status and action buttons are provided on the Site Status View action bar:
The Site Status View consists of a map display and a list of sites. All sites configured in the GNSS Spider Site server appear on the map and as well and on the List view. Callouts are providing additional site properties like Site code, Site name, Marker number, Marker name, Latitude, Longitude, Height, Receiver type, Receiver Serial Number, Antenna type, Antenna Serial Number and Antenna height. Details about the site connectivity and the Network fixing status are also shown.
The following functionalities are displayed on the Map View:
Site markers in the Map View are coloured depending on their site status. The following status indicator states are supported:
The Site statuses Connected and Disconnected only appear to users who have subscribed to the Site Status product .The Network status Fixed only appears to users who have subscribed to the Network Processing Status.
Site overview provides the available reference sites on the login page without any site information i.e. site status and callouts. Users can enable or disable site overview on the login page based on the checkbox value under Settings->System->General.
In order to include the site overview map into any other web application, just use a HTML command like:
"<iframe src="Frontend URL/SiteMap/SiteMapPublic" width="400" height="150"></<iframe>"
Alternatively the link "Frontend URL/SiteMap/SiteMapPublic" is supported as well.
In both cases Frontend URL is the SBC frontend URL as configured under Settings->System->Infrastructure.
Example:
http://localhost/sbc/SiteMap/SiteMapPublic/
The latest GNSS Spider Sites, Clusters and Cells details and status information are automatically synchronized with SBC. These contain site properties manually set by Spider operators, the Site states depending on the status of the raw data stream provided by a GNSS receiver, and the manually configured Clusters and Cells from GNSS Spider. Information about the Automatic Cells generated by Spider for a rover is also synchronized in Real-Time with SBC.
In order to get Site details into SBC it is mandatory to configure the SBC Central Server to connect to the right host, on the Network Server. Set the IP-address or hostname at Tools – Configuration – General.
The Rover Status View lists all GNSS rovers connected via GNSS Spider and displays them in a map. The Rover Status is designed to process and display data of multiple input streams in real-time. The status and position update depends on the received real-time data.
The IP port 80/443 is utilized by SBC to enable the data flow of the Rover Status View between the SBC Proxy Server computer and the accessing client Web browser.
On top of the Table View, a summary is displayed clarifying the total number of connected rovers and the distinction between the percentages of rovers with a Network Solution ("Fixed (Network)") and rovers with a Single Base Solution or SBS ("Fixed (Single Base)"). On the map, Network fixed rovers are marked in green, whereas SBS ones are marked in blue.
The table view provides major details of connected GNSS rovers in a paginated grid view. Search is related to all displayed columns.
| Column | Description |
|---|---|
| NMEA and Fixing |
The quality indicators define which one of the rover icons is displayed. For a detailed description of the NMEA GGA message and the Quality indicator, see the chapter on NMEA GGA definition.
Connected rovers are shown as icons in the map. Fixed icon appears in blue or green dependent if it is single site or Network fix. RTK fix at rover (indicator = 4). Green if network fix is available; blue if single site. DGPS or Navigated PPS mode at rover (indicator = 2, 3) Navigated SPS mode at rover (indicator = 1) No fix status information available at rover (indicator = 0) Float RTK fix at rover (indicator = 5) Invalid NMEA fixing status value (indicator >= 6)
If SBC did not receive any new rover information for 5 minutes, the rover status is considered as outdated. This outdated state is indicated by the hourglass symbol in the "Quality" column. Usually every 30 seconds (called "Keep-Alive") a new rover status is received from Spider unless there was already a change of the rover position earlier. Spider disconnects rovers that are connected too long without any "Keep-Alive" or "Update" but in special cases like custom timeout settings or network interruptions between Spider and SBC, it might happen that rovers are still shown in the Rover Status View while they are already disconnected. Those connections usually get cleaned after 10 minutes.
|
| User name | As configured in SBC |
| Full name | Differs from User name only if explicitly set to the personal data of a particular user. |
| Duration | A running timer, which starts when a rover user is first-time connected. |
| Update | Time of last received data set. |
|
Satellites Ref./Rover |
1st number: Number of satellites tracked at the rover as received from the rovers NMEA message. 2nd number: depending on the RT Product type:
|
| Ref. Station RTCM/NMEA | ID of the reference station sent to the rover. |
| Distance | 3D distance between rover and reference position. |
In the Live Usage View there is an action bar
placed at the top right side of the Map View. It provides the functionality to display or hide the sites layer, the Regions, Clusters and Cells layer, and the Rover Events view.
By default, the “Display site layer” action button is active and shows all sites configured in GNSS Spider Site Server.
The “Display Regions, Clusters and Cells” layer and “Rover Events” view are not active by default.
The following status and action buttons are provided on the Live Usage View action bar:
Similar to Regions, the Site Status view appears as an optional layer in the Rover Status View. Once selected, it displays all GNSS Reference Stations configured in GNSS Spider together with all connected GNSS rovers in the Map View. The rovers are displayed automatically in the Live Usage View, if a successful connection was done to the Spider RTK corrections data streams.
Connected rovers appear in the Map View indicated by their currently transmitted quality indicator. Callouts can be displayed either by clicking on the rover icon in the Map View or by clicking on the Rover Details icon in the Rover Table View. They provide additional rover user details, such as User name, Rover Type, position, satellites at Master Site, satellites at Rover, RTCM Ref. Stn. ID, NMEA Ref. Stn. ID, distance, RT Product etc.
The following features are displayed on the Map View:
The Live Usage View provides also the possibility to visualize in additional map layers all manually configured Clusters and Single Cells in GNSS Spider Network Server, and the Automatic Cells generated by GNSS Spider Network Server to send out corrections for the connected rover users. The list of Clusters, Single Cells and Regions is displayed under the custom control button “Display Regions, Clusters and Cells” under their corresponding tabs.
The Clusters and Single Cells status/configuration are synchronized in Real-Time between the Network Server and SBC as soon as the Network processing is started or restarted in case of changing the configuration of a Cluster/Cell.
Only the Administrator, Support viewer and Operator user privileges have access to visualize the Clusters, Single Cells and the Automatic Cells on the “Usage > Rover Status” view.
Display of Regions, Clusters, Single Cells and Automatic Cells:
The Live Usage View provides the possibility to visualize and filter the Rover events generated by GNSS Spider Network Server for connected rover users. The filtering options are displayed under the custom control button “Show rover events - Rover events” under its corresponding tabs. The rover events can be filtered by User Events, Unknown User Events, and All Rover Events, but also by the last 5, 10, or 30 minutes, and the last 1000, 3000, or 5000 Rover Events.
The Rover events are forwarded in Real-Time from the Network Server to SBC as soon as a log event has been triggered by the rover user. All the forwarded rover events are displayed in a right panel on the “Usage > Rover Status” page in SBC.
Only the Administrator, Support Viewer and Operator user privileges have access to visualize the Rover events on the “Usage > Rover Status” view.
In order to display GNSS Rover data at the SBC Rover Status View the GNSS Spider network server needs to connect to the SBC Proxy Server. Please check also the GNSS Spider workflow diagram for further information about used TCP/IP ports that might need to be considered for firewall configuration. For this purpose it is necessary to set SBC Proxy Server Connection at Spider Network Server – Tools – Configuration – General properly.
The following status indicator states are supported:
Connection to SBC Proxy Server or GNSS Spider Network Server not established.
Establishing connection to SBC Proxy Server.
Connection to SBC Proxy Server and GNSS Spider Network Server established but no incoming data received. Receiving data.
The Rover Status View in SBC is license protected. To enable this feature please order: Spider Web Service - Real-Time Status (812435)
This feature allows extracting business relevant information regarding rover user connection details. Data basement is the Logging Service database which is one component of a GNSS Spider installation.
Reports are only generated on demand. A request requires a time period and one or multiple user names or subscription-IDs. Output is a brief statistics summarizing about major rover user connection parameters. Usage reports consist of following logical sections:
Properly running User connection reports within SBC requires the following:
The time period for which user connection data will be extracted from the Logging data base is defined by start date and end date. Here the time zone of the Central Server installation is used which may differ from the browser's timezone. The maximum supported time span is 3 months.
A Time Selector provides the possibility for quick selection of the time period. The quick selection takes Today as maximum selectable end date.
Selector options are:
The selected start and end dates are displayed next to the selector.
Together with some additional details all user names and subscription-IDs are listed in an overview similar to the subscription overview . Search and sorting is fully supported for this view. The first column offers single and multiple user or rather subscription selection. As soon as any change happens to the time period or to the user selection the resulting connection statistics will be generated based on the input data.
The Report results are displayed in a tab view showing Connection Summary on one tab and Connection List on the other. Connection Summary is always displayed as the initial result view. Switching between the tabs is possible.
Clicking the symbol is expanding the result section to full page view. In this mode the result section is expanded covering the complete page between main menu bar at top and bottom line. The result section can once again be minimized to the original mode.
As a quick result without providing all connection records stored in the GNSS Spider Logging data base, SBC returns a brief connection statistics. Section Request Summary contains details about the input data of the report generation. Section Network Performance Indicators provides the distribution of the three correction types on a percentage basis. Furthermore some numerical indicators summarizing the corrections availability according to the input data are provided.
The three portions of a doughnut chart represent the distribution of GNSS correction data based on all rover user connections contained in this report. It's distinguished between:
This option allows exporting all connection records from the GNSS Spider Logging data base to an Excel Workbook .XLSX file. The data content is very similar to the General Connection logs of GNSS Spider. Generating the XLSX report can take several seconds up to a minute depending on the number of requested subscriptions and the way of the distributed installation of the GNSS Spider components.
The naming convention of downloaded XLSX file is:
GL_startdate(yyyymmdd)_enddate(yyyymmdd).xlsx
XLSX File downloads are following the default download path as defined in the browser settings.
Following connection details are written to XLSX connection report:
| Connection ID | Rover connection Id |
| Subscription ID | Subscription Id |
| Article No. | Article number |
| Subscription Owner | User name of subscription owner. |
| Company | Company associated with rover user. |
| Rover Username | User name of authenticated rover user entity. |
| Rover Type | Rover type |
| Start Time | Start date and time of the connection between rover user and Spider RTK server. |
| End Time | End date and time of the connection between rover user and Spider RTK server. |
| Time Zone | The time zone of the connection start and end dates. |
| Duration | Duration of the connection between rover user and Spider RTK server. |
| Lat | Latitude of first coordinate that was received from the rover user via NMEA GGA message. |
| Long | Longitude of first coordinate that was received from the rover user via NMEA GGA message. |
| Height | Height of first coordinate that was received from the rover user via NMEA GGA message. |
| TTFD | Time to first data |
| No Corr | Duration without any GNSS correction data. |
| Single Site Corr | Duration where only single site corrections were available. |
| NRTK | Duration with GNSS network correction data like MAX, i-MAX, VRS, etc. |
| RTK Server | RTK host server name |
| Detailed Connection Log Available | Indicates whether a Detailed Connection Log has been generated for this event type. |
The tab Connection List displays all the connection records in a list view based on the selected input data. The header contains details about the input data of the report generation.
The list view provides following details of connections in a paginated grid view:
| Column | Description |
|---|---|
| Subscription Id | Subscription Id related to the User name and the real time product. |
| User Name | User name of authenticated rover user entity. |
| Company | Company associated with rover user. |
| Start Date | Start date and time of the connection between rover user and Spider RTK server. |
| End Date | End date and time of the connection between rover user and Spider RTK server. |
| Duration | Duration of the connection between rover user and Spider RTK server. |
| Latitude | Latitude of first coordinate that was received from the rover user via NMEA GGA message. |
| Longitude | Longitude of first coordinate that was received from the rover user via NMEA GGA message. |
| Height | Height of first coordinate that was received from the rover user via NMEA GGA message. |
| Click to visualize the Detailed Connection Logs written by GNSS Spider. It allows a comprehensive analysis of connection events. |
All columns except Counting Number, Latitude, Longitude and Height are sortable. Search functionality is not supported for this view.
For Administrators, Operators, Support Viewers, and for Dealer and Sales Organisation Administrators, an overview of the Post Processing Services Usage is available under Usage > Post Processing, for billing and informational purposes. The information provided by this page concerns the Post Processing requests triggered by SBC Users: RINEX and Virtual RINEX Data requests, Coordinate Computations and Coordinate Transformations.
The RINEX Data Availability Indicator (chart) button is displayed at the top right corner of the Post Processing page. It allows all SBC privileges the possibility to verify the RINEX data availability for the last 30 days.
- The SBC Administrator and Operator have an additional option to export the RINEX data availability values for the entire history to an Excel Workbook.
Like in the Real Time page, it is possible to select a time span and some specific users, for which information about the triggered Post Processing requests will be displayed. The time and users selector is structured in the same way as in the Real time page.
After setting the required filtering options, in the Post Processing page, four tabs are displayed: one for each of the Post Processing services offered by Leica Spider Business Center.
Each tab, when selected, displays a table, dedicated to the corresponding Post Processing service. Each table contains relevant information about all requests of the corresponding type. Requests triggered by the selected user(s) in the selected time span are displayed. The displayed information varies according to the selected service, hence, the columns in each table differ, according to what is relevant for each of the post processing services.
- Viewers of the Post processing Services Usage Statistics have the possibility to export the visualized content to CSV, so that it is easier for them to use the statistics for further purposes. Two options are available: