43
Defining the Raw
Data Generated by
the CORS Station
Click on
Data Output
and then on the
Raw Data
submenu. Use
the page that opens as explained below:
•
All ATOM and Ashtech legacy raw data message types are
listed below.
(Typically, a G-file should contain NAV, RNX and ATR data
to guarantee successful conversion of the file into RINEX
files. NAV provides navigation data, RNX observations
data, and ATR external sensor data.)
•
Follow the instructions below to define the output of
ATOM message types:
– For each ATOM message type you need to define,
select it from the
Message
drop-down list, then select
the output port (“R - Session” necessarily) from the
Output
drop-down list, then enter its output rate, in
seconds, in the
Rate
field, and finally click on the
Add
button. The new message definition will then appear as
a new row in the table on the right.
NOTE: You don’t have to define an output rate for EVT
and DAT.
– Should you change the definition of an existing
message, select the corresponding row in the table.
This populates the fields on the left with the definition
of that message. Edit the definition and then click on
the
Modify
button to save your changes.The table row is
updated accordingly.
Note that depending on the current selection on this
page, the button located underneath the fields on the
left may be either grayed or with a different label (
Add
or
Modify
).
– Deleting a message definition can be done by simply
clicking on the corresponding “trash” sign in the
Clear
column on the far right. This deletes the table row.
There is also a
Clear All
button under the table that
allows you to delete all message definitions from the
table in one click.
•
Follow the same instructions as above to define the output
of Ashtech legacy message types. Note that you don’t have
to define an output rate for SBD.
Format
Message types
ATOM
NAV, PVT, ATR, DAT, EVT, RNX
Ashtech legacy
DPC, SAL, SAG, SAW, SNG, SNV, SNW, ION, SBD,
MPC, PBN
