Leica Spider Software Suite PDF

Leica Spider Software Suite
Technical data
Leica Spider Software Suite – Technical Data 1

Introduction
This brochure contains important technical data regarding Leica Spider Software Suite.
Read carefully through the Technical Data.
Trademarks  Windows is a registered trademark of Microsoft Corporation in the United States and
other countries
All other trademarks are the property of their respective owners.
Validity of this This brochure applies to the Leica Spider Software Suite.
brochure
myWorld@Leica Geosystems (https://myworld.leica-geosystems.com) offers a
wide range of services, information and training material.
With direct access to myWorld, you are able to access all relevant services whenever
it is convenient for you, 24 hours a day, 7 days per week. This increases your efficiency
and keeps you and your equipment instantly updated with the latest information from
Leica Geosystems.
Service Description
myProducts Add all Leica Geosystems products that you and your company own.
View detailed information on your products, buy additional options or
Customer Care Packages (CCPs), update your products with the latest
software and keep up-to-date with the latest documentation.
myService View the service history of your products in Leica Geosystems Service
Centres and detailed information on the services performed on your
products. For your products that are currently in Leica Geosystems
Service Centres view the current service status and the expected end
date of service.
mySupport Create new support requests for your products that will be answered
by your local Leica Geosystems Support Team. View the complete
history of your Support and view detailed information on each request
in case you want to refer to previous support requests.
myTraining Enhance your product knowledge with the Leica Geosystems Campus -
Information, Knowledge, Training. Study the latest online training
material or download training material on your products. Keep up-to-
date with the latest News on your products and register for Seminars
or Courses in your country.
myTrusted Offers increased productivity while at the same time providing
Services maximum security.
 myExchange
With myExchange you can exchange any files/objects from your
computer to any of your Leica Exchange Contacts.
 mySecurity
If your instrument is ever stolen, a locking mechanism is available
to ensure that the instrument is disabled and can no longer be
used.

Table of Contents
In this brochure Chapter
Contents
Introduction .................................................................................................................. 2
Table of Contents ......................................................................................................... 3
1 Overview ................................................................................................................ 6
1.1 Leica GNSS Spider .......................................................................................... 6
1.1.1 Spider Site Servers .................................................................................. 7
1.1.2 SpiderNET – Network RTK ....................................................................... 7
1.1.3 Spider Positioning Services ..................................................................... 8
1.2 Leica Spider Web Applications ........................................................................ 9
1.2.1 SpiderWeb – World-Wide-Web-Services .................................................. 9
1.2.2 Spider Business Center ........................................................................... 9
1.3 Leica SpiderQC ............................................................................................. 10
2 Leica Spider Suite System Architecture ................................................................ 12
2.1 Overview ...................................................................................................... 12
2.2 Description .................................................................................................. 14
2.2.1 GNSS Spider .......................................................................................... 14
2.2.1.1 GNSS Spider Client ............................................................................ 14
2.2.1.2 GNSS Spider Windows Services....................................................... 15
2.2.1.3 GNSS Spider SQL Database ............................................................... 17
2.2.2 Spider Web Applications ....................................................................... 18
2.2.2.1 SpiderWeb ........................................................................................ 18
2.2.2.2 SpiderWeb Windows Services ......................................................... 19
2.2.2.3 SpiderWeb SQL Database .................................................................. 19
2.2.2.4 Spider Business Center...................................................................... 20
2.2.2.5 Spider Business Center Windows Services ...................................... 21
2.2.2.6 Spider Business Centre SQL Database ............................................... 22
2.2.3 SpiderQC............................................................................................... 22
2.2.3.1 SpiderQC Application ......................................................................... 22
2.2.3.2 SpiderQC Windows Service ............................................................. 23
2.2.3.3 SpiderQC Database ........................................................................... 23
2.2.4 CLM ...................................................................................................... 23
2.2.4.1 Client License Manager...................................................................... 24
2.2.4.2 Local License Server Windows Services .......................................... 25
2.2.4.3 CLM Database ................................................................................... 25
2.3 Installation Requirements and System Performance ..................................... 26
2.3.1 Supported Virtualization Environment ................................................... 26
2.3.2 Operating System and other Software Requirements ........................... 26

2.3.3 Hardware Requirements ....................................................................... 26
2.3.4 System Performance ............................................................................. 28
2.4 Security ........................................................................................................ 29
2.4.1 Overview............................................................................................... 29
2.4.2 General Security Aspects ...................................................................... 30
2.4.3 Distributed Installation in a Corporate LAN ........................................... 33
2.4.4 General Data Flow ................................................................................ 37
3 Leica Spider Software Suite Features ................................................................... 39
3.1 Leica GNSS Spider ........................................................................................ 39
3.1.1 General Layout ..................................................................................... 39
3.1.1.1 Views and Menus .............................................................................. 39
3.1.1.2 General Settings................................................................................ 40
3.1.1.3 Management ..................................................................................... 41
3.1.1.4 Tools ................................................................................................. 46
3.1.2 Site Server ............................................................................................ 49
3.1.2.1 Configurations .................................................................................. 49
3.1.2.2 Site Creation ..................................................................................... 50
3.1.2.3 Site Configuration ............................................................................. 52
3.1.2.4 Receiver Configuration ...................................................................... 56
3.1.2.5 File Products Service ......................................................................... 59
3.1.2.6 Real Time Product Service ................................................................. 62
3.1.2.7 Monitoring System Performance ....................................................... 63
3.1.3 SpiderNET ............................................................................................. 69
3.1.3.1 General Configuration ....................................................................... 69
3.1.3.2 Network Processing .......................................................................... 71
3.1.3.3 Real Time Product Services................................................................ 74
3.1.3.4 Monitoring System Performance ....................................................... 77
3.1.3.5 RT Connection Audit ......................................................................... 81
3.1.3.6 Reference Frames and Coordinate Systems ...................................... 84
3.1.4 Spider Positioning ................................................................................. 86
3.1.4.1 Real Time Positioning ........................................................................ 86
3.1.4.2 Post Processed Positioning ............................................................... 88
3.2 Leica Spider Web Applications ...................................................................... 90
3.2.1 Spider Business Center ......................................................................... 90
3.2.1.1 Views and Menus .............................................................................. 90
3.2.1.2 Preferences ....................................................................................... 91
3.2.1.3 Service Data Management ................................................................. 99
3.2.1.4 SBC User Features ........................................................................... 108
3.2.1.5 User Management ........................................................................... 109
3.2.1.6 Tools ............................................................................................... 113
3.2.1.7 SSL Configurator ............................................................................. 116

3.2.1.8 API .................................................................................................. 117
3.2.2 SpiderWeb .......................................................................................... 119
3.2.2.1 Views and Menus ............................................................................ 119
3.2.2.2 Configurations ................................................................................ 119
3.2.2.3 Site Management ............................................................................ 125
3.2.2.4 Rinex Job Service ............................................................................. 129
3.2.2.5 Virtual RINEX service ....................................................................... 131
3.2.2.6 Computation and Transformation Service........................................ 131
3.2.2.7 Results Menu .................................................................................. 133
3.2.2.8 Statistics ......................................................................................... 138
3.2.2.9 Tools ............................................................................................... 140
3.3 Leica SpiderQC ........................................................................................... 144
3.3.1 General Layout ................................................................................... 144
3.3.1.1 Views and Menus ............................................................................ 144
3.3.1.2 General Settings.............................................................................. 144
3.3.1.3 Limit Checks and Messaging ............................................................ 162
3.3.2 Manual Data Quality Check ................................................................. 164
3.3.2.1 Quality Check .................................................................................. 164
3.3.2.2 Quality Check (Comparison) ............................................................ 165
3.3.2.3 SNR Analysis ................................................................................... 166
3.3.2.4 Multipath Analysis ........................................................................... 166
3.3.2.5 Tracking Analysis ............................................................................. 166
3.3.2.6 Receiver Clock Analysis.................................................................... 166
3.3.2.7 Residual Analysis ............................................................................. 167
3.3.3 Automated Analysis of Reference Station Data .................................. 168
3.3.3.1 Automatic Quality Check ................................................................. 168
3.3.3.2 Web Page and Status Information ................................................... 168
3.3.3.3 Graphs and Reports ........................................................................ 168
3.3.4 Other Automated Services .................................................................. 170
3.3.4.1 Network RTK Analysis ..................................................................... 170
3.3.4.2 Coordinate Analysis......................................................................... 171
3.3.4.3 Inclination Analysis .......................................................................... 172
3.3.5 Tools .................................................................................................. 173
3.3.5.1 Ionosphere Plots ............................................................................. 173
3.3.5.2 Analysis of Spider Rover User Logs ................................................. 173
3.3.5.3 Other Tools ..................................................................................... 176

1 Overview
Flexible & Leica Spider Software Suite provides a highly customizable platform for GNSS
customizable infrastructure. It supports applications like surveying and GIS, machine construction,
precision farming, hydrographic survey and others with high accuracy corrections in
real time or post processing. Leica Spider Software Suite can also manage large
seismic networks and provide high speed real time monitoring of critical
infrastructure such as buildings, bridges, mines and airports. With a modular
architecture, it can be easily scaled to suit your application and budget, large or
small.
Versatile With Leica Spider Software Suite, you have the flexibility and power to make your
Architecture – infrastructure the way it should be. For RTK networks the IT infrastructure is rarely
reliable and secure built from the scratch. Therefore, Leica Spider Software Suite is designed to blend
into your existing IT environment with minimum installation and configuration effort.
Security is crucial for systems exposed to the Internet, and was a key focus when
developing Leica Spider Software Suite. Thus, Leica Spider Software Suite will lower
your total cost of ownership (TCO), but not your security.
Flexibility counts Leica Spider Software Suite’s modular server architecture allows for compact
centralized as well as highly distributed installations with maximum reliability and
redundancy. With the stand-alone graphical user interface application supervisors
can work at distant locations, even at home, as well as at the main control centre.
It’s easy to arrange a friendly duty schedule that suits everybody perfectly.
Security is The unique Leica Spider proxy server technology provides maximum security for
fundamental RTK/DGNSS data distribution, as well as for the Spider Business Center and
SpiderWeb internet portal services. Secure firewalls can protect the core systems
and data, whilst the services are easily accessible from the internet.
Reliability is Leica Spider Software Suite servers run as services within the operating system. They
essential are started automatically when the computer is (re-)booted without the user logging
in. GNSS Spider architecture supports setups with redundant processing
configurations and the built-in watch dog monitors all threads and operations.
Integrated Leica Spider Software Suite fully integrates the Leica Reference Network Solution
Solution and the Leica Monitoring Solution.
It works seamlessy with Leica GR series, GRX1200 series and GMX900 series as well
as a range of legacy and third-party GNSS receivers at no additional costs.
Leica GNSS Spider smoothly interfaces to other Leica software solutions such as
Leica GeoMoS or Leica Infinity for monitoring, quality control and other applications.
1.1 Leica GNSS Spider

Overview GNSS Spider is an integrated software suite for centrally controlling and operating
GNSS reference stations and networks. GNSS Spider is modular and scalable and can
be tailored to suit various GNSS surveying, seismic and strucutural monitoring
applications.
The advanced SpiderNET solution provides long-range high-accuracy Network RTK
and centralized data distribution. The Spider Business Center portal provides
powerful and secure access management.

Reliable – Once configured and started, all services run automatically and autonomously
Continuous & integrated within the operating system – fail-safe for highest reliability. Data for
Automatic post processing is continuously archived, monitored and distributed. Rovers connect
to various Network RTK or DGPS services for real time positioning using a variety of
flexible methods, automatically receiving the best available solution.
Secure – Control & Monitor and control your system locally or from a remote location with no additional
Audit tools needed. Control and view online who accesses your services. Receive automatic
event Email and messaging on system status anytime and anywhere.
Scalable With GNSS Spider you only invest in what is necessary for your current needs. As
Infrastructure requirements change and demand grows, it is easy to add stations extending your
Solution network coverage or add extra capabilities enhancing your scope of services.
Your Benefits  Efficient & secure, allowing you to focus on your strengths
 Convenient to use local or remote
 Reduces infrastructure and maintenance costs
 Upgradeable and expandable solution to protect initial investment
1.1.1 Spider Site Servers

Efficient – Easy to Use the setup wizard or simple drag & drop to create new sites. With just a few
Setup & Configure clicks you can create file products and services for RINEX logging with quality control
and FTP or X-pos distribution. Likewise, comfortably add real time data services with
choice of a variety of communication channels and data formats.
1.1.2 SpiderNET – Network RTK

Technology to the Using GNSS Spider with SpiderNET for continuous network processing provides
MAX consistent high accuracy and improved RTK performance over the entire network
region. This allows for even larger distances between your reference stations thus
covering large areas with a minimum number of stations. Leica MAX Master Auxiliary
corrections and other methods, deliver customized services in a wide range of
formats with the performance and reliability you need – it’s the ideal “Win-Win”
situation.
Smart The SpiderNET state-of-the-art processing kernel applies the latest in zero-
performance and difference processing algorithms and the proven Leica SmartCheck technology to
MAX productivity deliver outstanding reliability and performance. The entire process runs continuously
and automatically to provide high quality RTK & DGPS corrections in order to
maximize productivity in the field. A redundant system as backup or for
reconfiguration is easy to setup for ensuring continuous availability without any
downtimes.
Network corrections can be provided using the newest standard RTCM V3.2 MSM
network corrections, as well as a variety of other methods and formats to suit a
wide range of rover systems. Using Leica SmartStation, even a Total Station can
benefit from the latest in Network RTK technology. Whichever method is used,
whatever application you have, SpiderNET offers longer range, consistent accuracy,
higher reliability and faster RTK initialization times that will increase your
productivity.

Supported MAX – Moving with the Standard
Network RTK Leica MAX network corrections provide superior performance over all other existing
Methods known methods for Network RTK, especially when combined with rovers using Leica
SmartRTK technology. This method is ideally suitable for bi-directional as well as
broadcast only services. Leica MAX uses the only fully industry-approved RTCM V3.1
Network RTK message format – a standard jointly driven by Leica Geosystems – the
leader in GNSS Surveying.
i-MAX – Individualized MAX

Leica i-MAX provides individually network corrected RTK data to the rover based on a
nearest station in various message formats and is ideal for supporting legacy GNSS
receivers. Results are always traceable to a true physical reference station.
Virtual Reference Station

The “Virtual Reference Station” method applies network corrections and transforms
the reference data and location to a virtual station near the rover. With a variety of
message formats, it is suitable for rover systems that support this method.
FKP – Flächen-Korrektur-Parameter
FKP or “Area Correction Parameters” work in both broadcast and two-way
communication modes and are suitable for compatible rover systems.
Your Benefits For the system provider:

 Continuous service even during maintenance periods
 Best reliability with Leica Smart- Check
 Dependable with data processing redundancy
 Live audit of field rovers in map views and traceability of any field survey
For the rover users:

 Increased coverage and availability
 Faster rover initializations
 Higher productivity
 Consistent high accuracy
1.1.3 Spider Positioning Services

Overview Using continuously streamed or periodically downloaded data, the Spider Positioning
module computes station coordinates automatically and continuously in real-time or
in post processing. With proven processing algorithms tuned to monitoring
applications, Spider Positioning provides excellent accuracy and reliability even with
single frequency receivers.
Integrated solution Spider Positioning results smoothly interface to Leica GeoMoS and/or Leica SpiderQC
for monitoring for further displacement analysis, integration with other sensors and notifications
applications based on configurable limit checks.
Designed to match Whatever movements you need to monitor Spider Positioning provides the optimum
your application solution in real time or post-processing. Spider Positioning is equally applicable to
reference station integrity monitoring and structural monitoring applications such as
bridges, buildings, volcanoes, oil rigs, dams and more.

1.2 Leica Spider Web Applications
1.2.1 SpiderWeb – World-Wide-Web-Services
Overview Leica SpiderWeb is an advanced solution for the convenient presentation of your
network and comprehensive post-processing data services over the internet.
Value added services assist with the convenient distribution and use of GNSS data sets from
individual stations or networks to users through standard web browser.
It ideally complements Leica GNSS Spider and SpiderQC, as well as any other
reference station solution producing data in RINEX format.
Securely managed SpiderWeb integrates smoothly with the Spider Business Center for secure
registration and login to access its value-added services. Secure HTTPS is supported.
Value added RINEX Jobs Service

services Provides convenient access to RINEX data by time interval, data rate and station(s) selection.
Powerful job management functions assist with convenient access and automated
data request for longer-term applications.
Virtual RINEX Service

Based on SpiderNET advanced technology, Virtual RINEX allows your clients to benefit
from network corrections also in post-processing applications.
Coordinate Computation and Transformation Service

The coordinate computation service delivers postprocessed and adjusted coordinates
in WGS84 and local datum by email. The data uploaded by the user is processed
relative to multiple manually or automatically selected reference stations. Integrated
blunder detection, coordinate adjustment and even use of Virtual RINEX ensure best
reliability.
Status and Quality Service

SpiderWeb smoothly integrates with SpiderQC to present data availability and
quality. Web pages with traffic light status, reports and graphs for each site as well
as SpiderQC real time NOVA (Network Online Visualisation of Accuracy) RTK network
residual error maps can be shown.
Easy – Flexible –  Online registration and subscription to services

Reliable  Integrated Google Maps™ for showing site locations
 Automatic or map based “point & click” site selection
 Easy localization of language and appearance
 Transparent tracing of user activities for billing
 Customizable content with different access levels allows to share pages with
internal staff or registered users or anyone
1.2.2 Spider Business Center

Overview The Spider Business Centre web portal is the integrated secure solution for online
subscription and management of all GNSS network services. It smoothly integrates
GNSS Spider and SpiderWeb services and allows you to complement them with your
own value adding benefits.
The Spider Business Centre provides you and your clients with tools to view, register
and manage real time and post-processing services. It is designed to monitor service

usage, to enable exchange of data, to view online network and rover status and
assist with support & accounting.
It reduces the time required for administration, thus lowering your operational and
maintenance costs. With using the Spider Business Centre you can fully focus on
growing your business and achieve the best return on your investment (ROI).
Compose unique Tailor your individual service offerings into unique value-added articles that best
Articles match your capabilities, business model and local market needs.
 Use all GNSS Spider & SpiderWeb services
 Add time or geographic attributes to be applied automatically by the
authorization mechanisms
 Complement articles with your own benefits
Capture the Customer information, including access credentials and service usage information are
information that valuable for your business. The customizable registration form allows you to capture
you need the information from your clients that you require to operate and grow your
business.
With the Spider Business Center being an integral part of the whole solution, all this
information is securely managed in one central location.
Secure & The Spider Business Center portal is based on the proven secure GNSS Spider proxy
Adaptable client-server technology and can be smoothly integrated into existing web
portals.
 Web services can be accessed publicly
 All data and authentication services are securely operated inside your LAN
 A central database allows efficient and secure archiving of all your valuable
business information
 Allows for flexible integration of the Spider Business Center into your own
corporate website or into SpiderWeb portal.
One solution for  Centralized, convenient and secure internet portal to access and manage your
all GNSS network complete service portfolio
services  For network RTK, post processing and custom network services
 Web based interface enables flexible access at anytime from anywhere for both
customers and system administrators
 Full transparency for you and your clients regarding current subscriptions and
their status
1.3 Leica SpiderQC

Overview Leica SpiderQC is the first choice Software for Quality Control and Performance
Analysis of GNSS Reference Station Networks to complement Leica GNSS Spider or
any other reference station software. It can analyze various GNSS raw and derived
data in a range of formats such as RINEX, SINEX, IONEX and NMEA.
Ensure your reference station network is performing at its peak using the
comprehensive quality checking features of Leica SpiderQC.
 Select the best location for your reference stations
 Evaluate the quality of data from your reference stations
 Visualize the performance of your RTK network and identify how your network
could be improved
 Be warned about site movements/vibrations in real time

Site Assessment Leica SpiderQC helps you to select the best location for your reference station. Use
and Quality it to evaluate code and phase multipath, check for RF interference and signal
Control attenuation, measure data quality and completeness and much more. Once the site
is installed, it continuously monitors the data quality in case changes to the site or
nearby environment cause it to degrade. Leica SpiderQC provides you with a
convenient overview of the data quality using e.g. traffic light status, graphs, reports
and web pages, email or SMS warnings.
Network RTK The Network Online Visualisation of Accuracy (NOVA) feature of Leica SpiderQC
Performance enables you to visualise the spatial and temporal quality of single base and network
Monitoring RTK positioning over your network. Real time maps show the distribution of residual
ionosphere and troposphere/ orbit error enabling you to monitor the network status
and identify problem areas in the network.
Reference Station Using Leica GNSS Spider RT Positioning, a fixed rover in your network or the Site
Integrity Monitor feature of Leica GR series receivers, Leica SpiderQC can monitor the quality
Monitoring and availability of corrections from the network. Statistics such as accuracy,
precision, availability, reliability and more can be used to quantify the integrity of the
service and warn if thresholds are exceeded so corrective action can be taken.
Deformation Use Leica SpiderQC to detect and visualise movements of your reference stations or
Monitoring other critical infrastructure. Leica SpiderQC integrates with a variety of high speed
real time and post processing positioning engines including Leica GNSS Spider and
Bernese. Together they provide a flexible monitoring system for reference stations,
bridges, dams, landslides and more. High precision tilt measurements from Leica
Nivel200 inclination sensors can be used to complement the GNSS derived data or
velocities of the GNSS antennae measured by Vadase application onboard Leica GR
series receivers.

2 Leica Spider Suite System Architecture
2.1 Overview
Overview Leica Spider Software Suite is a modular solution with a client/server architecture
running on Microsoft Windows operating systems. It features an intuitive
graphical user interface (GUI) whose components are designed to interact seamlessly
with standard Windows operating system procedures. The software suite can be
easily configured to establish permanent or temporary connections to local and
remote GNSS receivers either separately or simultaneously. The type of connection
will depend on the communication infrastructure available at the installation. Leica
Spider Software Suite is a modular package of server components allowing a central
or distributed installation of the servers.
Operation The local application of each Leica Spider Software Suite server runs as a standard
automation Windows service, which is launched automatically when Windows is started and,
therefore once all components have been properly configured, user intervention is
not necessary. Each Leica Spider Software Suite server can establish connection to
the receiver or other components automatically. Continuous open communication
lines are not required, although this is supported as well and required for all real-
time applications such as real-time positioning or network computations for Network
RTK.
GUI Client The GUI Client applications allow full control of remote Leica Spider Software Suite
Applications servers through an IP-based connection (dial-up or network link), thus relieving the
operators from the necessity of being at the server console to manage the network
of reference stations and all related services.
Those who are already familiar with Windows will find the Spider Software Suite
GUI applications very easy to learn and use. However, prior knowledge of Windows
is not required to quickly become proficient in using the Leica Spider Software Suite.
Comprehensive online help covering many details beyond the topics addressed in the
Getting Started section is also available for additional information for all Leica Spider
Software Suite components and functions.
SQL Database All components, the Spider Software Suite Servers and the GUI applications, access
the SQL databases or Leica proprietary database (in case of SpiderQC). These run as
Windows services (Microsoft® SQL Server®) and store system configurations, settings
and status information for sites and sensor data, active connections and data
products. These do not include the archived GNSS data products or other file
products. The data file products are stored in a user-definable folder structure,
which can be accessed independently using a standard file browser such as Windows
Explorer, even when Spider Software Suite Servers are not running.
Uninstalling Leica Spider Software Suite components will not delete product files and
directories; neither will it delete the SQL or proprietary databases.

Communications: Reliable communication is critical for GNSS reference stations and networks. GNSS
phone / cellular / Spider software polls the receivers and downloads data files; RTK and DGPS data are
GSM / wireless, transmitted from reference stations to RTK and GIS rovers. For centralized real-time
Internet etc. data distribution and network processing, raw data is required to be continuously
streamed from the receivers and sent to the different server components.
Note that the computer platform on which the GNSS Spider Site Server is installed
does not need to be co-located with a permanent reference station receiver.
Depending on the requirements and the available infrastructure, communication
between GNSS Spider Site Server computer and the reference-station GNSS receivers
can be by:
 Dial-up modem (landline/cellular/GSM/high-speed wireless);
 Internet, local or wide area networks (TCP/IP, Ntrip),
 Direct serial link (RS232)
Transmission of RTK and DGPS data directly from the receivers will usually be by
radio or phone modem.
Centralized transmission of RTK, DGPS or Network RTK can be done via radio or
phone modem, modem access router or the Internet.
System supervisors using the GNSS Spider GUI Client at remote locations will
normally connect the to the GNSS Spider server by Internet, Intranet or dial-up RAS
connections.
Leica Geosystems can suggest the most suitable communication solutions for your
applications and networks and provide full advice on ancillary equipment such as
modems, device servers, routers etc.
Data file GNSS Spider will transmit raw data and RINEX files immediately when available or at
distribution specified time intervals to one or multiple FTP servers for easy access by the GNSS
user community. Different files can be pushed to different FTP servers. With Leica
Spider Software Suite you have full flexibility.
For convenient and secure distribution of GNSS data sets from any network to
individual users via the internet we recommend using a web server application such
as SpiderWeb.
Command line With command line processing, you can launch an application or script. Users can be
processing notified by e-mail that data is available, data files can be sent directly to users.
Programs or scripts can be launched upon events such as communication failure or
low disk space.
System monitoring Leica Spider Software Suite checks the completeness and quality of all data
and data control downloaded or streamed from the reference-station receivers or delivered to the
end users. It also monitors the various communication links and the operation of
the entire system. Warnings are generated and e-mail messages can be sent to
supervisors if any unexpected events occur. Event log files are created. Leica Spider
Software Suite provides full information.
Leica Spider Leica Spider Software Suite is a modular solution with a client/server architecture
Software Suite that comprises the following distinct system components:
Components

2.2 Description
2.2.1 GNSS Spider
Overview The GNSS Spider software is a modular system with a client/server architecture that
comprises the following distinct system components:
 GNSS Spider Client
 GNSS Spider Services:
 Site Server
 Network Server
 Cluster Server
 RTK Proxy Server
 GNSS Spider Database (Microsoft® SQL Server® database)
2.2.1.1 GNSS Spider Client

GUI The GNSS Spider GUI Client is the graphical user interface (GUI), with typical
Windows™ look and feel that allows the operator to configure and monitor the
operation of the GNSS Spider Servers. It is always installed locally on the Site Server
and Network Server computer and can also be installed on multiple other remote PCs
or Notebooks. Regardless of the installation type – local or remote – the GNSS
Spider GUI Client always provides identical functionality and look-and-feel.
Any GNSS Spider GUI Client can be used to access other GNSS Spider server
installations on the same computer network or at other remote locations, to which
IP connections are available. This is a particularly useful tool in clustering

applications for large networks where several GNSS Spider – Site Servers are
configured to each manage a subset of the large network, or simply for remote
maintenance and control of your installation.
Access from a GNSS Spider GUI Client to the GNSS Spider Servers does require
knowing the GNSS Spider Server access password that is set during the installation
process and can be modified only through the locally installed GNSS Spider GUI
Client.
Multiple GNSS Spider GUI Clients can access a GNSS Spider server simultaneously,
such that a local GUI Client can be open, whilst one or more remote GUI Client users
connect, for example to inspect the system status.
GNSS Spider - GNSS Spider supports two distinct access levels for a GUI client user connecting to a
Client access levels GNSS Spider server – Administrator and Viewer access.
Administrators:
Administrators (e.g. system supervisors) have full control of GNSS Spider software
and the receivers. They can start and stop the various operations, create and change
configurations, set parameters and modes etc.
Viewer Level:
Other interested parties can be granted viewer-only rights. Viewers can inspect the
operation of the software, configuration parameters, system and receiver status etc.
Viewers can neither control a GNSS Spider server, nor modify its configuration or
operation.
2.2.1.2 GNSS Spider Windows Services

GNSS Spider – The GNSS Spider Site Server modul performs all standard reference station
Site Servers operations continuously and automatically:
 Controlling the receivers.
 Downloading and/or streaming data.
 Checking, converting, compacting, archiving and distributing data.
 Monitoring the entire Site server system.

 Performing POSITIONING computations.
It can be installed on the same computer as the Network Server, Cluster Server, RTK
Proxy Server or SBC servers, but it can also be installed on a separate computer that
is dedicated for the Site Server operations. It requires an SQL database be installed
on the same computer.
GNSS Spider – SpiderNET module comprises the following services:

SpiderNET  Network Server
 Cluster Server
 RTK Proxy Server
Network Server The GNSS Spider Network Server performs all network related data management and
configuration tasks and as such forms the central component of SpiderNET. It can
be installed on the same computer as a Site Server, Cluster Server. RTK Proxy Server
or SBC Server, but can also be installed on a separate computer dedicated for the
Network Server operations. It requires an SQL database be installed on the same
computer.
The Network Server provides the configurations for one or multiple Cluster Servers
and one RTK Proxy server. It also manages the data streams from one or multiple
Site Servers that are assigned to the Network Server for network computation. It
further manages the data streaming from the Site Server(s) raw data to the Cluster
Server(s) for network computation as well as the Site Server(s) raw data and Cluster
Server(s) network correction data to the RTK Proxy server for the real-time data
distribution to Rover users in the field.
For rover user access management, authentication and authorization for RT-Product
access, the Network Server connects to and communicates with the SBC server.
Cluster Server The GNSS Spider Cluster Server performs real-time computation of network
corrections and as such is the SpiderNET processor engine. It does not have a direct
graphical user interface connection and is configured through the Network Server. It
can be installed on the same computer as the Site Server, Network Server, RTK Proxy
Server or SBC Server, but it can also be installed on a separate computer that is
dedicated for the Cluster Server operation. It does not require an SQL database be
installed on the same computer.
Once it is configured and started by the Network Server, the Cluster Server receives
the raw data directly from the Site Server(s), performs the required network
computation tasks and streams out the network corrections back to the Network
Server for further distribution.
More than one Cluster Server can be assigned to a Network Server, which allows
built-in redundancy for network processing and distributes the processing load over
multiple core processors or computers for processing of larger networks.
RTK Proxy Server The RTK Proxy Server takes care of the secure real-time data distribution and as such
is the SpiderNET interface to the rover users in the field. It does not have a direct
graphical user interface connection for itself and is configured through the Network
Server. It can be installed on the same computer as the Site Server, Network Server,
RTK Proxy Server or SBC Server. It can also be installed on a separate computer that
is dedicated for the Proxy Server operation and may also host the SBC Proxy Server,
which is the recommended set-up. It does not require an SQL database be installed
on the same computer.
The RTK Proxy Server can be configured to provide single site real time corrections
computed directly from a raw data stream that is received from individual sites of a
Site Server, as well as network corrections received from the Cluster Server(s). Both

the single site data streams and the real-time network corrections are provided
through the Network Server, which manages all the data streams and connections.
The RTK Proxy interfaces with the communication media such as the Internet, serial
modems or access routers. It also hosts the Ntrip1 caster(s) and can act as an Ntrip
Server.
The RTK Proxy Server is designed such that it is ideally suited for a secure IT network
installation, where connections from an Intranet to the Internet are secured with
software and/or hardware firewalls creating a so-called DMZ (De-Militarized Zone).
Data Dispatchers The GNSS Spider Data Dispatcher (DD) ensures the GNSS Spider Servers and all GNSS
Spider clients that are connected to a server are synchronized. This is realized by
instant event distribution for each client or server action. Thus, any changes made
through one GNSS Spider client will be instantly available to other connected clients
or the server itself.
The Data Dispatcher also takes care of the general communication and real-time raw
data and network correction data distribution between the server components.
The Data Dispatchers run as Site Server and Network Server services threads.
GNSS Spider –
Client / Server
Connectivity
2.2.1.3 GNSS Spider SQL Database

GNSS Spider – All components, the GNSS Spider Servers and the Clients, access the GNSS Spider
SQL Database SQL database (Microsoft® SQL Server®). The GNSS Spider comprises the following
SQL databases:
1 Ntrip – Networked Transport of RTCM via Internet Protocol

 Spider
 SpiderNetwork
 SpiderCoordSystem
 SpiderPositioning
2.2.2 Spider Web Applications

Leica Spider Software Suite incorporates two major web applications:
 SpiderWeb
 Spider Business centre (SBC)
2.2.2.1 SpiderWeb
Overview SpiderWeb web application is an integrated secure solution for dissemination of
post-processing services. It comprises the following distinct system components:
 SpiderWeb web portal
 SpiderWeb Services:
 SpiderWeb RINEX Service
 SpiderWeb VRINEX Service
 SpiderWeb LCG Service
 SpiderWeb Database (Microsoft® SQL Server® database)
GUI The SpiderWeb web application provides the graphical user interface (GUI) for the
configuration and management functionality of SpiderWeb. As a web service, it can
be accessed by standard web browsers such as the Microsoft® Internet Explorer,
Google Chrome, Safari or Mozilla Firefox.
It is always automatically installed with the SpiderWeb Services. It requires the
Microsoft® Internet Information Service (IIS) Web Management (Script and Tools) to
be installed and activated on the same computer.
SpiderWeb - SpiderWeb supports three distinct access levels for a GUI client user connecting to a
access levels SpiderWeb portal – Admin, User and Viewer access.
Admin Level:
Administrators (e.g. system supervisors) have full control of SpiderWeb web
application. They can perform various operations, create and change configurations,
set parameters and modes etc. They can also monitor usage of SpiderWeb services,
display statistics and results of users’ requests, set billings, etc…
User Level:
User level group is limited to access only those SpiderWeb services that are granted
by their valid subscriptions.
Viewer Level:
This access level is granted to users without SBC accounts. Only unprotected
information provided on the SpiderWeb portal’s front page can be accessed by
Viewer level group.

2.2.2.2 SpiderWeb Windows Services
SpiderWeb RINEX The SpiderWeb RINEX Service is the core SpiderWeb server component. It processes
Service and manages all RINEX download requests. It stores all related data within its
exclusive SQL database installed on the same computer.
It is installed on the same computer as SpiderWeb application. The configuration and
operation of the SpiderWeb RINEX Service is realized through the SpiderWeb web
application.
SpiderWeb VRINEX The SpiderWeb VRINEX (VirtualRINEX) Service is an optional SpiderWeb server
Service component. It processes and manages all Virtual RINEX download requests. It stores
all related data within its exclusive SQL database installed on the same computer.
It is installed on the same computer as SpiderWeb application. The configuration and
operation of the SpiderWeb Virtual RINEX Service is realized through the SpiderWeb
web application.
SpiderWeb LCG The SpiderWeb LCG (Leica Coordinate Generator) Service is an optional SpiderWeb
Service server component. It processes and manages the following coordinate computation
post-processing requests:
 static computation request
 kinematic computation request
 stop&go computation request
 coordinates transformation request
It stores all related data within its exclusive SQL database installed on the same
computer.
2.2.2.3 SpiderWeb SQL Database

SpiderWeb – All components, the SpiderWeb portal and the SpiderWeb services, access the
SQL Database SpiderWeb SQL database (Microsoft® SQL Server®). The SpiderWeb web application
comprises the following SQL database:
 SpiderWeb

2.2.2.4 Spider Business Center
Overview The Spider Business Center is an integrated secure solution for online subscription
and management of all GNSS network services. It smoothly integrates GNSS Spider
and SpiderWeb services and allows you to complement them with your own value
adding benefits. It comprises the following distinct system components:
 SBC web portal application
 SBC Services:
 SBC Central Server
 SBC Proxy Server
 SBC RT Status Server
 SBC Database (Microsoft® SQL Server® database)
Both, then GNSS Spider Network Server and SpiderWeb connect to the SBC. They
submit their available product services to the SBC, where these can then be
combined into articles. Registered end users then can subscribe these articles or
they can be assigned by administrators, who also authorize subscription requests.
GUI The Spider Business Center web portal application provides you and your clients with
tools to view, register and manage real time and post-processing services. It is
designed to monitor service usage, to enable exchange of data, to view online
network and rover status and assist with support & accounting.
The SBC Web Portal application provides the graphical user interface (GUI) for the
configuration and management functionality of the SBC. As a web service, it can be
accessed by standard web browsers such as the Microsoft® Internet Explorer,
Google Chrome, Safari or Mozilla Firefox.
It is always automatically installed with the SBC Proxy Server. It requires the
Microsoft® Internet Information Service (IIS) Web Management (Script and Tools) to
be installed and activated on the same computer.
SBC - SBC supports three distinct access levels for a GUI client user connecting to a SBC
access levels web portal – Admin, User and Viewer access.
Administrator Level:
Administrators (e.g. system supervisors) have full control of SBC web application
with unlimited rights. There are two administrator subgroups, Sales Organisation
Administrators and Dealer Administrators, which are able to manage all data
associated to their sales organisation and dealer organisation respectively.
Support Level:
Support level group can access all settings and configurations of SBC administrator
portal as a viewer having no rights to edit or modify.
User Level:
User level group can login to SBC User Portal, see and modify their account details,
subscribe to articles in the shop area, access the services already granted by valid
subscriptions and contact their SBC Administrator via email.
SBC - Administrator and Support level users access SBC web application via SBC
Administrator Administrator Portal.
Portal

SBC - User level accesses SBC web application via SBC User Portal.
User Portal
2.2.2.5 Spider Business Center Windows Services

SBC Central Server The SBC Central Server is the core SBC server component. It processes and manages
all configuration, registration, access and authorization requests. It stores all related
data within its exclusive SQL database installed on the same computer.
It can be installed on the same computer as a Site Server, Network Server, Cluster
Server. RTK Proxy Server or SBC Proxy Server, but can also be installed on a separate
computer dedicated for the SBC Central Server operations.
The configuration and operation of the SBC Central Server is realized through the
web portal application that is automatically installed with the SBC Proxy Server.

SBC Proxy Server The SBC Proxy Server is the IT interface component to the SBC Central Server. It
takes care for secure communication between the SBC Central server and internet
users, Network Server and SpiderWeb.
It can be installed on the same computer as a Site Server, Network Server, Cluster
Server, RTK Proxy Server or SBC Proxy Server, but can also be installed on a separate
computer dedicated for the SBC Central Server operations. It does not require an
SQL database be installed on the same computer.
The SBC Proxy Server is designed such that it is ideally suited for a secure IT network
installation, where connections from an Intranet to the Internet are secured with
software and/or hardware firewalls creating a so-called DMZ (De-Militarized Zone).
Spider RT Rover A running Spider RT Rover Status Service is a prerequisite for a properly working
Status Server Usage View in SBC. The service is part of the SBC distribution. It always comes with
the SBC Proxy Server installation and needs no particular configuration. It does not
require an SQL database to be installed on the same computer.
Similar to SBC Proxy Server, it is designed such that it is ideally suited for a secure IT
network installation, where connections from an Intranet to the Internet are secured
with software and/or hardware firewalls creating a so-called DMZ (De-Militarized
Zone).
2.2.2.6 Spider Business Centre SQL Database

SBC – All components, the SBC web portal and the Spider Business Centre services, access
SQL Database the SBC SQL database (Microsoft® SQL Server®). The SBC web application comprises
the following SQL database:
 SBC_UAM
2.2.3 SpiderQC
Overview Leica SpiderQC is dual mode software. It can run as a stand-alone application and
also as a Windows Service.
Leica SpiderQC comprises the following distinct system components:
 SpiderQC Application
 SpiderQC Service:
 SpiderWeb GNSS QC Service
 Proprietary Database
2.2.3.1 SpiderQC Application

GUI The SpiderQC application represents a standalone software solution but can also
serve as the graphical user interface (GUI) that allows the operator to configure and
monitor the operation of SpiderWeb GNSS QC Service. SpiderQC has a typical
Windows™ look and feel. It can be installed on the Site Server, Network Server or
SpiderWeb computer and can also be installed on multiple other remote PCs or
Notebooks. Regardless of the installation type – standalone or as a service – the
SpiderQC always provides identical functionality and look-and-feel.
SpiderQC - Due to the nature of the software functionalities (data quality analysis), SpiderQC
access levels provides only one access level with full control of all settings, configurations and
features.

2.2.3.2 SpiderQC Windows Service
SpiderQC - SpiderWeb GNSS QC Service performs all standard quality analysis tasks continuously
SpiderWeb GNSS and automatically:
QC Service  Scheduled processing or RINEX files generated by a reference station network
 Generate a customisable multi-language web pages with key quality check
information including user definable traffic light status
 Graphical display of residual ionosphere and troposphere error across an RTK
network
 Time series of global RMS values for an RTK network
 Display time-line or scatter plots of coordinate displacements from real time data
streams
 Display time-line or scatter plots of inclination (x-tilt, y-tilt) and internal
temperature from real time data streams from Leica Nivel210/220 inclination
sensors
2.2.3.3 SpiderQC Database

SpiderQC – Both components, SpiderQC application and SpiderWeb GNSS QC Service access the
Proprietary SpiderQC proprietary database.
Database
2.2.4 CLM
Overview The Leica Geosystems Software Licensing is based on a reliable and secure
technology that does not require any Software Protection Key (“Dongle”). For the
initial activation of licenses, an internet connection is required for connecting to the

Leica Geosystems License Server. Once the licenses are activated on the local server,
this internet connection is no longer required. For activating additionally purchased
software options or software maintenance as contained in Customer Care Packages
(CCPs), an internet connection will be needed again though.
Within the Licensing system used by Leica Geosystems to manage software licenses,
the Floating Licenses can be shared across multiple client workstations within the
same local network. The Leica Spider Software Suite uses floating licenses model for
all applications.
Floating licenses are managed by a Local License Server running in your local
network. This Local License Server manages the license pool and controls that the
number of simultaneously used licenses does not exceed the total number of
purchased licenses.
The Local License Server comprises the following distinct system components:
 Client License Manager
 Local License Server Services:
 CLM Remote Daemon
 FLEXnet License Server
 FlexNet Licensing Service
 Proprietary Database (Trusted Storage)
2.2.4.1 Client License Manager

GUI The Client License Manager is the client graphical user interface (GUI), with typical
Windows™ look and feel that allows the operator to activate new, rehost existing,
verify and monitor the usage of software licenses. It is always installed locally on the
Local License Server computer and is also installed on multiple other remote PCs with
each Leica Spider Software Suite component that requires connection to Local
License Server (Site Server, Network Server, SpiderWeb, SBC and SpiderQC).
Regardless of the installation type – local or remote – the Client License Manager
always provides identical functionality and look-and-feel.
Any Client License Manager can be used to access the Local License Server
installations on the same computer network to which IP connections are available.
This is a particularly useful tool for remote maintenance and control of your software
licenses.
Multiple Client License Manager GUI Clients can access the Local License Server
simultaneously, such that a local Client License Manager can be open, whilst one or
more remote Client License Manager GUI Client users connect, for example to inspect
the usage of licenses.

CLM - Due to the nature of the software functionalities (management of software
access levels licenses), CLM provides only one access level with full control of all settings,
configurations and features related to software licenses.
View Bar
Navigation Pane
Report View
Tool Bar
Watch View
2.2.4.2 Local License Server Windows Services

CLM – The Local License Server can be installed on any physical server in your network and
Local License runs as a Windows service in the background. The Local License Server can manage
Server the licenses for one or more Leica Geosystems software products. The Local License
Server manages the license pool fully automatically and controls that the number of
simultaneously used licenses does not exceed the total number of purchased
licenses. If no more licenses are available, the Local License Serve will notify the
system administrator.
2.2.4.3 CLM Database

CLM – Both components, the Client License Managers and the Local License Server services
Proprietary access the CLM proprietary database (Trusted Storage) storing information related to
Database all activated licenses.

2.3 Installation Requirements and System Performance
2.3.1 Supported Virtualization Environment
Supported The installation and operation of the Leica Spider Software Suite is supported on the
Virtualization following host platforms:
Environments  Microsoft Hyper-V
 VMware ESXi 5.5
 Citrix XenServer 6.2
2.3.2 Operating System and other Software Requirements

Supported The following Microsoft® Windows™ operating system editions are supported and
Operating Systems recommended for the current version of GNSS Spider:
Operating System Version Recommended Service Pack2

 Windows Server 2016 64-bit
 Windows Server 2012 R2 64-bit
 Windows Server 2008 R2 SP1 64-bit SP1
 Windows 7 Professional SP1 64-bit SP1
Microsoft® SQL Some components of the Leica Spider Software Suite make use of the Microsoft®
Server® Database SQL Server® database.
requirements Leica Geosystems provides a separate installation package for convenience, which
will install and configure the Microsoft® SQL Server® 2012 Express for use with the
Leica Spider software suite and Leica GeoMoS software.
If a full version of Microsoft® SQL Server® 2012 shall be used, it must be purchased
and installed separately.
2.3.3 Hardware Requirements

Computer In general, the computer hardware requirements depend on parameters such as the
Hardware number of GNSS receivers / data streams connected, the number of sites included in
Requirements a network processing and/or the number of file-, real-time- or positioning- product
services that shall be active. The following hardware requirements are a general
guideline and should not be taken as being absolute. In case of doubts please
consult your Leica Geosystems representative for advice.
 GNSS Spider GUI only Minimum

Processor type Pentium II
Processor speed 1.0 GHz
Memory (RAM) 1 GB
Hard disk 1 GB
Gigabit-Ethernet
Monitor, Mouse, Keyboard
2 Later service packs should be used if available.

 GNSS Spider Site Server installation Minimum Recommended
Processor type Pentium II Xeon
Processor speed 1.0 GHz 2.0 GHz
Memory (RAM) 1 GB 2 GB
Hard disk 4 GB 100 GB
Gigabit-Ethernet
 GNSS SpiderNET installation Minimum Recommended

Processor type Pentium IV Xeon
Processor speed 2.5 GHz 2.6 GHz
Memory (RAM) 512 MB 4 GB
Hard disk 4 GB 100 GB
Gigabit-Ethernet
When all GNSS Spider servers will be installed on one computer, the higher computer
requirements should be satisfied at least.
Communication ports/devices have to be available depending on requirements and
final network configuration.
For professional use, the following (or equivalent) rack mountable server hardware is
recommended:
 Hewlett Packard ProLiant DL360 Server series
 Dell PowerEdge R710
using e.g.:
 Processor type: Intel Xeon E5520
 Processor speed: 2.26 GHz
 Memory: 4GB
Servers should be protected against power outages using an uninterruptible power

supply (UPS). The following (or equivalent) is recommended:
 APC Smart-UPS 3000i
A professional hardware firewall should be used to protect GNSS Spider server

installation. The following (or equivalent) is recommended:
 Cisco PIX 501 Security Appliance
Supported Modem For RTK data distribution via telephone lines it can be advantageous to use modem
Access Router access routers. The following modem access routers are supported directly within
Types GNSS Spider:
 Cisco AS5xxx series
 Cisco 3xxx series
For updated information on support of other access router models please contact
your Leica Geosystems sales & support representative.

2.3.4 System Performance
Guide values on The following Microsoft® Windows™ operating system editions are supported and
system recommended for the current version of GNSS Spider:
performance
Server Run on Limits
Site Server State of the art desktop Up to 100 Sites (100 1Hz/1h-
PC or Server, with fast Streaming File Products each)
hard disk
or
Up to 100 Sites when using 150 1Hz-
Real Time Positioning Products and no
Streaming File Products
or
Up to 50 Sites when using 50 1Hz-
Streaming File Products and 100 Post
Processing Products
Cluster Server High end PC or Server up to 10 Cluster Servers

(hyper-threading, multi- per core-processor unit up to 50
core, see recommended GPS-only Sites (e.g. for a dual-core =
hardware) total 100 sites) assigned to one or
multiple cluster servers
or
up to 10 Cluster Servers
per core-processor unit up to 25
GPS&GLONASS Sites (e.g. for a
quad-core = total 100 sites)
assigned to one or multiple cluster
servers
or
up to 10 Cluster Servers
per core-processor unit up to 8 G4
(4-constallations) Sites (e.g. for a
quad-core = total 32 sites) assigned
to one or multiple cluster servers
Network Server State of the art desktop 150 sites with network processing
PC or Server
RTK Proxy Server State of the art desktop Up to 500 Rover users
PC or Server, with fast simultaneously with normal baseline
CPU & memory RTK-data (single/nearest site)
or
Up to 300 Rover users
simultaneously with network
products (MAX, RTCM 2)
or
Up to 250 Rover users
simultaneously with individualized
network products (iMAX GPS &
GLONASS)
or

Re-broadcast up to 250
GPS&GLONASS sites with proprietary
data
Note: The GNSS Spider performance parameters given in the above table are guiding
values and based on testing results using the recommended hardware, as stated in
section 2.3.3. “Hardware Requirements”. The actual maximum performance
limitations therefore can still significantly vary (up or down) using different hardware
platforms. Also, continuous improvements of the GNSS Spider software will impact
these guide values. Please contact your local Leica Geosystems representative or
distribution partner for assistance to support your configuration and set-up.
2.4 Security
2.4.1 Overview
Generally, a Leica Spider Software Suite installation does not cause any concern
regarding your computers security. The notes in the following sections are intended
to support the system administrators for installations in corporate network
infrastructure and to learn about how Leica Spider Software Suite configuration
settings and software architecture help to achieve a highly secure installation set-up.
In corporate networks with firewall security, depending on how you install and
configure Leica Spider Software Suite and the selected components, several IP-ports
must be opened in the firewall for a certain communication direction. The Section
“Distributed installation in a corporate LAN” below should help to discuss required
network settings with your IT administrator or manager.
All Leica GNSS Spider, Leica Business Center, the Local License Server and Microsoft®
SQL Server® need to open IP ports on your computer. An active software firewall
installation may prevent the successful installation or operation of GNSS Spider. The
Windows built-in personal firewall is reconfigured automatically by Spider during
installation. Any other firewall must be reconfigured manually. A simple method is to
remove any active firewall from the system prior to the GNSS Spider installation and
then re-install the firewall afterwards. The following IP ports are utilized by GNSS
Spider and must be open in the firewall on the computer:
 Leica GNSS Spider (Data Dispatcher):
- Site Server IP port = 9877
- Cluster Server IP port = 9882 (9883, 9884, ...)3
- Network Server IP port = 9879
- RTK Proxy Server IP port = 9880
- RT Rover Status Server IP port = 9876
 Spider Web Applications:
- SBC Central Server IP port = 8023
- SBC Proxy Server IP port = 8020, 8021
- SBC Web Portal/SpiderWeb IP port = 80 (web server port)
 Local License Server IP port = 27000-27010, 19701
 MS SQL Server: IP port = 1433
If Leica Spider Software Suite is installed in a corporate network with public internet
access, we recommend installing a professional hardware firewall to properly protect
your reference station servers from unwanted access. Please also refer to Section
“Distributed installation in a corporate LAN” for security-related aspects of the Leica
Spider Software Suite installation.
3 Additional Ports as shown are used when using multiple Cluster Servers on a single computer.

2.4.2 General Security Aspects
Overview Any computer and software today is prone to be affected by external violations such
as viruses, worms or hacking attacks. To prevent these, it is recommended to run
appropriate software tools such as virus scanners and firewalls on your computer
systems. These tools must always be kept up to date, the responsibility of your IT
network personnel.
Of specific concern related to GNSS Spider is the protection against unauthorized
access to GNSS Spider operation and data in terms of:
 Remote user interface access at Spider Administrator level
 Logged data files (GNSS raw data, event logs, RTK Rover user logs, etc…)
 Real time GNSS data streams and RTK corrections
 End-user account information
Remote GNSS GNSS Spider control and configuration is only allowed for users who are member of
Spider GUI Client the Windows™ user group “Spider Administrators”. Any other user connection will
access control have viewer rights only. Thus, you should carefully manage the members of the
“Spider Administrators” group.
In case of security concerns regarding the remote client access, this can be fully
disabled for a GNSS Spider Server or be limited to GNSS Spider Administrators access
only.
A remote GNSS Spider GUI access requires the following IP ports to be open on the
GNSS Spider Server computer and any firewall between the remote computer the
GNSS Spider Server:
 GNSS Spider:
IP port = 9877 (Leica GNSS Spider Site Server Data Dispatcher)
IP port = 9879 (Leica GNSS Spider Network Server Data Dispatcher)
 SQL Server:
IP port = 1433
GNSS Spider For access to a GNSS Spider Site Server or Network Server the remote client must
Server Access know the GNSS Spider Server password.
Password This server password is individually set during the installation for each GNSS Spider
Site Server and Network Server.
The GNSS Spider Server password is required for connections of the GNSS Spider GUI
Client to a GNSS Spider Server as well as for connections between the different GNSS
Spider Servers. Therefore, a GNSS Spider Cluster Server as well as a GNSS Spider RTK
Proxy Server must also know the correct password of the Network Server to which
they are assigned.
Modify Server The GNSS Spider Site Server and Network Server access password can only be
Access Passwords modified using the local GNSS Spider Client GUI. It cannot be modified through a
remote GNSS Spider GUI.
For all local GNSS Spider Clients the passwords are updated. For example, changing
the local Network Server password, will automatically update the same password for
a locally installed Cluster Server or RTK Proxy Server, as well as for the connection
shortcut entry in the GNSS Spider Server Management. Restart the computer so that
the Password changes are ‘accepted’.
For all remote GNSS Spider Clients that should still connect to the Site Server or
Network Server, after the password has been changed, these must be updated
separately. This can only be done directly at the computer where they are locally
installed.

SBC default At first installation of the Spider Business Center a default master administrator
administrator account is created automatically to allow access to the web GUI using an internet
access browser.
The default administrator account logon details are as follows:
 User name: Admin
 Password: Admin
It is strongly recommended to change the default password for this account after
first logon and enter a valid email address for this account. Or to create a completely
new master administrator account with a new name and password and then to
delete the default Admin account.
Logged data file Access to logged data files such as GNSS raw data, QC files, event log files, RT user
access access log files, etc… is always possible directly on the local computer.
To provide public access to some or all of the file products, it is recommended to
copy these to a FTP server (which is set-up with the required access security). GNSS
Spider provides the tools to automatically push files onto FTP servers allowing public
access. For security reasons, such an FTP server should either be installed in a
company’s DMZ or with an external FTP provider.
For convenient and secure distribution of GNSS data sets from any network to
individual users via the internet we recommend using a web server application such
as SpiderWeb.
RTK Proxy – The RTK Proxy server is specifically designed to provide secured access to real time
Security for real- data streams for conventional RTK or Network RTK. It does not require access to the
time data access GNSS Spider SQL database, but only a single IP communication channel to the GNSS
Spider Network Server. To cope with a typical corporate Internet security policy, the
communication to the RTK Proxy Server is always initiated from the Network Server
(on the Intranet, inside the firewall) to the RTK Proxy Server (on the Internet or DMZ,
outside the primary firewall). Ports in the firewall must only be opened in the
outside direction, therefore protecting the Intranet from unintentional access.
Consequently, the RTK Proxy Server can be easily installed on a computer in a
company’s DMZ, whilst the remaining GNSS Spider servers are installed within the
secured Intranet, separated by a firewall from the outside Internet.
The following IP communication port must be opened in a firewall to successfully
connect from the Network Server to the RTK Proxy Server (in one direction only,
from the LAN to the DMZ):
 IP port = 9880 (Leica GNSS Spider RTK Proxy Server Data Dispatcher)
Additionally, access to the individual RTK product services that can be provided
through the RTK Proxy Server can be secured with various authentication and
authorization methods, available through the optional GNSS Spider RTK User
Management option. This option also provides the possibility to log individual user
accesses, providing the necessary information to charge RTK users for services
received. Note that no User-related data is stored on the server in the DMZ.
SBC Proxy – The SBC Proxy server is specifically designed to provide secured access to all Spider
Security for user Business Center related data and functions and to SpiderWeb. It is used by the SBC
management web server portal and SpiderWeb portal to communicate with the SBC Central Server.
access The GNSS Spider Network Server communicates directly with the SBC Central Server
to validate user login data for authentication that is stored in the SBC Central Server
SQL database.

Consequently, the SBC Proxy Server can be easily installed on a computer in a
company’s DMZ, whilst the remaining GNSS Spider Servers are installed within the
secured Intranet, separated by a firewall from the outside Internet.
connect from the SBC Central server to the SBC Proxy Server to allow communication
between the two (in one direction only, from the LAN to the DMZ):
 IP port = 8021 (Leica GNSS Spider SBC Proxy Server Data Dispatcher)
Spider RT Rover A running Spider RT Rover Status Service is a prerequisite for a properly working Live
Status Server Usage View in SBC. The service is part of the SBC distribution. It always comes with
the SBC Proxy Server installation and needs no particular configuration. It does not
require an SQL database to be installed on the same computer.
Like the SBC Proxy Server, it is designed such that it is ideally suited for a secure IT
network installation, where connections from an Intranet to the Internet are secured
with software and/or hardware firewalls creating a so-called DMZ (De-Militarized
Zone).
connect from the Network Server to the Spider RT Rover Status Server (in one
direction only, from the LAN to the DMZ):
 IP port = 9876
CLM Local License A running and fully configured CLM Local License Server with activated respective
Server licenses is a prerequisite for an operational CORS Network solution. The CLM Local
License service is part of the global Leica Spider Software Suite distribution and
similar to other components, it is designed such that it is ideally suited for a secure
IT network installation, where connections from an Intranet to the Internet are
secured with software and/or hardware firewalls creating a so-called DMZ (De-
Militarized Zone). In case your local network is split into a LAN and DMZ section, we
recommend installing the Local License Server in the DMZ (De-Militarized Zone) part.
The following IP communication port must be opened in a firewall to allow CLM
clients to successfully connect to the CLM Local License Server (in one direction only,
from the LAN to the DMZ):
 IP port = 19701
 IP port = 27008
 IP port = 27010
For the initial installation of the Local License Server and activation of licenses an
Internet connection is required to the Leica Geosystems License Server. Once the
Local License Server is installed and the licenses are activated, this Internet
connection is no longer required. For activating additionally purchased software
options or software maintenance as contained in the Customer Care Packages (CCPs)
the Internet connection needs to be established again. The following port must be
open for all the above-mentioned transactions (from the DMZ to the Internet):
 IP port = 443
SQL Database Leica Spider Software Suite makes use of the Microsoft ™ SQL Server database. This
database contains all configuration information and should therefore be well
protected.
It is therefore important that you enter a secure password for the SQL System
Administrator (sa) during the installation of SQL Database.
If no Leica Spider Software Suite remote access is required through the firewall, then
the following port must not be open in your company’s firewall (i.e. this port must
remain closed).

 SQL Server: IP port = 1433
2.4.3 Distributed Installation in a Corporate LAN

Overview This section is primarily of interest for distributed installations in a corporate
network infrastructure. It does not apply to single stand-alone computer
installations, such as a single reference station installation with the GNSS Spider Site
Server only. It should help you when explaining the security aspects relating to Leica
Spider Software Suite to your IT network administrator.
A typical corporate network with public Internet access is structured in zones of
different security levels.
 Secured LAN/Intranet = Private network inside a company or organization.
 De-Militarized Zone (DMZ) = Subset of a corporate network, located between
the unsecured Internet and the secure local area network (LAN or Intranet). This
subset is the public part of the LAN. Communication between local and external
networks is controlled by security devices such as routers, firewalls.
 Un-Secured Zone = Word Wide Web / Internet.
With its individual server components, Leica GNSS Spider is perfectly designed to fit
into this concept.
Following are some sample information about the required IP ports to be opened in
distributed installations. In general, the GNSS Spider Site Server, Network Server and
Cluster Server and the SBC Central Server should be located in the secure LAN area
on a single computer (or distributed over multiple computers), whilst for security
reasons, the RTK Proxy Server, SBC Proxy Server, RT Status Server and the Spider
Web Apps (SBC Web Portal and SpiderWeb) should ideally be located in the DMZ.

Sample I:
Providing raw data
files using an FTP
server
 No GNSS Spider specific IP ports need to be opened.

 Firewall_1 needs to open standard FTP port from inside to outside.
 Firewall_2 needs to open standard FTP port from outside to inside.
 The FTP server should be configured to have public as well as protected access
available.
Sample II:
Providing RTK
Products via TCP/IP
channel
 From the LAN (Intranet) to the DMZ (Firewall_1) only one port (port 9880) must
be opened and only in one direction (LAN to DMZ)!
 From the DMZ to the Internet (Firewall_2) all IP ports that are configured within
the GNSS Spider RTK products to send data to TCP/IP must be opened to allow
access from the Internet to the RTK Proxy Server.
 For example, if a RTK product of the type Nearest Site is configured to use TCP/IP
port 9000, then this particular port must be opened in Firewall_2. It is then not
needed to open a port per individual site. In Firewall_1 only port 9880 must be
open.
 For example, if 20 RTK Products of type Single Site are configured for each one
of 20 individual sites using ports 9000 - 9020, then all these particular ports
must be open in Firewall_2, whilst in Firewall_1 still only the one port 9880 must
be open.

Sample III:
Providing RTK
Products via NTRIP
channel
 From the Intranet to the DMZ (Firewall_1) only one port (port 9880) must be
opened and only in one direction (LAN to DMZ)!
 From the DMZ to the Internet (Firewall_2) those IP ports must be opened that
are configured within the GNSS Spider RTK products to send data to NTRIP-Client,
to allow access from the Internet to the RTK Proxy Server. However, this should
typically be only one port, since when using send data to NTRIP-Client it is
possible (and advantageous) to use the same IP port for all products of this type.
With NTRIP, individual products are identified thanks to their mount point
descriptors.
 For example, various RTK products of different types can be configured to send
to NTRIP-Client port 8080. Then only this particular port must be opened in
Firewall_2. It is then needed to open an individual port neither per site nor per
RTK Product. On Firewall_1 only port 9880 must be open.
Sample IV:
Using SBC Central
Server and SBC
Proxy Server with
public access to
Spider Web
Applications and
RT Status Server
 From the Intranet to the DMZ (Firewall_1) only 3 ports (ports 80, 9876 and
8021) must be opened and only in one direction (LAN to DMZ)!
 From the DMZ to the Internet (Firewall_2) only HTTP port 80 and ports 9015 and
9015 must be open, to allow web browser access to the SBC Web Server and
GNSS Spider RT Status Information with Rover Live Usage Status and / or
SpiderWeb access.

Sample V:
Using fully
featured Leica
Spider Software
Suite CORS
Network Services
 From the Intranet to the DMZ (Firewall_1) 5 ports in total (ports 80, 9876, 8021,
9880 and 21) must be opened and only in one direction (LAN to DMZ)!
 From the Internet to DMZ (Firewall_2) HTTP port 80 (in both directions), NTRIP
port, e.g. 8080 and ports 9015 and 9015 must be open, to allow access and
distribution of data for RT and PP services.
Sample VI:
Remote GNSS
Spider GUI Client
connection
through DMZ
 For a remote connection with the GNSS Spider GUI Client into a corporate
network with firewall protection and DMZ, we recommend using virtual private
network (VPN) technology.
 The following ports must be opened within the VPN tunnel:
9877 = Leica GNSS Spider Site Server
9879 = Leica GNSS Spider Network Server
1433 = SQL Server

Sample VII:
Communication of
CLM Local License
Server with other
Spider Suite
components
 From the Intranet to the DMZ (Firewall_1) at least 3 ports in total (ports 19701,
27008 and 27010) must be opened and only in one direction (LAN to DMZ)!
 From DMZ to the Internet (Firewall_2) HTTPS port 443 must be open for the
initial installation of the Local License Server and activation of licenses an
Internet connection is required to the Leica Geosystems License Server. Once the
Local License Server is installed and the licenses are activated, this Internet
connection is no longer required. For activating additionally purchased software
options or software maintenance as contained in the Customer Care Packages
(CCPs) the Internet connection needs to be established again.
2.4.4 General Data Flow

The following diagrams show the general data flow for configuration and streaming
data between GNSS receivers and the server components. The data flow is the same
regardless whether all GNSS Spider are installed on one computer or distributed on
different computers.
Site Server only For a GNSS Spider Site Server only installation, the main data flow is from the
installation receivers to the Site Server. From here, file products and real-time products can be
provided to the end user, or data can be streamed into a SpiderNET installation for
real-time network processing and advanced real-time distribution using the RTK
Proxy Server.

RTK Network For a real-time network installation including GNSS SpiderNET, data from one or
installation more Site Servers can be combined within SpiderNET, which consists of the Network
Server, one or more Cluster Servers and the RTK Proxy Server. For user access
management, also the SBC servers are required.
A small network consisting of 5-10 reference stations and serving only a few number
of RTK users, all server components could also be installed on a single sufficiently
high-performance computer.
The diagram shows the RTK Proxy Server as well as the SBC Proxy server / Web Portal
being separated by a firewall from the other server components, which is a
recommended set-up for best IT security.
RTK Network and Should Post-Processing services be included in the provided CORS Network solutions,
Post Processing SpiderWeb and related Web Portal can be combined with the RTK Network
Services Installation. SpiderWeb installation can share the same computer with SBC Web
installation Application or can be installed on a dedicated machine.
The diagram shows the SpiderWeb as well as the SBC Proxy server / Web Portal being
separated by a firewall from the other server components, which is a recommended
set-up for best IT security.

3 Leica Spider Software Suite Features
3.1 Leica GNSS Spider
3.1.1 General Layout
3.1.1.1 Views and Menus
Menu Bar
Toolbar
List Bar
Management Tree
View
Management
Report View
Tabbed View
Watch View
Status Bar
Context Menu  right click to open context menu

 different content of context menu in different views

Management  right click on the column header to open content designer
Report View
Content Designer
3.1.1.2 General Settings

Layout  Show/Hide components
 List Bar
 Watchview Bar
 Status Bar
Toolbars  Create new, customise existing and reset toolbars

 Show or hide tooltips

Settings  General Settings:
 Show splash window on startup
 Keep site windows within the main window (MDI)
 Open last used views on startup
 Linear units
 Meters [m]
 US Survey feet [fts]
 International feet [fti]
 Time Format
 Local
 UTC
 Coordinate Type
 Cartesian X/Y/Z
 Geodetic Lat/Lon/Height
 Deactivated messages pool
 Watch View Settings:
 Automatically display last message
 Play event sound
 Enable verbose mode
3.1.1.3 Management
Server  create new, modify of delete Site Server or Network Server (SpiderNET)
Management connections

Operator  create new, modify of delete agencies operating the CORS Network
Management
 create new, modify of delete operators of the CORS Network

 select notification method for each operator

Antenna  manually create new, modify or delete configuration of GNSS antennas including
Management phase center offsets and phase center variations components
 import of mean antenna calibration files in standard formats (NGS and ANTEX)
 import of individual antenna calibration files in standard formats (NGS and
ANTEX)
 antenna information is stored in the SQL database
Device  create new, modify of delete devices used for communication in the CORS
Management Network

Data Transfer  create new, modify of delete transfer locations used for files distribution or data
Locations Manager downloads in the CORS Network
 supported protocols
 FTP via built-in FTP client
 FTP file transfer to multiple locations
 use passive mode option
 verify successful FTP transfer option
 proprietary solution
 built-in Data Transfer Locations Manager
 configure GNSS data storage FTP locations
 FTP server IP address or hostname
 user name
 password
 remote directory including fully customizable subdirectory structure
 support for sending additional commands
 configure proprietary GNSS data storage locations
 server IP address or hostname
 user name
 password
 remote directory structure

Event Management  list of events that can trigger notifications and alarming
 configure the notification method: email or network notifications
 use command line prompt to trigger a 3rd party application or script
Transformation  create new, modify of delete coordinates transformations in accordance with

Management RTCM standard
 create new, modify of delete Datum Transformations

 create new, modify of delete Ellipsoid Models
 create new, modify of delete Horizontal or Vertical (Geoid) Residual Models
 create new, modify of delete Projections
3.1.1.4 Tools
Database  backup, restore or delete Leica Spider Software Suite SQL databases
Management Tool  can be started out of a CMD-Window or via batch files
Password Tool  modify access passwords

Manual File  manually download Raw Data Files from Leica receivers
Download  remotely format the memory device
Manual RINEX  supported product types:

converter  RINEX 2.x
 RINEX 3.x
 support for multiple Leica proprietary files input
 RINEX file products observation rates: 0.02, 0.05sec, 0.1sec, … 300sec
 support for the following file compressions:
 None
 Zip
 GZip
 Unix compressed Z
 CRINEX (Hatanaka) compacted data
 support for multiple extensions
 definable content of the RINEX files including:
 observations
 selection of observables
 selection of satellite system
 product dynamics
 SNR values
 Doppler measurements
 L2C
 navigation
 external sensors
 meteo sensors
 tilt sensors
 user definable header information (observer, agency) and comments

Remote FW  remotely upgrade GNSS sensor’s FW or insert the license key
Upgrade Tool
Support Tool  in case of troubles, use the Support Tool Wizard to collect all information
necessary for NRS support team to resolve your incident

3.1.2 Site Server
3.1.2.1 Configurations

General  Message expiry age for Watchview Bar
 Designation of MASTER time site
 Support for secondary port in failover system
Connections  Email notifications:

 Mail dial-up connection
 Mail server configuration
 Dispatch interval and maximum number of messages per mail for email
notifications
 FTP Client:
 FTP dial-up connection
 FTP push interval
 Immediately
 1h, 2h, …24h
 FTP push sort order
 Oldest first & sorted by location
 Latest first
 Latest first & sorted by location
 Oldest first
 Access Router:
 Access router type
 Telnet login password
 Enable mode password
 NTRIP Caster
 Active NTRIP Caster
 Set NTRIP Caster port
Thresholds  Sensor conditions:
 Remaining power
 Available memory
 Internal temperature
 QC check criteria:
 Actual vs. expected observations
 Obs. L2 : Obs. L1
 #LLI_L1 : #OBS_L1
 #LLI_L2 : #OBS_L2
 Data gaps
 QC Elevation mask
 Server settings:
 Available disk space
Security  Allow remote access for
 All
 Spider Administrators
 None
UTM Projection  False Easting:
(used in Spider  False Northing:
Positioning)  Zone width and Zone offset is set automatically based on Site Coordinates
Leap Second  Automatic handling of leap seconds
 Manual handling of leap seconds
 Current number of leap seconds
 Future number of leap seconds
 Future number of leap seconds valid from
3.1.2.2 Site Creation

Site Creation
Wizard
Site import from  drag and drop a RINEX file into the Site Tab Management Report View
RINEX file
Manual Site  create sites from the scratch
Creation  create sites as a copy of the existing site. Such a site will have identical settings
as the already existing site

3.1.2.3 Site Configuration
Communication  supported types of communication between Site Server and sites
 Serial (RS232)
 USB
 Modem
 TCP/IP (TCP/IP Client to Server)
 NTRIP (NTRIP Client to Caster)
 NTRIP (NTRIP Source to Caster)
 communication backup
 support for two communication lines to one site (primary and backup
communication links)
 automatic switch between primary and backup communication links
Input GNSS Raw  Raw Data Streams

Data Formats  Proprietary Leica LB2
 RTCM 2.x (GPS and GLONASS)
 RTCM 3.x (extended)
 RTCM 3.2 MSM (MSM4 and MSM5)
 Trimble RT17
 Ashtech MBEN

 Downloaded Raw Data Logged Files
 Proprietary Leica MDB
 standard formats
 RINEX 2.x
 RINEX 3.x
 Csv (WNI meteo)
Input GNSS Raw  Raw Data Streams

Data Rates  Proprietary Leica LB2
 Streaming rate: off, 0.05, … 60sec
 Downloaded Raw Data Logged Files

 Proprietary Leica MDB
 Polling rate:
 never
 at regular intervals: every 1 min, 5 min, …24hours
 at fixed times
 autodelete logged MDB files: never, older than 4 hours… older than 90
days

 RINEX 2.x, 3.x, Csv (WNI meteo) via FTP
 FTP location
 length of file: 5min, … 24h
 expected latency
 support for Compact RINEX
 archive types:
 none
 GZIP
 Unix compress
 Zip
 support for multiple extension
 support for predefined and customizable Directory Naming Convention
Naming  Site name

 Site code
 RINEX Marker Name
 RINEX Marker Number

Coordinates  Coordinate input in geodetic or cartesian format
 Dual-Coordinate sets for sites (Product & Physical coordinates)
 Import site coordinate from a file for updates
Antenna  Antenna type and offsets

Receiver  Receiver manufacturer, model, FW and SN
 support for backup receiver at the site
Miscellaneous  Primary and secondary operator

 Site specific RINEX header comments and links to include ASCII files with content
 Thematic information
3.1.2.4 Receiver Configuration

Power AutoOn  Configuration of GNSS Receiver start up after power failures
 AutoOn - Power Fail: immediate starts up again if there is full power available
 ExtPowerLow/ PowerFail: immediate starts up also if there is only low power
available
 Delay On Turning Sensor Off
 number of seconds the sensor waits from receiving the Turn GNSS sensor off
command until turning off

Tracking  Elevation Mask
 Code Smothing
 Not smoothed
 Smoothed or Sampled
 Enabled Satellite Systems
 GPS
 GLONASS
 GALILEO
 BEIDOU
 QZSS
Logging  rate: off, 0.05, … 300sec

 length of file: 5min, … 24h
 autodelete logging file: never, older than 4 hours… older than 90 days
 dynamics: static, moving
 compression: zip, none
Direct RTK output  direct dual serial interface RT output from the receiver (independent rates and
formats for RT output 1 and RT output 2 respectively)
 communication devices configuration (based on Device Management)

 Message configuration
 Message Type
 Leica/Leica 4G
 CMR/CMR+
 RTCM2.x
 RTCM3.x
 End of message
 Reference Station ID
 Time slicing support
 Rates
 Coordinate rate
 Infor rate
 Data rate
 Ephemeris rate
External sensors  Support for two external RS232 sensors connected to one GNSS sensor
 meteorological sensor
 inclination/tilt sensor

3.1.2.5 File Products Service
File product types  Leica GNSS raw data proprietary format MDB
 RINEX v2
 RINEX v3
 Event log file
Source of GNSS  downloaded proprietary Leica raw data files MDB

raw data  downloaded RINEX files
 proprietary Leica raw data streams LB2
 RTCM raw data streams
Properties  multiple file products configurable per type and individual sites
 identical file products configurable for all sites in the network using one global
file product definition
 GNSS file products observation rates: 0.05sec, 0.1sec, … 60sec
 GNSS file products lengths: 1min, 5min, …24 hour
 user definable header comments include files individual per site and RINEX file
type
Archiving  support for the following file compressions:
 None
 Zip
 GZip
 Unix compressed Z
 CRINEX (Hatanaka) compacted data
 support for multiple extensions
 auto cleanup scheduler
 never
 after 1day, 2 days, 1 week, … 12months
 after successful push
 fully customizable folder structure

Contents  Observations
 fully customisable for RINEX 2.x
 Observables
 L1 code only
 L1 code and phase
 L1 & L2 code and phase
 L1, L2 & L5 code and phase
 Satellite system
 GPS only
 GPS and GLO
 Product dynamics: static or kinematic
 Doppler measurements
 SNR values
 L2C
 “as set on GNSS receiver” for RINEX 3.x
 “as set on GNSS receiver” for MDB
 Navigation
 Navigation data
 Almanacs
 External sensors
 Meteo sensors
 Tilt sensors
 Quality Control Report

Distribution  via built-in FTP client
 upload individual file products to one or more destinations (based on Data Transfer
Locations Manager)
 fully customizable folder structure support on remote destination
Advanced  Command line option, executes applications or scripts upon file product
completion

3.1.2.6 Real Time Product Service
Communication  COM (serial interface)
interface  TCP/IP (TCP/IP host)
Satellite System  GPS

 GLONASS
 GALILEO
 BEIDOU
 QZSS
Message Types  Message configuration

 Message Type
 Original Raw Data
 Leica/Leica 4G
 CMR/CMR+
 RTCM 2.x
 RTCM 3.x (compact and extended)
 RTCM 3.x (MSM4 and MSM5)
 End of message
 support for Null Antenna
 support for code smoothing
Rates  customizable rates:

 coordinate rate: 5s, 10s, 15s, …120s

 info rate: 10s, 15s, 20s, …120s
 data rate: 1s, 2s, 3s, 4s, 5s, 6s, 10s, 12s, 15s, …60s
3.1.2.7 Monitoring System Performance

Site Tracking  Skyplot view
Performance  Elevation mask
 time of last change
 communication status
 last orbits update
 Tracking performance with 1Hz update rate

 tracked satellites information
 visualization of tracked signals
 SNR visualization
 elevation and azimuth of tracked satellites

Remote Sensors  site operation status and position
Status  memory, power, temperature of the GNSS receivers
 logging status and last downloaded file
 external meteo and tilt sensor data
 Validation of meta data information from 3rd party receivers/SW via RTCM
 Stationary ARP coordinates
 Stationary Antenna Height
 Reference Station Indicator
 Antenna Descriptor
 Receiver Type Descriptor
 Leap Second Information

Graphical Map  Location of GNSS Raw Data Site
View  site code
 site tracking and logging status
 tracked satellites info
 background map
 connect/disconnect site from the map view
 Graphical Settings
 Measure Tool
Communication  Real time status on the data stream

Status  Master Time Site visualisation (yellow background)
 Site Communication activity
 Disconnected
 Receive data
 Downloading
 Connecting
 No response
 Tracking Performance
 Data received (%) within the last 24 hours
 Date/Time of the first epoch received

 The rate of the raw data being received from each site
 Date/Time and duration in seconds of last gap occurred
 The total number of data gaps since the site was connected
 Date / time and duration in seconds of the largest gap since the site was
connected
 The current latency of the site (master time - time of site) in seconds
 The average latency of the site in seconds
 Primary or back communication link used
 Leap seconds information
 History of the data stream

 Online/offline mode
 Link to Watch View Window
Watch View  Consists of the tree view and the report view
 The report view displays the system events within a selected period
 Event type (based on Event Management)
 Information: this is the lowest level of status message (lowest level of
importance)
 Message: this is a middle level of status message (middle importance).
Displayed in blue
 Warning: this is the most serious level of status message (high importance).
Displayed in red
 The site of site-specific events
 Date and time of event
 User responsible for the event
 Source of the event
 Description of the event

 Online mode: view the event messages as they occur in a list ordered by time
 All
 General
 All sites
 Sites specific
 Offline mode: query on the messages via a user defined dialog
 Time range or User defined
 Content
 General
 Specific Site Related
 Message type
 All
 Information
 Messages
 Warnings
 Messages and Warnings
 Watch View display options:

 Add message manually
 Search functionality
 Find what: text string
 Search in column:
 All columns
 Site
 Date/Time
 User
 Category
 Text

Status Bar  the number of items selected and number of total items in the currently active
tree/report view (in the example below 2 out of 6 sites selected)
 location of the currently displayed server: Local or Remote
 Current privilege server access level
 system keyboard status for keys: scroll, num lock, caps lock
 local time
 software licensing LED status indicator
 green: connection of the GNSS Spider server component to the Local License
Server is possible and valid licenses are available
 yellow: the licenses were available in the past but currently a problem was
detected
 red: connection to the Local License Server is not possible or no valid license
could be found on the Local License Server

3.1.3 SpiderNET
3.1.3.1 General Configuration
General  Message expiry age for Watchview Bar

 Designation of MASTER time Site server
 Add, modify, update or remove SpiderNET components:
 RTK Proxy server host name or TCP/IP address
 Cluster server host name or TCP/IP address
 SBC Central Server connection
 SBC Central Server hostname or TCP/IP address
 Primary Authentication
 SBC only
 SBC with fallback
 Fallback Authentication always denied
 SBC Proxy Server hostname or IP address (optional)
Connections  Email notifications:

 Mail dial-up connection
 Mail server configuration
 Dispatch interval and maximum number of messages per mail for email
notifications
 FTP Client:
 FTP dial-up connection
 FTP push interval
 Immediately
 1h, 2h, …24h
 FTP push sort order
 Oldest first & sorted by location
 Latest first
 Latest first & sorted by location
 Oldest first

 Access Router:
 Access router type
 Cisco 3xxx
 Cisco AS5xxx
 Cisco 29xx
 Telnet login password
 Enable mode password
Security  Allow remote access for

 All
 Spider Administrators
 None
Status Logs  Write Watch View logs (weekly)

 Set directory path
 Write Site Status logs (real time and history)
 Write Network Status History log
 Write Network Status Real Time log
 Write Network Correction data
 Set directory path
 Autodelete files after
 Never
 Ater 1d, 2d, …30d
 Primary FTP location
 Set additional directory path
 Secondary FTP location
 Set additional directory path
Connection Logs  Set Network Name

 General Connection log
 Set root directory path
 Clean up files
 Never
 After 1d, 2d, 1w, 2w, …12m
 Format type:
 Spider format
 SAPOS format
 Detailed Connection log
 Select Directory Naming Convention
 Root path only
 Year/Month/Day of Month
 Clean up files
 Never
 After 1d, 2d, 1w, 2w, …12m
 FTP location
 NMEA log
 Select Directory Naming Convention
 Root path only
 Year/Month/Day of Month
 Clean up files
 Never
 After 1d, 2d, 1w, 2w, …12m

RTCM  RTCM 3 (MT1029) welcome message
3.1.3.2 Network Processing

Processing Modes  Real Time
 Reprocessing
 Set interval for Re-Processing
 Start date and time
 End date and time
 Observation Rate
 External data path
Processing  Elevation Mask

Parameters  Ionosphere model
 Automatic selection
 Highest status will be given to a model based on the predicted IONEX data,
that is downloaded from the IGS
 If IONEX data is not available the Klobuchar model will be used
 If Klobuchar model is not available, no model will be used
 Troposphere model
 Computed
 No Model
 Modified Hopfield
 Saastamoinen
 Niell
 Orbit model
 Broadcast only
 Automatic selection
 Broadcast ephemeris are sent for network RTK corrections since this is
required by the rover
 Additionally, precise ephemeris are used for network ambiguity resolution

Use of Precise  When configured, SpiderNET will automatically download and use precise GNSS
GNSS File Products products in network processing
 Precise Ephemeris
 Primary FTP source
 FTP location
 FTP path
 Backup FTP source
 FTP location
 FTP path
 IONEX
 FTP location
 FTP path
 FTP location
 FTP path
 DCB
 FTP location
 FTP path L1
 FTP path L2
 FTP location
 FTP path L1
 FTP path L2
 Multi-GNSS DCB
 FTP location
 FTP path
 FTP location
 FTP path

Supported Satellite  Operational Constellations
Systems and  GPS
Frequencies  GLO
 BDS
 GAL
 QZSS
 Triple frequency processing (GPS, GAL)
 Proven interoperability of mixed manufacturers (hardware bias handling)
CORS Network  support for CORS Network Clustering

Configuration  Cluster configuration
 Tabular (drag & drop)
 Graphical

 Start / Stop of individual Clusters
 Configurations of individual RTCM 3 Network RTK Master Auxiliary concept Cells

 Tabular (drag & drop)
 Graphical
3.1.3.3 Real Time Product Services

Product Types  Single Base RTK Solutions
 Single Site: user selected GNSS Site
 Nearest Site: GNSS Site nearest to the rover’s location
 Network RTK Solutions
 Single Cell: Network solution manually configured by administrator
 Automatic Cells: Automatically generated best solution based on rover’s
location
 User Location Service (NMEA Redirect)
 Real time output and/or logging of received rover data, e.g. NMEA
 Output to any available communication channel

 Secured with access authentication & authorization
Communication  Serial (COM)

interface  Phone
 Modem
 Access Router
 TCP/IP (TCP/IP Host)
 NTRIP
 NTRIP Caster on multiple TCP/IP ports with unlimited multiplexing
 NTRIP Server
Authentication  Based on used communication interface

Methods  NMEA GPUID
 Telephone number
 IP-Address
 Ntrip
Message  Message Type

Configuration  Supported data formats
 Original Raw Data
 Leica/Leica 4G
 CMR/CMR+
 RTCM 2.x
 RTCM 3.x (compact and extended)
 RTCM 3.x (MSM4 and MSM5)
 Supported Network RTK Methods
 MAX via RTCM3.1 and Leica 4G
 FKP via RTCM 2.3 and 3.1
 VRS via all supported RTK data formats
 iMAX via all supported RTK data formats
 End of message
 Nothing
 Carriage Return <CR>
 Coordinate Reference Frame
 Product Marker Coordinates Frame
 Physical Marker Coordinates Frame
 Custom
 Target Coordinate System
 select target coordinate system based on Transformation Management
 available with RTCM 3.1 and higher and Leica 4G formats
 Datum Transformations
 Ellipsoids
 Residuals (horizontal & vertical)
 Projections
 Satellite System
 GPS
 GLO
 GAL
 BDS
 QZSS
 Support for Code Smoothing
 Support for Null Antenna
 Support for Leica receiver emulation

Rates  customizable rates:
 coordinate rate: 5s, 10s, 15s, …120s
 info rate: 10s, 15s, 20s, …120s
 data rate: 1s, 2s, 3s, 4s, 5s, 6s, 10s, 12s, 15s, …60s
 ephemeris rate:
 off
 when new data available
 30s, 60s, 120s, 300s
 Iono and Geo rate (only for MAX network method):
 1s, 2s, 3s, 4s, 5s, 6s, 10s, 12s, 15s
 FKP rate (only for FKP network method):
 1s, 2s, 3s, 4s, 5s, 6s, 10s, 12s, 15s
 support for Residual message (only for VRS and iMAX via RTCM3.x)
 support for RTCM welcome message (MT1029)

 different rates can be set for obsolete or legacy data formats, e.g. RTCM 2.x
NTRIP  NTRIP metadata for RT products using NTRIP communication interface
Advanced  automatic optimization of RTK solution based on Rover’s changing location

Properties  maximum distance limit between rover and GNSS site to provide RTK service
 automatic selection of alternative solution based on GNSS sites observation
conditions and Rover’s location
 automatic fallback/fallforward from Network RTK to Single Baser RTK solution
and vice versa based on specific criteria
 poor network corrections availability or rover user outside of CORS Network
coverage
 distance between rover user and nearest GNSS site shorter then user definable
threshold
 automatic disconnection of inactive users (rover heartbeat feature)
3.1.3.4 Monitoring System Performance

Graphical Map  Location of GNSS Raw Data Site
View  site code
 site network fixing status (color codes)
 number of fixed/tracked satellites info

 background map
 Measure Tool
Sat Status  visualization of real-time network processing status per SV frequencies and site
 Site Code
 Cluster/Cell
 Fixed/Available GNSS Satellites
 Fixed/Available GPS Satellites
 Fixed/Available GLO Satellites
 Fixed/Available GAL Satellites
 Fixed/Available BDS Satellites
 Fixed/Available QZSS Satellites
 Last Update
Sat History  visualization of network processing status history per SV frequencies and site
 Site Code
 Cluster/Cell
 Fixed/Available GNSS Satellites
 Fixed/Available GPS Satellites
 Fixed/Available GLO Satellites
 Fixed/Available GAL Satellites
 Fixed/Available BDS Satellites
 Fixed/Available QZSS Satellites
 Last Update

 Online/offline mode
 Link to Watch View Window
Watch View  Consists of the tree view and the report view
 The report view displays the system events within a selected period
 Event type (based on Event Management)
 Information: this is the lowest level of status message (lowest level of
importance)
 Message: this is a middle level of status message (middle importance).
Displayed in blue
 Warning: this is the most serious level of status message (high importance).
Displayed in red
 The cluster of cluster specific events
 The product of product specific events
 Date and time of event
 User responsible for the event
 Source of the event
 Description of the event
 Online mode: view the event messages as they occur in a list ordered by time
 All
 General
 All Clusters
 Cluster Specific
 All Products
 Product Specific
 Offline mode: query on the messages via a user defined dialog
 Time range or User defined
 Content
 All

General
Specific Cluster related
Specific Product related
 Message type
 All
 Information
 Messages
 Warnings
 Messages and Warnings
 Watch View display options:

 Add message manually
 Search functionality
 Find what: text string
 Search in column:
 All columns
 Site
 Date/Time
 User
 Category
 Text
Status Bar  the number of items selected and number of total items in the currently active
tree/report view (in the example below 3 out of 5 sites selected)
 Network Processing status
 location of the currently displayed server: Local or Remote
 Current privilege server access level
 system keyboard status for keys: scroll, num lock, caps lock
 local time
 software licensing LED status indicator
 green: connection of the GNSS Spider server component to the Local License
Server is possible and valid licenses are available

 yellow: the licenses were available in the past but currently a problem was
detected
 red: connection to the Local License Server is not possible or no valid license
could be found on the Local License Server
3.1.3.5 RT Connection Audit

Graphical Map  On-line graphical and numerical RT connection status with background map
View  RT solution status and positioning quality
 RT user ID
 RT user name
 start of connection
 duration of connection
 RT product name
 RT user’s position
 RT user’s distance to GNSS site/Master station used in RT solution
 GNSS sites used in RT solution and configuration of Network RTK product
Rover Status  On-line graphical and numerical RT connection status with Google Maps™

 RT solution positioning quality
 RT user ID
 RT user name
 start of connection
 duration of connection
 RT product name
 number of satellites tracked at the rover vs. number of satellites data
provided by RTK corrections
 product name
 RTK correction latency
 CORS site/Master Site ID
 CORS site/Master Site ID as read from incoming NMEA message
 Start of sending RTK corrections
 Solution type
 HDOP
 Rover position
 RT user’s distance to GNSS site/Master station used in RT solution
 Client host
General  simple monthly text file providing basic connection information for billing
Connection Log purposes
 User name of authenticated rover user entity
 Company associated with rover user
 Start date of the connection between rover user and SpiderNET
 Start time of the connection between rover user and SpiderNET
 End date of the connection between rover user and SpiderNET
 End time of the connection between rover user and SpiderNET

 Duration of the connection between rover user and SpiderNET
 Name of the RT product
 Latitude, Longitude and Height of first coordinate that was received from the
rover user via GGA message
Detailed  One log per connection event providing basic connection information (as per the
Connection Log general connection log) plus more detailed connection information
 General Information
 RT Product Settings
 Connection History

NMEA Log  log file is only created if a rover connects to a RT product and the rover provides
a NMEA GGA message
 data is logged with an absolute time stamp by Spider prefixing the NMEA GGA
message with the GPS week and the seconds of GPS week
3.1.3.6 Reference Frames and Coordinate Systems

Reference Frames  support for multiple reference frames
 product marker coordinates reference frame
 physical marker coordinates reference frame
 custom reference frames
 creating reference frames
 import of product marker reference frame coordinates from a CSV file
 import of physical marker reference frame coordinates from a CSV file

 creating a custom reference frame and import of coordinates from a CSV file
using the Coordinate Configurator Tool
 Map view visualisation of reference frames

 all sites with coordinates defined in the selected reference frame are
highlighted in dark grey colour
 all sites with missing coordinates are shown in light grey colour
Coordinate  create, modify or delete target coordinate systems supported by RTCM

Systems
 datum transformation
 preconfigured datum transformations

 definition of custom datum transformation
 7-parameter Bursa Wolf transformation model
 10-parameter Molodensky Badekas transformation model
 ellipsoids
 preconfigured ellipsoids
 definition of custom ellipsoids
 residuals
 definition of horizontal and vertical residual models (e.g. geoid models)
 projections
 preconfigured projections
 definition of custom projections supported by RTCM
3.1.4 Spider Positioning
3.1.4.1 Real Time Positioning

 Single- and Multi-Frequency real time processing of multiple baselines
General  Real time processing using single reference site or RTCM 3 Master Auxiliary
network corrections (MAC)
 Streaming coordinate output support
 standard COM channels
 TCP/IP
 directly to GeoMoS
 none
 Standard output formats
 NMEA GGQ
 NMEA GGA
 NMEA LLQ
 Leica proprietary
 Processing methods
 Single-Frequency
 Multi-Frequency
 Use of ephemeris
 Broadcast
 Precise

 Supported smoothing methods
Off
5s, 10s, 15s, 20s, 25s, 30s
 Supported initialisation methods
 On Known Point
 While Moving
 Quasi-Static
 Supported satellite systems
 GPS
 GLO
 BDS
Logging  Logging of coordinate output to text files

 Configurable log path
 Product length:
 10min, 30min, 1h, 2h, 4h, 6h, 12h, 1d
 Archive type:
 None
 Zip
 Clean up files:
 Never
 After 1d, 2d, 1w, 2w, 1m, 2m, 3m, 6m, 12m
Rates  Customisable rates

 data rate: 0.05s, 0.1s, 0.2s, 0.5s, 1s, 2s, 3s, 4s, 5s, 6s, 10s, 12s, 15s, …60s

3.1.4.2 Post Processed Positioning
 Single- and Multi-Frequency post processing of multiple baselines
General  Post-processing using RINEX files also downloaded from 3rd party FTP servers
 Support for Meteo file products
 Post-processing modes
 Static
 Kinematic
Logging  Logging of coordinate output to text files and Spider database
Configuration of logged text files

 Configurable log path
 Message type:
 NMEA GGQ
 NMEA GGA
 NMEA LLQ
 Leica proprietary
 Product length:
 1d, 2d, 1w, 2w, 1m
 Archive type:
 None
 Zip
 Clean up files:
 Never
 After 1w, 2w, 1m, 2m, 3m, 6m, 12m

Processing  Cut-off Angle
Parameters  Use Ephemeris
 Broadcast
 Automatic
 use precise ephemeris when available
 Solution Type:
 Automatic
 use code and phase observations for the computation and to resolve the
ambiguities
 if only code or phase measurements are available, the system
automatically switches to use exclusively these measurements for
computation
 Automatic
 use all GNSS data available for reference and rover
 Frequency
 Automatic
 if dual-frequency data is available, both frequencies will typically be used
 if baseline is shorter than 15 km, then L1+L2 will be processed
 if baseline is longer than 15 km
 If ambiguities have been resolved previously, they are introduced into
the ionospheric-free solution
 If ambiguities have not been resolved, the result will be an L3 float
solution
 Tropospheric Model
 Automatic
 Hopfield
 Simplified Hopfield
 Saastamoinen
 Essen and froome
 No Model
 New Brunswick ABC
 Computed Troposphere
 Vienna Mapping Function
 Ionospheric Model:
 Automatic
 selection depends on the duration of the session
 for reference observations longer than 45 minutes, a user defined
ionospheric model will be computed
 with shorter observation periods, the Klobuchar model will be preferred
 if no Klobuchar model parameters are available, no model will be used for
observation times below 45 minutes
 Standard
 No Model

 Computed
 Global Regional
 Klobuchar
3.2 Leica Spider Web Applications

3.2.1 Spider Business Center

Standard Login
Page

Administrator
Portal
Header Bar
Ribbon Bar
Navigation Bar
Report and
Property View
Footer
User Portal
Header Bar
Ribbon Bar
Navigation Bar
Report and
Property View
Footer
3.2.1.2 Preferences
General  Agency name
 Default Language
 Disable site overview map on login page
 Disable shop on login page
 Disable user sign up
 Disable user login
 Disable automatic subscription activation
 Enable customer subscription renewal
 Prevent user from changing user name
 Prevent user from changing password
 Administrator home page
 Users (Individuals, Credentials, devices, Groups)


Service Data (Sales Organisations, Dealers, Subscriptions, Group Subscriptions,
Articles)
 Usage (Site Status, Rover Status)
 Products (GNSS Spider, Various Types)
 Tools (Dashboards, Notifications, Audit Log)
 Settings (Regions, Sign Up, Preferences)
 Audit log retention
 3m, 6m, 9m, 12m
 Support e-mail
 Forward incoming mails
Notifications SMTP Server

 Outgoing Mail server
 SMTP port
 Mail address of sender
 SMTP server authentication (optional)
 User name
 Password
 Show password feature
 SSL/TLS support
 Send test mail

 Disable auto-generated mails
 Redirect contact mail request

Embedded Twitter Timeline
 Twitter timeline
 Twitter account
Documents  Specify Privacy Notice pdf document for download individual per supported
language
 Specify Tems of Use pdf document for download individual per supported
language
Maps  OpenStreetMap support

 Standard maps
 Satellite imagery support for dedicated user levels

 Define a maps section to initialize map views according to your home base
Regions  Create, View and Manage regions for RTK access restriction
 Graphical region definition
 Support of KML format

Infrastructure Services provided by SBC
 Frontend URL
 Enable SBC-HTTP API
 Connection Verification
Public Ntrip Caster access

 Ntrip Caster host name
 Ntrip Caster port
Services where SBC connects to

 Private hostname of X-pos Server
 Public hostname of X-pos Server
 Combined SBC / X-pos installation

Thresholds  Set limits of various indicators across the SBC user interface
 Ambiguity fixing status of reference sites
Corporate Design  Configuration of SBC Administrator and User Portal appearance
 Name of Theme
 Corporate Logo
 Header
Background colour
Actions background colour
Actions foreground colour
 Navigation bar
 Background colour
 Foreground colour
 Selected items colour
 Buttons
 Footer

 Ribbon bar
 Table
 Corporate design preview

 Admin Portal
 Login Page
 User Portal

User registration –  Add custom user profile properties
Sign up form  Set custom properties as mandatory or optional for user registration
 Publish custom parameters for user registration or keep them for internal use
only.
 Translate custom user profile properties for all supported languages

Menu  Footer menu extension
 extend the Footer Menu at the bottom right of the SBC web portal
 menu labels, their content in the form of URLs and their appearance before or
after login can be defined
3.2.1.3 Service Data Management

Supported Services  All GNSS Leica SpiderNET RT-Product Services
 GNSS Spider Status Services
 Site Status
 Network Processing Status
 Rover Status
 All SpiderWeb Services
 RINEX Service
 Virtual RINEX Service
 Coordinate Computation Service and Transformation Service
 Custom defined Services
 e.g. hotline service
Site Status  displays all CORS locations configured in GNSS Spider in a map
 designed to be displayed to administrators of SBC and to customers (privilege:
user) who have a sufficient subscription
 site status update depends on received site data
 Site Status view consists of:
 a map view
 a list of sites view
 all sites configured on GNSS Spider site server appear in the map as well as in the
list view
 callouts provide additional site properties:
 General:
 Site code, RTCM ID, Marker name, Marker number
 Site Status, Network Processing Status, Last Update, Site Server
 Latitude, Longitude, Height,
 Hardware:
 Receiver Manufacturer, Receiver type, Receiver serial number, Receiver
Firmware
 Antenna Manufacturer, Antenna type, Antenna serial number and
Antenna height

 details about the site connectivity and the network fixing status are shown based
on colour codes
 red: site disconnected. No valid raw data stream provided from reference
receiver
 blue: site connected. A valid raw data stream is received from reference
receiver
 green: used for network processing with ambiguities of 5 or more satellites
are fixed on L1 and L2
 other features provided by the site status view
 searching for sites using site code or site name
 layer selection: enable / disable displaying of all configured regions in the map
view
 center on sites: adapt the map section that all sites are displayed; zoom in,
zoom out and full screen view functionalities are available
 switch between administrator view and user view
 hide sites: this list view option allows hiding particular sites for users who
have a site status subscription
Rover Status  lists all GNSS rovers connected via GNSS Spider and displays them in a map
 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 (NMEA
GGA message)
 Rover Status view consists of
 a map view
 a list view
 provides major details of connected GNSS rovers in a paginated grid view
 search is related to all displayed columns
 GNSS rover details:

 NMEA Positioning quality
 Colour coded Fixing Status
 red: not fixed
 blue: fixed (Single Base)
 green: fixed (Network)
 User name
 Rover User Name
 Duration of connection
 Time of last received data set
 Satellites Ref./Rover
 Site Code and RTCM reference station ID as configured in GNSS Spider
 Reference station ID returned from Rover via NMEA data stream
 3D distance between rover and reference station

 Pin Functionality
 supported for one or multiple rovers
 puts the rovers to the top of the list and highlights them in the map with blue
colour
 rover selection is also possible directly in the map view
 use ‘Pin icon’ to create a rectangle and select all enclosed rovers
 all pinned rovers can directly be notified by mail
 all pinned rovers can be disconnected

 Other features
 display total number of connected users
 display number of users with fixed Network RTK solutions (green color
code)
 display number of users with fixed Single Base RTK solutions (blue color
code)
 send RTCM text message to rovers
 disconnect all pinned or individual rovers
 center and display rover user info by icon or clicking the rover icon in the map
 zoom in, zoom out and full screen view functionalities are available
 allows automatic removal of disconnected users or view freezing
 adapt the map section that all rovers are displayed
 center on sites if site layer is active
 compose a message and send it to all or pinned recipients
 disconnect all pinned rovers
 searching for rovers using user name or rover user name
 RT Rover Service connectivity status indicator
 Map layer features

 activate or hide the Site Status layer
 activate or hide the Regions layer
 freeze view
 display map only
 display table only
 display split view

Products  View and Manage all available registered Spider service products
(services are registered to SBC automatically from GNSS Spider Network server or
SpiderWeb)
 Edit service descriptions (meta data)

 Create other custom service products

Articles  Container of products used in subscription process
 Create, View and Manage articles
 Configurable article details:
 Article name
 Article number
 Status
 Public
 Private
 Inactive
 Article description
 Regional restriction (unlimited, one or several regions definition for regional
RTK-Product access restriction)
 Lifetime (default period for subscription expiration)
 7d, 14d, 1m, 3m, 6m, 9m, 1y, 2y, 3y, unlimited
 Price and promotional picture
 Use for automatic subscription

 Configurable Article content:
 One or multiple GNSS Spider RT-Products
 One or multiple SpiderWeb service products
 One or multiple GNSS Spider Status Products
 One or multiple Custom service products
 Sales Organisation Ownership (who can subscribe the article):

 Direct

 Specific Sales Organizations
 Specific Dealers
 Used in subscriptions overview
Subscriptions  One to one relation between User and Article, allows user to access the article
content
 Create, View and Manage Subscription and Group Subscriptions
 Subscription Details:
 Subscription Owner
 First Name
 Last Name
 Company
 Company-ID
 Group Name
 Subscription Content (Article Name)
 Article Number

 Subscription Period
 Consumption limit
 Subscription-ID
 Sales Organisation
 Dealer
 Status
 Created by
 Creation Date
 Initial activation
 Start Date
 Expiry Date
 Renewal Date
 Days to go
 Consumption progress bar
Group Subscription  Relation between a User Group and an Article, allows group members to access
the article content
 Create, View and Manage Group Subscriptions
Details
 Subscription Details:
 Subscription Owner (User Group)
 Member count
 Subscription type
 Subscription Content (Article Name)
 Article Number

 Consumption limit
 Subscription-ID
 Sales Organisation
 Dealer
 Status
 Created by
 Creation Date
 Initial activation
Member Subscriptions
 Manage individual subscriptions per group member
3.2.1.4 SBC User Features

SBC User features  Online registration, incl. selection of preferred language of all available
 Online subscription in web shop
 Online view and re-order of subscribed articles
 Full edit of user profile and credentials

 Change of password
 Request forgotten password
 Contact form to send message to network operator
 Access to Subscribed SBC Services (Site Status, Rover Status)
SBC Administrator  Multiple administration access levels:

features  Administration (full unrestricted access)
 Support Administration (View only access to verify user, services and
subscription status)
 Sales Organization Administration (2nd administration level)
 Dealer Administration (3rd administration level)
 User & groups access, account and subscription management
 Real-time and Post-Processing Service management
 Region management (for regional RTK access limitation)
 Article management
 System configuration
 Multiple languages support
 Email Notification
 Convenient Search & Sorting options to quickly find and access data items
 Dashboard and Audit Log access and management
3.2.1.5 User Management

Individual Users  Create, View and Manage user accounts
Details
 Credentials
 User name
 Password
 Show password functionality
 Manage authentication details for RTK services
 NMEA GPUID
 Telephone number
 IP-Address
 Ntrip
 Personal Data
 First name
 Last name
 Email address
 Preferred language
 Account Status
 Active
 Pending
 Inactive
 Access Privileges
 Sales Organisation/Dealer Ownership
 Company
 User picture
 Other information as requested by the SBC administration (as defined in the
Sign-Up form)

Subscriptions
 View & activate pending subscriptions for articles
 Manage expirations for subscribed articles
 View & renew expired subscriptions

 Manage access and logging policies for RTK services
 Authorize single or multiple simultaneous access
 Set Rover inactivity validation time
 Enable/disable detailed and/or general access logging
 Enable/disable rover NMEA data logging
 Enable/disable displaying the rover user in Live View
 Enable/disable transfer of detailed connection logs via FTP push
 Enable/disable output of rover position to reports
 Set preferred notification method and Ntrip Caster for individual users
User Groups  Create, View and Manage groups of users, e.g. as companies
Group Details
 Group Name
 Sales Organisation/Dealer Ownership
 Description

 Display group members in Live View
 Add and remove users to/from groups
 Activate and suspend group accounts
Group Subscriptions
 View & activate group subscriptions for articles
 Manage expirations for subscribed articles

3.2.1.6 Tools
Dashboard  View several charts summarizing the most important SBC data in a graphical view
 Charts can be exported to a PDF format
 Charts can be added or removed or moved to a different position
 List of charts:
 Number of Users by Status
 Evolution of User Registration
 Credentials
 Number of Subscriptions by Status
 Number of Subscribers
 Top 5 GNSS Rover Types
 Evolution of Subscription Activation
 Subscriptions per Article
 Monthly Subscription Churn Rate
 Monthly Subscription Retention Rate
 New Subscribers per Month

Audit Log  View important events occurring during regular operations
 Audit Log Retention setting
 Supported Events:
 Category User
 Create pending/active user
 Activate user (Modify pending to active)
 Modify user details
 Delete user
 Add user to/delete user from Sales Organization
 Category Subscription
 Create pending/active subscription
 Modify pending/active subscription
 Create user having auto subscription
 Create subscriptions using subscription order wizard
 Create/Modify group subscription
 Delete user groups having active group subscriptions
 Adding/Removing of members in user group who are having subscriptions
 Region added/removed to subscription
 Consumption limit exceeded
 Subscription period expired
 Renew subscription
 Quota counter reset/not reset
 Category Configuration
 Modify Audit log retention
 Modify Hostname of Spider User Connection Log Server
 Category Article
 Modify subscription period
 Modify consumption limit

 Category License Check
 Create/Fail to create new subscription
Notifications  Send Notifications to individual users or user groups

 Copies of notifications also sent to administrators and/or support viewers
 Automatic emails to users for important account and subscription events
 Customisable mail templates in HTML format
 Support for keyword variables

Site Overview  site overview provides the available reference sites on the SBC login page
Forwarding without any site information i.e. site status and callouts
 in order to include the site overview map into any other web application, 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
3.2.1.7 SSL Configurator

Overview  automates the required configuration steps to run SBC as secured web
applications
 supports the creation of so-called Certificate Signing Requests (CSR)
 simplifies the setup and handling of SSL certificates

3.2.1.8 API
Overview  Spider Business Center is provided with an application programming interface
(API) allowing 3rd party mechanisms to interface SBC for direct control and data
extraction
 With help of the API a customer is able to replace some native SBC user portal
functionality, i.e. the registration and subscription process, with its own
implementation
 It is not the content of the API to provide full functionality of the administrator
portal. I.e. the native SBC administrator portal has to be used to, e.g., define
articles, define regions, change general configuration or access any kind of
realtime status
 The SBC API can, e.g., be used to fulfill the following use cases:
 Use an own web portal for user registration and subscription process
(customer web shop)
 Integration of SBC with any 3rd party payment system
Supported API  General

methods  Login to the API to obtain a valid session token
 Get status for currently logged user
 Users
 Obtain a list of users
 Create a new user in pending state
 Delete or deactivate an existing user
 Get the user details of a particular user
 Update an existing user
 Get the GNSS details of a particular user
 Update Rover Settings (GNSS) of an existing user
 Get a list of users details of a particular email
 Get user details of a particular user
 Forgotten password Functionality
 Modify user password
 Subscriptions
 Get the subscription details for set of subscriptions.
 Create a subscription for a user.
 Delete user subscription for a user article.
 Update subscription using subscription Id.
 Create a subscription for a user with subscription Id.
 Delete a subscription for a given user and article.
 Get the subscription details for a particular subscription.
 Update subscription.
 Get the subscription details for a particular user.
 Delete all subscriptions for a user
 Articles
 Obtain a list of articles
 Sites
 Obtain a list of sites
 Rover Connections
 Load all rover connections using the given input filter parameters
 Load all rover connections for a given user using the given input filter
parameters
 Load the connection details for a given connection by its connection ID
 Load all rover connections that do not have any username assigned
 Load the list of currently known event types
 Regions
 Obtain a list of the regions

 Get the region details
 Sales Organisations
 Obtain a list of sales organisations
 Dealers
 Obtain a list of dealers
Swagger User  SBC Swagger User Interface visualizes and interacts with the API’s resources
Interface without having any of the implementation logic in place
 It’s automatically generated from your Swagger specification, with the visual
documentation making it easy for back end implementation and client side
consumption

3.2.2 SpiderWeb

Standard Login
Page
Administrator View
Corporate Header
Main Menu Bar
Vertical
Navigation Bar
Report and
Property View
Footer
3.2.2.2 Configurations
SpiderWeb General
Configuration  Company name:
 Email sender address
 Browser title
 SpiderWeb URL

Layout
 Welcome page picture
 Top-left logo
 Top-right logo
 Bottom image
 Top-left logo link
 Menu bar colour
Data Lifetime
 Raw Data lifetime
1w, 2w, 1m, 2m, 3m, 6m, 12m
 User result files lifetime
 1w, 2w, 1m, 2m, 3m, 6m, 12m
 Coordinate computation results lifetime
 1w, 2w, 1m, 2m, 3m, 6m, 12m
RINEX Job Service  Observer

Settings  Agency
 Enabled RINEX files
 Observation (mandatory)
 Navigation
 Meteo
 Auxiliary
 Maximum Observation Rate
 0.05s, 0.1s, 0.2s, …60s
 General header for all RINEX output
 Additional header for individual RINEX output
 O-file (observation)
 N-file (navigation)
 M-file (meteorological)

 A-file (auxiliary, eg. tilt)
 VRinex-file
Leica SpiderQC  Integrate Leica SpiderQC Output into SpiderWeb

Configuration  Show advanced Leica SpiderQC output to users
Computation  Integrate Leica Computation Service into SpiderWeb

Service  Do adjustment
Configuration  Do blunder check
 Show heights in computation report
 Delete LGO project after computation
 Temporary path for LGO projects
 Select default Coordinate System
 Maximum allowed distance of rover in meters
 Custom ASCII export settings name
 Fully customisable processing parameters via external parameters.ini file

Virtual RINEX  Enable virtual RINEX requests for users
Configuration  Root path for NetCorrection archive
Map Configuration Google Maps

 Google map key
 Midpoint of map
 Zoomlevel
 Map size
 Selected icon color
 white, black, red, blue, yellow, pink or green
 Display legend
 Preview functionality
Traditional Map
 Select map file
 Circle Size in map
 Circle animation
 yes or no
 Selected circle color
 white, black, red, blue, yellow, green

Vertical Menu  can be set for all language versions or for a specific language version
extension
Viewer welcome link
 activate/deactivate and select file
Login welcome link

 activate/deactivate and select file
New menu items

 menu item name
 web link
 link visibility
 administrators
 active users
 viewers
 link opens
 within SpiderWeb
 in a new window
 display link
 on the top
 at the bottom

Billing  activate/deactivate billing information
 billing information are stored in an ASCII billing file on the SpiderWeb server
 GPS RINEX file costs
 per minute
 per epoch
 GPS and GLONASS RINEX file costs
 per minute
 per epoch
 Computation Service costs
 price per one computation run
 Transformation Service costs
 price per one transformation run
 Currency
 List of billing file recipients
 Frequency of billing file sendouts
 daily
 weekly
 monthly
 Activate FTP push of billing file
 FTP server host or IP
 Remote Directory
 IP port
 User name
 Password

3.2.2.3 Site Management
Site Overview  Graphical overview of locations of GNSS sites either in traditional map or in
Google Map with basic Google features (based on map settings)
 Callouts to provide more details about sites
 Drop-down menu to select details of a specific site

Creating New Sites  Visibility
 Yes, if the site is to be available for the logged in user and displayed in the
site map.
 No, to keep the site stored in the SpiderWeb data base but not visible to the
users
 Site Name
 Site Code
 IERS DOMES Number
 Description
 visible in the individual site pop up window in site overview
 Latitude, Longitude, Height
 Creation Date
 Receiver Type and Serial Number
 GPS only
 GPS and GLONASS
 Antenna Type and Serial Number
 Antenna Reference Point
 Coverage radius of the site
 Elevation Mask
 Recording Rate
 Comment about the site visible in the detailed site information
 IP Address of Site Server
 A picture of the site can be uploaded from the Upload site image page feature
 Position of site in traditional map
 click on the map button to open the uploaded map and click into the map to
select the position for the site
 enter the x- and y-map coordinates for the site
 Circle color for the traditional map
 Colour of the Google map icon

 Assigning sites to services
 Activating access to raw data files
Importing Sites  site information can also be uploaded from file

from a file  data in this file has to be semicolon - delimited of file type *.csv

Uploading Site  specific images can be uploaded for specific sites
Images
Viewing Site
Details

Deleting Sites
3.2.2.4 Rinex Job Service

Create New Job  RINEX request
Wizard  Once only (no job name is required)
 Everyday (job name is required)
 Every week on specific days (job name is required)
 start of RINEX file in local time

 duration of RINEX file
 RINEX files type (e.g. navigation, meteo, …)
 observation rate
 satellite systems
 GPS only
 GPS and GLONASS
 selection of GNSS sites
 manually from the list
 manually from the map

 automatically closest to the given position (customizable number of GNSS
sites)
 automatically from the map (customizable number of GNSS sites)
 expiry of repetitive RINEX requests
 RINEX request summary

Manage own/all
repetitive RINEX
jobs
3.2.2.5 Virtual RINEX service

Virtual RINEX  Date of Virtual RINEX file
request overview  Start of Virtual RINEX file in local time
 Duration of RINEX file
 RINEX files type (e.g. observation only)
 Observation rate
 Virtual Station site name
 Virtual Station site code
 Virtual Station position
 manually by entering coordinates
 from the map
 Satellite systems
 GPS only
 GPS and GLONASS
3.2.2.6 Computation and Transformation Service

Computation  Input data
Request overview  upload up to 3 observation RINEX files for the same station in static
computation mode
 upload 1 observation RINEX file for the kinematic and stop&go computation
mode
 upload one ASCII file for transformation run
 GNSS sites selection
 automatic based on uploaded RINEX coordinates
 manual from the list
 manual from the map
 use Virtual Station
 PP computation mode:

static
kinematic
stop and go
transformation to local coordinate system including geoid model
 Select target coordinate system
 Set computation precision for static computation mode
 Manually
 10mm+3ppm
 20mm+5ppm
Transformation  Select available target coordinate system (coordinates systems are managed by
Request overview SpiderWeb Administrators)
 Input data
 upload one ASCII file with a list of cartesian WGS84 coordinates for the
transformation run
 formats supported for the input file :
 point ID, X, Y, Z
 point ID, X, Y, Z [, dX, dY, dZ]
 point ID; X; Y; Z
 point ID; X; Y; Z [; dX; dY; dZ]
 X, Y, Z are the cartesian WGS84 coordinates in meters and dX, dY, dZ
are the related standard deviations
 squared brackets indicate optional parameters

3.2.2.7 Results Menu
Overview  displays all service requests results that have been made by logged-in users
 only successfully processed requests contain links for results download
 status of the requests is indicated by an icon in the right column of the displayed
table

Display Options  User Name
Select the user the results are to be displayed for. Only the administrator can
select all users.
 Logged in users will see their own user names and cannot edit the selection
 Show transactions
 All
 RINEX Downloads
 Coordinates Computations
 Virtual RINEX Requests
 Coordinate Transformations
 Start date
 End date
Results Overview  Date/Time of request
Table  Download link for successfully processed requests
 Request Type (in RINEX requests list the sites for which data was requested in a
job)
 Job Name (only available for repetitive RINEX requests)
 Status icon for each request result
 move the mouse over the icon to display a description of the problem that
occurred during processing
 User
 for a logged in user, the own user name is displayed in this column
 Delete result check box option

 Control buttons
RINEX Job Service  The result of the RINEX job service is a RINEX file or a list of RINEX files for
Results requested sites
 RINEX Job Service Results overview table displays:
 RINEX date and RINEX Time
 Sites
 File Name
 Cost
 Size
 Previous downloads
 Delete RINEX files check box option

 After processing of RINEX request an email is sent to the user with download
links to the SpiderWeb Result page
 Download options:
 Only specific RINEX files
 Download all
 The transaction is billed only after pressing Download File button

 All RINEX files are downloaded as one zip file
Virtual RINEX Job  The result of the Virtual RINEX job service is a Virtual RINEX file for the requested
Service Results position
 Virtual RINEX Job Service Results overview table displays:
 RINEX date and RINEX Time
 Sites
 File Name
 Cost
 Size
 Previous downloads
 Delete Virtual RINEX files check box option
 After processing of Virtual RINEX request an email is sent to the user with
download links to the SpiderWeb Result page
 Download options:
 Only specific Virtual RINEX file
 Download all (as only one position can be introduced in the Virtual RINEX
request, both download options are identical)

 The transaction is billed only after pressing Download File button
 Virtual RINEX files are downloaded as one zip file
Coordinates  The result of the Coordinate Computation request is an email with text report of
Computation computation
Service Results  The results are also stored in SpiderWeb for a pre-configured time interval before
they are automatically deleted
The content of the computation report

 Date and time of data processing
 Chosen computation precision
 Uploaded files for computation
 Permanent GNSS reference stations used for computation
 Up to 3 real CORS sites
 Virtual RINEX
 Rejected baselines:
 due to unresolved ambiguity status
 due to failed comparison of repeated baselines test
 due to detection of outliers
 Baseline Summary:
 Baseline ID
 Date and time of start of observation
 Observation duration
 X, Y, Z
 Slope distance
 Fixing Status
 Result of Baseline Processing
 Total number of computed baselines
 Total number of computed baselines used in adjustment
 WGS 84 Geodetic Coordinates
 B, L, H
 Standard deviations for B, L, H
 Maximum residuals of GNSS baseline in B, L, H components
 Local Grid Coordinates
 Easting, Northing, Ellipsoidal and Orthometric Heights (if geoid model is part of the
target coordinate system)
 DOP values (GDOP, HDOP, PDOP, VDOP)
 Disclaimer
Example of an email with text report of computation

This e-mail is automatically generated on request of ************ by the
SpiderWeb GPS Data Computation Service of Leica Geosystems.

Please do not use the reply facility of your email to respond to the
sender. Any queries or suggestions regarding this GNSS Processing Service
should be addressed to: spiderweb@spiderweb.leica-geosystems.com.
Your data was processed on 11/9/2017 9:59:15 AM.
Your chosen computation precision is 20mm+5ppm.
Your uploaded file(s):

test335e00.17o
Permanent GNSS reference stations used for this computation:

ABTW
BREG
RUTH
Rejected GNSS baseline(s) because of ambiguity unsolved:

none
Rejected GNSS baseline(s) by comparison of repeated baselines:

none
Rejected GNSS baseline(s) by detection of outliers:

none
Baseline summary
---------------------------------------------------
ABTW -- TEST:
11/9/2017 5:00:00 AM 00:59:30 -52346.0189 -6444.3763
30000.1655 60676.5656 yes
BREG -- TEST:
11/9/2017 5:00:00 AM 00:59:30 -9342.6903 -68172.8025
22243.4987 72315.9049 yes
RUTH -- TEST:
11/9/2017 5:00:00 AM 00:59:30 -3804.1428 18083.072
-2437.1522 18638.9031 yes
Results of TEST
---------------------------------------------------
Total number of GPS baselines computed = 3
Total number of GPS baselines used for final computation (after baseline
rejection) = 3
WGS 84 Geodetic Coordinates

---------------------------------------------------
Latitude = 59º 25' 16.12751 N Standard error = 3.584 mm
Longitude = 24º 41' 52.91471 E Standard error = 2.925 mm
Ellipsoidal Height = 44.544 m Standard error = 6.755 mm
Max. residual of GPS baseline in latitude component = 33.28 mm

Max. residual of GPS baseline in longitude component = 14.74 mm
Max. residual of GPS baseline in ellipsoidal height component = 40.07 mm
Local Grid Coordinates ( Local Datum )

---------------------------------------------------
Northing = 6587236.098 m
Easting = 539628.628 m
Ellipsoidal Height = 44.544 m
Orthometric Height = 26.349 m
Dilution Of Precision
---------------------------------------------------
GDOP 1.4 - 1.9, HDOP 0.6 - 0.8, PDOP 1.2 - 1.7, VDOP 1 - 1.5
Disclaimer
---------------------------------------------------

This automatic computation result is only for reference purposes.
Estonian Land Board and Leica Geosystems provide no guarantee regarding
the correctness of this automatic computation (both its method and
result) and shall not be liable for any loss, damage or injury (including
but not limited to consequential loss, damage or injury) however caused,
which may arise directly or indirectly from the use or application of
this automatic computation result. Please verify this automatic
computation result before use.
Transformation  The result of the Transformation service request is an email with text report of
Service Results transformed coordinates
 The results are also stored in SpiderWeb for a pre-configured time interval before
they are automatically deleted
The content of the transformation report

 SpiderWeb verion
 Date/Time of request
 Input file name
 Target Coordinate System
 Output file name
 List of points with transformed coordinates
Example of an email with text report of computation

#SpiderWeb V5.0, build 5599
#Date/Time: 1/18/2015 1:25:16 PM
#Input file: LGTB_spider.csv
#TargetSystem: Local Datum
#Output file: 20150118_ LGTB_spider.csv_Local_Datum.txt
ABTW;6546481.162;696627.174;59.805;42.613
BREG;6475831.296;518328.635;41.697;21.429
FLUM;6506573.264;416133.958;32.655;12.171
KALT;6498243.556;478667.746;42.393;21.934
RUTH;6540191.857;426403.159;38.413;18.098
3.2.2.8 Statistics
RINEX, Virtual  available for users and administrators
RINEX Downloads  lists all downloads that have been done for each registered user
 administrators can choose a month and for this month and a selected user
(or all users) all downloaded files are listed
 users can select a month and for this month and this user, all downloads will
be listed.
 users cannot display the downloads for other users

Computation  available for users and administrators
Service  lists all coordinate computations and transformations that have been done for
each registered user
 administrators can choose a month and for this month and the selected user
(or all users), all coordinate computations are listed
 users can select a month and for this month and this user, all coordinate
computations will be listed
 users cannot display the coordinate computations for other users
All Statistics:  only available for administrators

RINEX , Virtual  lists all downloads that have been done for each registered user or from each
RINEX Downloads configured site
 administrators can choose to sort all downloads by site or by user
 after selecting a month, all downloads for all users (or sites) are listed
 by clicking on an underlined user ID in the list of downloads, a new window
opens, showing all sites from which this user downloaded data during the
selected month
All Statistics:  only available for administrators

Computation  lists all the transformations and coordinate computations that have been done
Service for each registered user or with each configured site
 administrators can choose to sort all computations by site or by user

 If “List by User” is chosen, the table lists all coordinate computations and
transformations done in the current month sorted alphabetically by users
 When listing by User: Clicking on one of the underlined user IDs opens a
page that displays the coordinate computations this user did for the
chosen month. The list is sorted by date and time.
 If “List by Site” is chosen, the page lists for each site how many coordinate
computations it had been included in and what the costs were. The list is
sorted alphabetically by site name
 When listing by Site: Clicking on one of the underlined site IDs opens a
page that displays each coordinate computation this site has been included
in for the chosen month for each user.
3.2.2.9 Tools
Email to all users  send email to all or only specific users
SpiderWeb Mail SMTP Server

Setup  Outgoing Mail server hostname or IP address
 SMTP port
Authentication
 Mail address of sender
 SMTP server authentication (optional)
 User name
 Password

Leica Tools  allows for integration of value added services into SpiderWeb portal
Integration  allows for integration of user authentication of SpiderWeb services
Database Tools  Database setup tool
 Database backup and restore tool

Spider Sites Export  allows to export sites from Spider Site server database into a csv file
Tool  the sites csv file can be directly imported into SpiderWeb database
Localisation  SpiderWeb can easily be translated into as many languages as necessary

 by default SpiderWeb is available in English
 other currently available languages can be downloaded from the Leica myWorld
web portal
 the English language file is called “ENSpiderWeb.xml”
 in order to translate SpiderWeb into other languages, the English language file
needs to be copied, renamed and translated
 files for several languages can be stored in the language directory
 for each file, the language short cut will be displayed. clicking on a short cut in
the main SpiderWeb window will change the language accordingly
 if SpiderWeb is to be used in conjunction with SpiderQC, the SpiderQC web
output should be translated as well. The language files for the SpiderQC results
output can be found in SpiderQC language directory

3.3 Leica SpiderQC
3.3.1 General Layout
Menu Bar
Toolbar
Report View
Tabbed View
Status Bar
3.3.1.2 General Settings

Quality Testing General thresholds
and Processing  Elevation Mask
 Minimum SV
 Minimum SNR
 Report Data Gap
 Report Missing SV
 Show extended output

 Auto save QC report

Cycle Slip Detection
 Cycle slip detection processing parameters
 Cycle slip management
Multipath Estimation Parameters

 MP moving average settings

Quality Testing
 Pass/Fail tests criteria
 Ignore orbit related problems checkbox
 Minimum Epochs with Minimum SV threshold
Required Observation Types

Single Point Positioning Processing Parameters
 Frequency
 L1
 Iono Free
 Troposphere Model
 None
 Saastamoinen
 Modified Hopfield
 Ionosphere Model
 None
 Klobuchar
 Stochastics
 A priori sigma
 Weighting Model
 Equal
 Elevation Dependent
Satellite Status

 disabling satellites from quality analysis
General Settings  Reference Coordinates File

 UTM Projectsion
 Dispay Time Settings
Automatic RINEX General settings and thresholds

Quality Check  Program Mode:
 Stand-alone
 Integrated with SpiderWeb
 Resume automatic processing on program startup
 Load automatically on system startup
 Last file expiry threshold

 Check for late file rate threshold
 Store individual QC report files setting

Archiving
 Set path for archiving data
Global Navigation Files

 Manage use of global navigation files
 File Site ID
 Archive Type
 None
 Zip
 Unix compress
 Multiple Extensions
 No
 *.??o.zip
 *.rnx.zip
 Root path
 Fully customisable folder structure
 Example path and filename

Output
 Create web pages
 Create graphic files
 by Calendar month
 by GPS week
Security
 monitor files by types (file extensions)
 include files with no extension
 delete unexpected files

Site Status
 Status Test Range
 Status States (colour codes)
 QC fails
 Files not available
 Overall (not available and/or QC fails)
Connections NMEA / Spider RT Positioning

 General options
 Update plot rate
 Webpage output rate
 Automatic reconnection setting
 Time periods
 Time period to store in memory
 Time period to display as default
 Plot Options
 Plot title
 Automatic scaling the plot to fit the data

Spider PP Positioning
 General options
Update plot rate
Webpage output rate
Automatic reconnection setting
 Time periods
 Plot Options
 Plot title
SINEX Processing
 General options
 Time periods

Time period to store in memory
Time period to display as default
 Plot Options
 Plot title
Nivel200
 General options
 Time periods
 Plot Options
 Plot title
Spider Network

 General options
Update plot rate
Webpage output rate
Automatic reconnection setting
 Display Options
 Time period to show global RMS values
 Extrapolation distance
Graphing General
 Plot Size
 Line Graph Options
 Vector Plot and Map Options
 General Colours
QC Graph Extends
 Graph Types
 Cycle Slips
 Cycle Slips per 1000 Observations
 DOP


Latency

Multipath

Number of Satellites

Outliers

Percentages
 Configurable values
 Minimum
 Maximum
 Ticks
Displacement Graph Extends

 Graph Types
 2D / Coordinate Quality
 3D
 Longitudinal
 Transverse
 Easting/Northing
 Height
 2D Scatter
 HDOP
 Satellites Used
 Age of Data
 Vectors
 Scale Factor
 Reference Length
 Minimum
 Maximum
 Ticks

Troposphere Graph Extends
 Graph Types
 Zenith Path Delay
 Zenith Gradients
 Minimum
 Maximum
 Ticks
Network Error Map Extends

 Graph Types
 Ionosphere
 Troposphere/Geomertry
 Minimum
 Maximum

Tilt Graph Extends
 Graph Types
 Tilt
 Temperature
 Minimum
 Maximum
 Ticks
Messaging General
 Minimum disk space
 Intercal for status OK message
Email Messaging
 Email content parameters
 From Name
 From Email Address
 To Email Address
 CC Email Addresses
 Domain

 Mail Server
 Port
 Send Test Email Functionality
SMS Messaging
 COM Port Settings for the GSM device
 COM Port
 Baud Rate
 GSM SettingsDomain
 Check that modem responds with OK
 Send PIN code
 PIN code
 Test Connection Functionality
Map Display  Plot coastline

 Coast line source file selection
 Plot background image
 Background image source file selection
 Georeferencing
 Latitude and Longitude of upper left corner
 Latitude and Longitude of lower right corner
 Specify Map Boundaries
 Latitude Min and Max
 Longitude Min and Max

Web Settings General
 Web Path Root Directory
 Force use of asp.net directed links
QC
 Up to 8 different plots per page
 Available satellite systems
 All (total amount)
 GPS specific
 GLO specific
 GAL specific
 BDS specific
 QZSS specific
 Graph Types
 Cycle Slips
 Cycle Slips per 1000 Observations
 Overall Data Completeness
 % Complete Observations
 % Epochs Min SV
 % Epochs With Data
 Multipath (for different frequencies)
 Average Tracked Satellites
 Outliers
 Latency
 PDOP
 GDOP
 Pressure

 Dry Temperature
 Relative Humidity
 Wind Speed
 Rainfall
 X Tilt
 Y Tilt
 Plot Data Range
 File Report Length
 Availability Report Length
 Include receiver name in the overview page option
 Include links to the QC reports option
NMEA / Spider RT Positioning

 Graph Types
 2D Time Series
 3D Time Series
 Longitudinal Time Series
 Transverse Time Series
 Easting Time Series
 Northing Time Series
 Height Time Series
 2D Scatter
 2D Vector
 Height Vector
 2D Velocity
 Height Velocity
 Coordinate Quality Time Series
 HDOP Time Series
 Satellites Used
 Age of Data
 Easting Velocity Time Series
 Northing Velocity Time Series
 3D Velocity Quality Time Series
 Include connection status information option

Spider PP Positioning
 Graph Types
 2D Time Series
 3D Time Series
 2D Scatter
 2D Vector
 Height Vector
 2D Velocity
 Height Velocity
 HDOP Time Series

SINEX
 Graph Types
 2D Time Series
 3D Time Series
 2D Scatter
 2D Velocity
 Height Velocity
 Troposhere Zenith Path Delay
 Troposhere East Gradient
 Troposhere North Gradient
Language
 Selection of languages of the web page output
 The list of supported languages depends on the availability of language files in
the SpiderQC Root Directory
3.3.1.3 Limit Checks and Messaging

Limit Checks  Limit (tolerance) checks generate messages and events when received
coordinates differ by more than a certain amount from the known a priori
(reference or null) values
 Limit Classes hold a set of thresholds for displacement/statistics/tilt indicators
 Each Limit Class has up to eight different limit checks
 Supported methods
 NMEA / Spider RT Positioning
 Spider PP Positioning
 Nivel200
Limit Check NMEA / Spider NMEA with Apply Spider PP Nivel200

Type RT Positioning Statistics option Positioning
Longitudinal ● ●
Transverse ● ●
Height ● ●
2D ● ●
3D ● ●
2D ●
Accuracy
Height ●
Accuracy
Availability ●
X Tilt ●
Y Tilt ●
Messaging and  list of events that can trigger notifications and alarming
Events  events are generated by the automatic RINEX processing or by coordinate
analysis components
 limit checks are taken into account
 supported notification methods
 email
 SMS
 running a 3rd party application via command line

3.3.2 Manual Data Quality Check
3.3.2.1 Quality Check

 Summary of key quality and quantity (tracking) information
 HTML output
 Critical problems are highlighted for quick analysis
 Includes data completeness, satellite tracking, cycle slip, multipath, receiver clock
and formatting information
 Supports GPS and mixed GPS/ GLONASS/ Galileo/ BDS data
 Supports RINEX versions 2.1, 2.11, 2.12, 3.0, 3.01 and 3.02

3.3.2.2 Quality Check (Comparison)
 Summary of key quality and quantity (tracking) information for multiple sites
 HTML output
 Includes observation count, tracking performance, data completeness, SNR,
multipath, loss of lock
 Supports GPS and mixed GPS/ GLONASS/ Galileo/ BDS data
 Supports RINEX versions 2.1, 2.11, 2.12, 3.0, 3.01 and 3.02

3.3.2.3 SNR Analysis
 Numerical summaries and graphical views of L1/ E1/ B1, L2, L5/ E5a, E5b/ B2 and
E5a+b signal to noise ratios
 Display SNR as sky plots or as scatter plots against satellite elevation
3.3.2.4 Multipath Analysis

 Numerical summaries and graphical views of code and phase multipath on L1/
E1/ B1, L2, L5/ E5a, E5b/ B2 and E5a+b for single, dual and triple frequency data
 Display multipath as residuals on a satellite track, time series of residuals
together with satellite elevation, RMS on a skyplot, and RMS versus satellite
elevation
3.3.2.5 Tracking Analysis

 Numerical summaries and graphical views of locations of obstructions and cycle
slips on L1/ E1/ B1, L2, L5/ E5a, E5b/ B2 and E5a+b for single, dual and triple
frequency data
 Display tracking info as sky plots or as scatter plots against time
3.3.2.6 Receiver Clock Analysis

 plot and analyse receiver clock offset

3.3.2.7 Residual Analysis
 zero, single, double, triple and time difference residual analysis computed from
the loaded RINEX files
 different frequencies supported
 choice of corrections to be applied
 phase levelling options
 potential use:
 detect unflagged cycle slips
 measure GLONASS hardware biases
 analyze the effectiveness of measurement differencing and other linear
combinations
 …
 ideal for studying or teaching GNSS data processing
 supports mixed GPS/ GLONASS/ Galileo/ BDS data
 supports GLONASS bias calibration

3.3.3 Automated Analysis of Reference Station Data
3.3.3.1 Automatic Quality Check

 Scheduled processing of RINEX files generated by a reference network
 Set thresholds to govern the test criteria for the quality check
 Email warning messages when specified test criteria fail
 Individual reports generated for each file processed
 Results stored in a database for generation of graphs, reports and web pages
3.3.3.2 Web Page and Status Information

 Key information displayed in a customisable multi-language web page
 User definable traffic light status displays based on the results of the most
recent data processed for each station
 Contents include: traffic light status, quality indicator plots, file by file quality
information and file availability
 Direct links to Leica GNSS Spider and Leica SpiderWeb are supported
3.3.3.3 Graphs and Reports

 Make graphs of key quality indicators for each station
 Graphs include: cycle slips, multipath, data completeness, data latency and many
more
 Create HTML reports that show summary information or detailed results of data
processing
 Reports include: statistics of pass/fail tests, average values for key quality
indicators and file by file results of the quality check

3.3.4 Other Automated Services
3.3.4.1 Network RTK Analysis

 Graphical display of residual ionosphere and troposphere error across an RTK
network
 Calculated in real time using data from Leica GNSS Spider network RTK
processing
 Maps for both network RTK users and nearest site users
 Time series of global RMS values
 Web page output of residual error maps

3.3.4.2 Coordinate Analysis
 Display time-line or scatter plots of coordinate displacements from real time data
streams or pre-logged files
 Formats supported include NMEA GGA, GNS, GGQ, LLQ, LVM, LDM and comma
separated (CSV) files from LGO
 Multiple real time high speed and Spider PP Positioning connections
 Graphical display of longitudinal, transverse, height, easting, northing, 2D and 3D
displacement time series and 2D scatter plots
 Limit checks and messaging (run application, email and SMS) are supported

 Web page output of displacements calculated from real time NMEA / Spider RT
Positioning data
3.3.4.3 Inclination Analysis

 Display time-line or scatter plots of inclination (x-tilt, y-tilt) and internal
temperature from real time data streams or logged files from Leica Nivel210/220
inclination sensors
 Formats supported include Leica binary format and comma separated (CSV) files
 Multiple real time high speed connections
 Graphical display of x-tilt, y-tilt, temperature and scatter plots
 Limit checks and messaging (run application, email and SMS) are supported
 Web page output of inclination and temperature from real time data streams

3.3.5 Tools
3.3.5.1 Ionosphere Plots

 Use IONEX files from CODE and IGS to make maps of the total electron content
 Make animated or static maps
 Display day/night, annotations and geomagnetic equator
 Supports IONEX version 1.0
3.3.5.2 Analysis of Spider Rover User Logs

 statistics on the fixing performance of rovers connected to GNSS Spider based
on General Connection Logs and NMEA Connection Logs generated by Leica GNSS
Spider
General  Number of Authorised Connections

Connection Log  Number of Unauthorised Connections
 Total number of Customers:
 Total number of Products
 Total connection time
 Average connection time
 Summaries of usage by time, products and users

 Display of all connections in the Google Map view
NMEA Connection  Number of rover connections

Log  Number of valid & invalid NMEA records received
 Total connection time
 Average connection time

 Average time to fix
 Median time to fix
 Percentage of connections with RTK fix
 Display of NMEA log positions in the Google Map view

3.3.5.3 Other Tools
RINEX Data  Decimation of RINEX observation files
Management  Concatenation of RINEX observation, GPS navigation, GLONASS navigation,
Galileo navigation and BDS navigation files
Date and Time  convert between common time formats used in GNSS
Conversion Tool  Civil Dates (calendar day, month and year)
 RINEX file name (day of year and file ID)
 GPS week, day of GPS week and seconds of GPS week
 Modified Julian Date
 Julian Date
Edit Coordinates  extract and display coordinates

 open an existing Bernese format *.CRD or *.CSV coordinate file
 save points as a Bernese format *.CRD coordinate file
 extract coordinates from a SINEX file
 extract coordinates from one or more RINEX observation files
 extract coordinates from a Leica GNSS Spider Site Server
 add new, edit or delete selected coordinates

 display the coordinates as Cartesian, Geographic or in UTM projection
Plot Map  plot a map of station coordinates

 supported sources of coordinates include:
 Bernese format *.CRD or *.CSV coordinate file
 Leica GeoMos Database
 Leica GNSS Spider Database
 plot settings include
 Use Google Maps
 Draw coastline
 Draw TIN
 Show interstation distances
Geodetic  supported sources of coordinates include:

Computations  Bernese format *.CRD file
 Output includes:
 The ellipsoid used for the calculations
 Forward Azimuth

 Reverse Azimuth
 Chord Distance between the two stations
 The ellipsoidal distance between the two stations
 Linear and Angular Units
Plotting and  Plot Rover NMEA Logs

Display Tools  Plot Offline Coordinate Time Series
 Plot Offline Meteo Data
 Plot Offline Auxiliary Data
 Plot Offline Inclination Time Series

Original text
Printed in Switzerland
Leica Geosystems AG
Heinrich-Wild-Strasse
CH-9435 Heerbrugg
Switzerland
Phone +41 71 727 31 31
www.leica-geosystems.com

Leica Spider Software Suite PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Leica Spider Software Suite PDF

Uploaded by

Copyright:

Available Formats

Leica Spider Software Suite

Leica Spider Software Suite – Technical Data 1

Leica Spider Software Suite – Technical Data 2

In this brochure Chapter

Leica Spider Software Suite – Technical Data 3

Leica Spider Software Suite – Technical Data 4

Leica Spider Software Suite – Technical Data 5

1.1 Leica GNSS Spider

Leica Spider Software Suite – Technical Data 6

1.1.1 Spider Site Servers

1.1.2 SpiderNET – Network RTK

Leica Spider Software Suite – Technical Data 7

i-MAX – Individualized MAX

Virtual Reference Station

Your Benefits For the system provider:

For the rover users:

1.1.3 Spider Positioning Services

Leica Spider Software Suite – Technical Data 8

Value added RINEX Jobs Service

Virtual RINEX Service

Coordinate Computation and Transformation Service

Status and Quality Service

Easy – Flexible –  Online registration and subscription to services

1.2.2 Spider Business Center

Leica Spider Software Suite – Technical Data 9

1.3 Leica SpiderQC

Leica Spider Software Suite – Technical Data 10

Leica Spider Software Suite – Technical Data 11

Leica Spider Software Suite – Technical Data 12

Leica Spider Software Suite – Technical Data 13

2.2.1.1 GNSS Spider Client

Leica Spider Software Suite – Technical Data 14

2.2.1.2 GNSS Spider Windows Services

Leica Spider Software Suite – Technical Data 15

GNSS Spider – SpiderNET module comprises the following services:

Leica Spider Software Suite – Technical Data 16

2.2.1.3 GNSS Spider SQL Database

1 Ntrip – Networked Transport of RTCM via Internet Protocol

Leica Spider Software Suite – Technical Data 17

2.2.2 Spider Web Applications

Leica Spider Software Suite – Technical Data 18

2.2.2.3 SpiderWeb SQL Database

Leica Spider Software Suite – Technical Data 19

Leica Spider Software Suite – Technical Data 20

2.2.2.5 Spider Business Center Windows Services

Leica Spider Software Suite – Technical Data 21

2.2.2.6 Spider Business Centre SQL Database

2.2.3.1 SpiderQC Application

Leica Spider Software Suite – Technical Data 22

2.2.3.3 SpiderQC Database

Leica Spider Software Suite – Technical Data 23

2.2.4.1 Client License Manager

Leica Spider Software Suite – Technical Data 24

2.2.4.2 Local License Server Windows Services

2.2.4.3 CLM Database

Leica Spider Software Suite – Technical Data 25

2.3.2 Operating System and other Software Requirements

Operating System Version Recommended Service Pack2

2.3.3 Hardware Requirements

 GNSS Spider GUI only Minimum

2 Later service packs should be used if available.

Leica Spider Software Suite – Technical Data 26

 GNSS SpiderNET installation Minimum Recommended