iG5 User Manual
58
OPUS assumes that all CORS data is perfect, so if a baseline
solution appears to be noisy, then (obviously) your rover data
must be at fault.
In other words, any high residuals in the baseline processing
are the fault of the user data and are never a result of bad
CORS station data. Even when the CORS station data is bad.
OPUS error messages are structured based on this
assumption of highest quality CORS data and low
expectations of your user data quality.
While most CORS stations are:
•
sited at excellent stable locations
•
have 100% open sky view above 10 degree
elevation in all directions
•
have top quality leveling mounts
•
are bolted to stable masonry structures or well-
engineered ground monuments
•
have booked coordinates that are within 2 cm of
their apparent actual location
•
have state of the art choke ring antenna
•
have short, high-quality low-loss coaxial antenna
cables with dielectric filled connectors
•
enjoy top of the line GNSS receivers with the latest
firmware
Stuff happens and some of the CORS stations are unreliable
and a few are horrible. No matter how bad a station might
be, NGS CORS will collect the bad data and the OPUS engine
will use the bad data and then blame your occupation for all
issues.
Содержание iG5
Страница 1: ...iG5 Static GNSS Receiver User Manual Revision V 2021 03 23...
Страница 4: ...iG5 User Manual 4...
Страница 50: ...iG5 User Manual 50...