Documente Academic
Documente Profesional
Documente Cultură
RINEX
Combine data from different manufacturers GPS receivers For static data processing and archive
NMEA
Transmission of data between GPS receiver and other devices (e.g. GPS antenna PDA with ArcPad software) For real time positioning
RTCM
Transmission of data between GPS receivers (e.g Base Rover) Binary file (more compact but difficult to understand) For real time DGPS/RTK corrections
NMEA Data
Introduction
NMEA data transfer from GPS antenna to PDA with ArcPAD software
(X,Y,Z,t)
Data Centre
NMEA 0183 Real Time Position of Rover
ASCII file
Easily readable (even by people) Less compact than binary
NMEA settings
Baud rate: 4800 (4800 characters in one second ) Data bits: 8 (Bit 7 set to 0) Stop bits: 1 or 2 Parity: none
The send device and receive device should have same setting so as to transfer the NMEA data
$aaaaa, df1,df2
Each message start with $ Five characters after $ are address field Multiple data fields delimited by commas Check sum (optional): a 2-character field (0-9,A-F) to increase data integrity (*) character placed after the last data field
Sentence structure
Talker sentence
Example
$GPGGA,031956,2218.2035,N,11410.7595,E,1,04,3,9,005.9,M,-001.3,M,,*51
Query sentence
A computer (CC) is requesting from GPS device (GP) the GGA sentence
Proprietary sentence
Format: $PmmmA,df1,df2,.[CR][LF]
P indictes it is a proprietary message mmm define as the manufacture The fifth character is a letter (A-Z) defines the specific message type
Example $PLEIS,AHT,0,1.90,0*34
LEI" is Leica manufacturer S for set command The message set the antenna height at 1.9m in the configuration of the internal sensor setting.
Description
Global positioning system fixed data Geographic position - latitude / longitude GNSS DOP and active satellites GNSS satellites in view Recommended minimum specific GPS data Course over ground and ground speed
To extract information related to surveyed position Record at least one of the 3 sentences: $GPGGA, $GPGLL, $GPRMC
Field
Sentence ID UTC Time Latitude N/S Indicator Longitude E/W Indicator Position Fix Satellites Used HDOP Altitude Altitude Units Geoid Separation Seperation Units Time since DGPS DGPS Station ID Checksum
Example
$GPGGA 092204.999 4250.5589 S 14718.5084 E 1 04 24.4 19.7 M
Comments
hhmmss.sss ddmm.mmmm N = North, S = South dddmm.mmmm E = East, W = West 0 = Invalid, 1 = Valid SPS, 2 = Valid DGPS, 3 = Valid PPS Satellites being used (0-12) Horizontal dilution of precision Altitude (WGS-84 ellipsoid) M= Meters Geoid separation (WGS-84 ellipsoid) M= Meters in seconds always begin with *
*1F
Fix quality:
0 1 2 3 4 5 = = = = = = invalid GPS fix (SPS) DGPS fix PPS fix Real Time Kinematic Float RTK
Field ID Latitude N/S Indicator Longitude E/W Indicator UTC Time Status Checksum
Comments ddmm.mmmm N = North, S = South dddmm.mmmm E = East, W = West hhmmss.sss A = Valid, V = Invalid
Satellite used on channel 12 Position dilution of precision Horizontal dilution of precision Vertical dilution of precision
*70
*25
References
NMEA data
http://www.gpsinformation.org/dale/nmea.htm
Outline
Background RTCM Data Format RTCM Message Types Transmission method of RTCM data RTCM data used in Network-RTK
(X,Y,Z,t)
Data Centre
NMEA 0183 Real Time Position of Rover
RTCM 2.0
for DGPS applications only (message 1,9) and no RTK data
RTCM 2.1
retain the full content of RTCM 2.0 add new messages for carrier phase data and RTK corrections
RTCM 2.2
contain GLONASS data and associated information store in newly added messages 31-36
RTCM 2.3
antenna types (message 23) ARP information (message 24)
RTCM 3.0
RTCM 2.3 requires 4800 bps to broadcast dual-frequency code and carrier-phase observation corrections of 12 satellites. The information content is send with 1800 bps in RTCM 3.0 accommodate for new GNSS systems that are under
New messages
added in RTCM2.2
New messages
added in RTCM2.3
RTCM Message 20
References