{"id":3592,"date":"2023-12-07T01:00:38","date_gmt":"2023-12-07T01:00:38","guid":{"rendered":"\/kb\/?post_type=ht_kb&p=3592"},"modified":"2024-02-17T17:22:52","modified_gmt":"2024-02-17T17:22:52","slug":"rtcm-3-message-list","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/rtcm-3-message-list\/","title":{"rendered":"RTCM 3 Message List"},"content":{"rendered":"

A complete list of all adopted RTCM 3 Messages with brief commentary.<\/strong><\/p>\n

The official release of the standard at this time is called:
\nRTCM 10403.4, Differential GNSS (Global Navigation Satellite Systems) Services
\n– Version 4\u00a0\u00a0<\/em> (published December 01, 2023<\/span>)<\/strong><\/p>\n

Purchase a copy from RTCM here<\/a>.<\/p>\n

Comments<\/h3>\n

If you are interested in the messages you are more likely to encounter in the real world, here is a link to our popular RTCM 3 cheat sheet<\/a> summary.\u00a0 By contrast, the list below contains all<\/span> official messages defined in the current published standard. [If you are not an active member of the RTCM SC-104 efforts, we do not recommend that you attempt to deploy the experimental messages the committee has in development at any given time as they are almost certain to change.]<\/p>\n

The text below is taken from the pop-up tool tips that SNIP<\/strong><\/span> will display when decoding various messages from an NTRIP stream.\u00a0 Unlike most NTRIP Casters<\/a>, SNIP<\/strong> <\/span>has the ability to decode and process the RTCM messages to provide additional functionality.<\/p>\n

The Message List<\/h3>\n

 <\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Msg#<\/strong><\/span><\/td>\nMessage Name & Usage Commentary<\/strong><\/span><\/td>\n<\/tr>\n
1~100<\/span> <\/strong><\/td>\nExperimental Messages
\n<\/strong>The messages in this range are temporary value assignments used by the RTCM SC-104 committee to develop and validate new messages before formal adoption and assignment of a permanent value.<\/td>\n<\/tr>\n
1001<\/span> <\/strong><\/td>\nL1-Only GPS RTK Observables<\/a>
\n<\/strong>This GPS message type is not generally used or supported; type 1004 is to be preferred.<\/td>\n<\/tr>\n
1002 <\/strong><\/span><\/td>\nExtended L1-Only GPS RTK Observables<\/a>
\n<\/strong>This GPS message type is used when only L1 data is present and bandwidth is very tight, often 1004 is used in such cases (even when no L2 data is present).<\/td>\n<\/tr>\n
1003<\/span> <\/strong><\/td>\nL1&L2 GPS RTK Observables<\/a>
\n<\/strong>This GPS message type is not generally used or supported; type 1004 is to be preferred.<\/td>\n<\/tr>\n
1004<\/span> <\/strong><\/td>\nExtended L1&L2 GPS RTK Observables<\/a>
\n<\/strong>This GPS message type is the most common observational message type, with L1\/L2\/SNR content. This is the most common legacy message found.<\/strong><\/td>\n<\/tr>\n
1005<\/span> <\/strong><\/td>\nStationary RTK Reference Station ARP<\/a>
\n<\/strong>Commonly called the Station Description<\/em> this message includes the ECEF location of the antenna (the antenna reference point (ARP) not the phase center) and also the quarter phase alignment details.\u00a0 The datum field is not used\/defined, which often leads to confusion if a local datum is used. See message types 1006 and 1032. The 1006 message also adds a height about the ARP value.<\/td>\n<\/tr>\n
1006<\/span> <\/strong><\/td>\nStationary RTK Reference Station ARP with Antenna Height<\/a>
\n<\/strong>Commonly called the Station Description<\/em> this message includes the ECEF location of the antenna (the antenna reference point (ARP) not the phase center) and also the quarter phase alignment details.\u00a0 The height about the ARP value is also provided. The datum field is not used\/defined, which often leads to confusion if a local datum is used. See message types 1005 and 1032. The 1005 message does not convey the height about the ARP value.<\/td>\n<\/tr>\n
1007<\/span> <\/strong><\/td>\nAntenna Descriptor<\/a>
\n<\/strong>A textual description of the antenna \u201cdescriptor\u201d which is used as a model number. Also has station ID (a number). The descriptor can be used to look up model specific details of that antenna.\u00a0\u00a0 See 1008 as well.\u00a0 Search for ADVNULLANTENNA for additional articles on controlling this setting.<\/td>\n<\/tr>\n
1008<\/span> <\/strong><\/td>\nAntenna Descriptor and Serial Number<\/a>
\n<\/strong>A textual description of the antenna \u201cdescriptor\u201d which is used as a model number, and a (presumed unique) antenna serial number (text). Also has station ID (a number). The descriptor can be used to look up model specific details of that antenna.\u00a0\u00a0 See 1007 as well. Search for ADVNULLANTENNA for additional articles on controlling this setting.<\/td>\n<\/tr>\n
1009<\/span> <\/strong><\/td>\nL1-Only GLONASS RTK Observables<\/a>
\n<\/strong>This GLONASS message type is not generally used or supported; type 1012 is to be preferred.<\/td>\n<\/tr>\n
1010<\/span> <\/strong><\/td>\nExtended L1-Only GLONASS RTK Observables<\/a>
\n<\/strong>This GLONASS message type is used when only L1 data is present and bandwidth is very tight, often 1012 is used in such cases.<\/td>\n<\/tr>\n
1011<\/span> <\/strong><\/td>\nL1&L2 GLONASS RTK Observables<\/a>
\n<\/strong>This GLONASS message type is not generally used or supported; type 1012 is to be preferred.<\/td>\n<\/tr>\n
1012<\/span> <\/strong><\/td>\nExtended L1&L2 GLONASS RTK Observables<\/a>
\n<\/strong>This GLONASS message type is the most common observational message type, with L1\/L2\/SNR content.\u00a0 This is one of the most common legacy messages found.<\/strong><\/td>\n<\/tr>\n
1013<\/span> <\/strong><\/td>\nSystem Parameters<\/a>
\n<\/strong>This message provides a table of what message types are sent at what rates.\u00a0 This is the same information you find in the Caster Table (this message predates NTRIP).\u00a0 SNIP<\/strong><\/span> infers this information by observing the data stream, and creates Caster Table entries when required.\u00a0 This message is also notable in that it contains the number of leap seconds then in effect.\u00a0 Not many NTRIP devices send this message.<\/td>\n<\/tr>\n
1014<\/span> <\/strong><\/td>\nNetwork Auxiliary Station Data<\/a>
\n<\/strong>Contains a summary of the number of stations that are part of a Network RTK system, along with the relative location of the auxiliary reference stations from the master station.<\/td>\n<\/tr>\n
1015<\/span> <\/strong><\/td>\nGPS Ionospheric Correction Differences<\/a>
\n<\/strong>Contains a short message with ionospheric carrier phase correction information for a single auxiliary reference station for the GPS GNSS type.\u00a0 See also message 1017.<\/td>\n<\/tr>\n
1016<\/span> <\/strong><\/td>\nGPS Geometric Correction Differences<\/a>
\n<\/strong>Contains a short message with geometric carrier phase correction information for a single auxiliary reference station for the GPS GNSS type.\u00a0 See also message 1017.<\/td>\n<\/tr>\n
1017<\/span> <\/strong><\/td>\nGPS Combined Geometric and Ionospheric Correction Differences<\/a>
\n<\/strong>Contains a short message with both ionospheric and geometric carrier phase correction information for a single auxiliary reference station for the GPS GNSS type.\u00a0 See also messages 1015 and 1016.<\/td>\n<\/tr>\n
1018<\/span> <\/strong><\/td>\nRESERVED<\/strong> for Alternative Ionospheric Correction Difference Message<\/a>
\nThis message has not been developed or released by SC-104 at this time.<\/td>\n<\/tr>\n
1019<\/span> <\/strong><\/td>\nGPS Ephemerides<\/a>
\n<\/strong>Sets of these messages (one per SV) are used to send the broadcast orbits for GPS in a Kepler format.<\/td>\n<\/tr>\n
1020<\/span> <\/strong><\/td>\nGLONASS Ephemerides<\/a>
\n<\/strong>Sets of these messages (one per SV) are used to send the broadcast orbits for GLONASS in a XYZ dot product format.<\/td>\n<\/tr>\n
1021<\/span> <\/strong><\/td>\nHelmert \/ Abridged Molodenski Transformation Parameters<\/a>
\n<\/strong>A classical Helmert 7-parameter coordinate transformation message.\u00a0 Not often found in actual use.<\/td>\n<\/tr>\n
1022<\/span> <\/strong><\/td>\nMolodenski-Badekas Transformation Parameters<\/a>
\n<\/strong>A coordinate transformation message using the Molodenski-Badekas method (translates through an arbitrary point rather than the origin)\u00a0\u00a0 Not often found in actual use.<\/td>\n<\/tr>\n
1023<\/span> <\/strong><\/td>\nResiduals, Ellipsoidal Grid Representation<\/a>
\n<\/strong>A coordinate transformation message.\u00a0 Not often found in actual use.<\/td>\n<\/tr>\n
1024<\/span> <\/strong><\/td>\nResiduals, Plane Grid Representation<\/a>
\n<\/strong>A coordinate transformation message.\u00a0 Not often found in actual use.<\/td>\n<\/tr>\n
1025<\/span> <\/strong><\/td>\nProjection Parameters, Projection Types other than Lambert Conic Conformal<\/a>
\n<\/strong>A coordinate projection message.\u00a0 Not often found in actual use.<\/td>\n<\/tr>\n
1026<\/span> <\/strong><\/td>\nProjection Parameters, Projection Type LCC2SP (Lambert Conic Conformal<\/a>
\n<\/strong>A coordinate projection message.\u00a0 Not often found in actual use.<\/td>\n<\/tr>\n
1027<\/span> <\/strong><\/td>\nProjection Parameters, Projection Type OM (Oblique Mercator)<\/a>
\n<\/strong>A coordinate projection message.\u00a0 Not often found in actual use.<\/td>\n<\/tr>\n
1028<\/span> <\/strong><\/td>\nReserved<\/strong> for Global to Plate-Fixed Transformation<\/a>
\nThis message has not been developed or released by SC-104 at this time.<\/td>\n<\/tr>\n
1029<\/span> <\/strong><\/td>\nUnicode Text String<\/a>
\n<\/strong>A message which provides a simple way to send short textual strings within the RTCM message set. About ~128 UTF-8 encoded characters are allowed.<\/td>\n<\/tr>\n
1030<\/span> <\/strong><\/td>\nGPS Network RTK Residual Message<\/a>
\n<\/strong>This message provides per-SV non-dispersive interpolation residual data for the SVs used in a GPS network RTK system.\u00a0 Not often found in actual use.<\/td>\n<\/tr>\n
1031<\/span> <\/strong><\/td>\nGLONASS Network RTK Residual<\/a>
\n<\/strong>This message provides per-SV non-dispersive interpolation residual data for the SVs used in a GLONASS network RTK system.\u00a0 Not often found in actual use.<\/td>\n<\/tr>\n
1032<\/span> <\/strong><\/td>\nPhysical Reference Station Position<\/a>
\n<\/strong>This message provides the ECEF location of the physical antenna used.\u00a0 See message types 1005 and 1006.\u00a0 Depending on the deployment needs, 1005, 1006, and 1032 are all commonly found.<\/td>\n<\/tr>\n
1033<\/span> <\/strong><\/td>\nReceiver and Antenna Descriptors<\/a>
\n<\/strong>A message which provides short textual strings about the GNSS device and the Antenna device.\u00a0 These strings can be used to obtain additional phase bias calibration information. This message is often sent along with either MT1007 or MT1008.<\/td>\n<\/tr>\n
1034<\/span> <\/strong><\/td>\nGPS Network FKP Gradient<\/a>
\n<\/strong>A message which provides Network RTK Area Correction Parameters using a method of localized horizontal gradients for the GPS GNSS system.<\/td>\n<\/tr>\n
1035<\/span> <\/strong><\/td>\nGLONASS Network FKP Gradient<\/a>
\n<\/strong>A message which provides Network RTK Area Correction Parameters using a method of localized horizontal gradients for the GLONASS GNSS system.<\/td>\n<\/tr>\n
1036<\/strong><\/span><\/td>\nNot defined at this time<\/a>
\n<\/strong>This message has not been developed or released by SC-104 at this time.<\/td>\n<\/tr>\n
1037<\/span> <\/strong><\/td>\nGLONASS Ionospheric Correction Differences<\/a>
\n<\/strong>Contains a short message with ionospheric carrier phase correction information for a single auxiliary reference station for the GLONASS GNSS type.\u00a0 See also message 1039.<\/td>\n<\/tr>\n
1038<\/span> <\/strong><\/td>\nGLONASS Geometric Correction Differences<\/a>
\n<\/strong>Contains a short message with geometric carrier phase correction information for a single auxiliary reference station for the GLONASS GNSS type.\u00a0 See also message 1039.<\/td>\n<\/tr>\n
1039<\/span> <\/strong><\/td>\nGLONASS Combined Geometric and Ionospheric Correction Differences<\/a>
\n<\/strong>Contains a short message with both ionospheric and geometric carrier phase correction information for a single auxiliary reference station for the GLONASS GNSS type.\u00a0 See also messages 1037 and 1037.<\/td>\n<\/tr>\n
1042<\/span> <\/strong><\/td>\nBDS Satellite Ephemeris Data<\/a>
\n<\/strong>Sets of these messages (one per SV) are used to send the broadcast orbits for the BeiDou (Compass) system.<\/td>\n<\/tr>\n
1043<\/strong><\/span><\/td>\nNot defined<\/strong> at this time<\/a>
\nThis message has not been developed or released by SC-104 at this time.<\/td>\n<\/tr>\n
1044<\/span> <\/strong><\/td>\nQZSS Ephemerides<\/a>
\n<\/strong>Sets of these messages (one per SV) are used to send the broadcast orbits for QZSS in a Kepler format.<\/td>\n<\/tr>\n
1045<\/span> <\/strong><\/td>\nGalileo F\/NAV Satellite Ephemeris Data<\/a>
\n<\/strong>Sets of these messages (one per SV) are used to send the Galileo F\/NAV orbital data.<\/td>\n<\/tr>\n
1046<\/span> <\/strong><\/td>\nGalileo I\/NAV Satellite Ephemeris Data<\/a>
\n<\/strong>Sets of these messages (one per SV) are used to send the Galileo I\/NAV orbital data.<\/td>\n<\/tr>\n
1057<\/span> <\/strong><\/td>\nSSR GPS Orbit Correction<\/a>
\n<\/strong>A state space representation message which provides per-SV data.\u00a0 It contains orbital error \/ deviation from the current broadcast information for GPS GNSS types.<\/td>\n<\/tr>\n
1058<\/span> <\/strong><\/td>\nSSR GPS Clock Correction<\/a>
\n<\/strong>A state space representation message which provides per-SV data.\u00a0 It contains SV clock error \/ deviation from the current broadcast information for GPS GNSS types.<\/td>\n<\/tr>\n
1059<\/span> <\/strong><\/td>\nSSR GPS Code Bias<\/a>
\n<\/strong>A state space representation message which provides per-SV data.\u00a0 It contains code bias errors for GPS GNSS types.<\/td>\n<\/tr>\n
1060<\/span> <\/strong><\/td>\nSSR GPS Combined Orbit and Clock Correction<\/a>
\n<\/strong>A state space representation message which provides per-SV data.\u00a0 It contains both the orbital errors and the clock errors from the current broadcast information for GPS GNSS types. Note<\/strong> <\/em>these are given as offsets from the current broadcast data.<\/td>\n<\/tr>\n
1061<\/span> <\/strong><\/td>\nSSR GPS URA<\/a>
\n<\/strong>A state space representation message which provides per-SV data.\u00a0 It contains User Range Accuracy (URA) for GPS GNSS types.<\/td>\n<\/tr>\n
1062<\/span> <\/strong><\/td>\nSSR GPS High Rate Clock Correction<\/a>
\n<\/strong>A state space representation message which provides a higher update rate than message 1058.\u00a0 It provides more precise data on the per-SV clock error \/ deviation from the current broadcast information for GPS GNSS types.<\/td>\n<\/tr>\n
1063<\/span> <\/strong><\/td>\nSSR GLONASS Orbit Correction<\/a>
\n<\/strong>A state space representation message which provides per-SV data.\u00a0 It contains orbital error \/ deviation from the current broadcast information for GLONASS GNSS types.<\/td>\n<\/tr>\n
1064<\/span> <\/strong><\/td>\nSSR GLONASS Clock Correction<\/a>
\n<\/strong>A state space representation message which provides per-SV data.\u00a0 It contains SV clock error \/ deviation from the current broadcast information for GLONASS GNSS types.<\/td>\n<\/tr>\n
1065<\/span> <\/strong><\/td>\nSSR GLONASS Code Bias<\/a>
\n<\/strong>A state space representation message which provides per-SV data.\u00a0 It contains code bias errors for GLONASS GNSS types.<\/td>\n<\/tr>\n
1066<\/span> <\/strong><\/td>\nSSR GLONASS Combined Orbit and Clock Corrections<\/a>
\n<\/strong>A state space representation message which provides per-SV data.\u00a0 It contains both the orbital errors and the clock errors from the current broadcast information for GLONASS GNSS types.<\/td>\n<\/tr>\n
1067<\/span> <\/strong><\/td>\nSSR GLONASS URA<\/a>
\n<\/strong>A state space representation message which provides per-SV data.\u00a0 It contains User Range Accuracy (URA) data for GLONASS GNSS types.<\/td>\n<\/tr>\n
1068<\/span> <\/strong><\/td>\nSSR GLONASS High Rate Clock Correction<\/a>
\n<\/strong>A state space representation message which provides a higher update rate than message 1064.\u00a0 It provides more precise data on the per-SV clock error \/ deviation from the current broadcast information for GLONASS GNSS types.<\/td>\n<\/tr>\n
1070<\/span> <\/strong><\/td>\nReserved<\/strong> for MSM<\/a>
\nThis Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1071<\/span> <\/strong><\/td>\nGPS MSM1<\/a>
\n<\/strong>The type 1 Multiple Signal Message format for the USA\u2019s GPS system.<\/td>\n<\/tr>\n
1072<\/span> <\/strong><\/td>\nGPS MSM2<\/a>
\n<\/strong>The type 2 Multiple Signal Message format for the USA\u2019s GPS system.<\/td>\n<\/tr>\n
1073<\/span> <\/strong><\/td>\nGPS MSM3<\/a>
\n<\/strong>The type 3 Multiple Signal Message format for the USA\u2019s GPS system.<\/td>\n<\/tr>\n
1074<\/span> <\/strong><\/td>\nGPS MSM4<\/a>
\n<\/strong>The type 4 Multiple Signal Message format for the USA\u2019s GPS system. This is one of the most common messages found when MSM is being used.<\/strong><\/td>\n<\/tr>\n
1075<\/span> <\/strong><\/td>\nGPS MSM5<\/a>
\n<\/strong>The type 5 Multiple Signal Message format for the USA\u2019s GPS system.<\/td>\n<\/tr>\n
1076<\/span> <\/strong><\/td>\nGPS MSM6<\/a>
\n<\/strong>The type 6 Multiple Signal Message format for the USA\u2019s GPS system.<\/td>\n<\/tr>\n
1077<\/span> <\/strong><\/td>\nGPS MSM7<\/a>
\n<\/strong>The type 7 Multiple Signal Message format for the USA\u2019s GPS system, popular.<\/td>\n<\/tr>\n
1078<\/strong><\/span><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1079<\/strong><\/span><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1080<\/strong><\/span><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1081<\/span> <\/strong><\/td>\nGLONASS MSM1<\/a>
\n<\/strong>The type 1 Multiple Signal Message format for the Russian GLONASS system.<\/td>\n<\/tr>\n
1082 <\/strong><\/span><\/td>\nGLONASS MSM2<\/a>
\n<\/strong>The type 2 Multiple Signal Message format for the Russian GLONASS system.<\/td>\n<\/tr>\n
1083<\/span> <\/strong><\/td>\nGLONASS MSM3<\/a>
\n<\/strong>The type 3 Multiple Signal Message format for the Russian GLONASS system.<\/td>\n<\/tr>\n
1084<\/span> <\/strong><\/td>\nGLONASS MSM4<\/a>
\n<\/strong>The type 4 Multiple Signal Message format for the Russian GLONASS system.<\/td>\n<\/tr>\n
1085<\/span> <\/strong><\/td>\nGLONASS MSM5<\/a>
\n<\/strong>The type 5 Multiple Signal Message format for the Russian GLONASS system.<\/td>\n<\/tr>\n
1086<\/span> <\/strong><\/td>\nGLONASS MSM6<\/a>
\n<\/strong>The type 6 Multiple Signal Message format for the Russian GLONASS system.<\/td>\n<\/tr>\n
1087<\/span> <\/strong><\/td>\nGLONASS MSM7<\/a>
\n<\/strong>The type 7 Multiple Signal Message format for the Russian GLONASS system.<\/td>\n<\/tr>\n
1088<\/span> <\/strong><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1089<\/span> <\/strong><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1090<\/span> <\/strong><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1091<\/span> <\/strong><\/td>\nGalileo MSM1<\/a>
\n<\/strong>The type 1 Multiple Signal Message format for Europe\u2019s Galileo system.<\/td>\n<\/tr>\n
1092<\/span> <\/strong><\/td>\nGalileo MSM2<\/a>
\n<\/strong>The type 2 Multiple Signal Message format for Europe\u2019s Galileo system.<\/td>\n<\/tr>\n
1093<\/span> <\/strong><\/td>\nGalileo MSM3<\/a>
\n<\/strong>The type 3 Multiple Signal Message format for Europe\u2019s Galileo system.<\/td>\n<\/tr>\n
1094<\/span> <\/strong><\/td>\nGalileo MSM4<\/a>
\n<\/strong>The type 4 Multiple Signal Message format for Europe\u2019s Galileo system.<\/td>\n<\/tr>\n
1095<\/span> <\/strong><\/td>\nGalileo MSM5<\/a>
\n<\/strong>The type 5 Multiple Signal Message format for Europe\u2019s Galileo system.<\/td>\n<\/tr>\n
1096<\/span> <\/strong><\/td>\nGalileo MSM6<\/a>
\n<\/strong>The type 6 Multiple Signal Message format for Europe\u2019s Galileo system.<\/td>\n<\/tr>\n
1097<\/span> <\/strong><\/td>\nGalileo MSM7<\/a>
\n<\/strong>The type 7 Multiple Signal Message format for Europe\u2019s Galileo system.<\/td>\n<\/tr>\n
1098<\/span> <\/strong><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1099<\/span> <\/strong><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1100<\/span> <\/strong><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1101<\/span> <\/strong><\/td>\nSBAS MSM1<\/a>
\n<\/strong>The type 1 Multiple Signal Message format for SBAS\/WAAS systems.<\/td>\n<\/tr>\n
1102<\/span> <\/strong><\/td>\nSBAS MSM2<\/a>
\n<\/strong>The type 2 Multiple Signal Message format for SBAS\/WAAS systems.<\/td>\n<\/tr>\n
1103 <\/strong><\/span><\/td>\nSBAS MSM3<\/a>
\n<\/strong>The type 3 Multiple Signal Message format for SBAS\/WAAS systems.<\/td>\n<\/tr>\n
1104<\/span> <\/strong><\/td>\nSBAS MSM4<\/a>
\n<\/strong>The type 4 Multiple Signal Message format for SBAS\/WAAS systems.<\/td>\n<\/tr>\n
1105<\/span> <\/strong><\/td>\nSBAS MSM5<\/a>
\n<\/strong>The type 5 Multiple Signal Message format for SBAS\/WAAS systems.<\/td>\n<\/tr>\n
1106<\/span> <\/strong><\/td>\nSBAS MSM6<\/a>
\n<\/strong>The type 6 Multiple Signal Message format for SBAS\/WAAS systems.<\/td>\n<\/tr>\n
1107<\/span> <\/strong><\/td>\nSBAS MSM7<\/a>
\n<\/strong>The type 7 Multiple Signal Message format for SBAS\/WAAS systems.<\/td>\n<\/tr>\n
1108<\/span> <\/strong><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1109<\/span> <\/strong><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1110<\/span> <\/strong><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1111<\/span> <\/strong><\/td>\nQZSS MSM1<\/a>
\n<\/strong>The type 1 Multiple Signal Message format for Japan\u2019s QZSS system.<\/td>\n<\/tr>\n
1112<\/span> <\/strong><\/td>\nQZSS MSM2<\/a>
\n<\/strong>The type 2 Multiple Signal Message format for Japan\u2019s QZSS system.<\/td>\n<\/tr>\n
1113<\/span> <\/strong><\/td>\nQZSS MSM3<\/strong><\/a>
\nThe type 3 Multiple Signal Message format for Japan\u2019s QZSS system.<\/td>\n<\/tr>\n
1114<\/span> <\/strong><\/td>\nQZSS MSM4<\/a>
\n<\/strong>The type 4 Multiple Signal Message format for Japan\u2019s QZSS system.<\/td>\n<\/tr>\n
1115<\/span> <\/strong><\/td>\nQZSS MSM5<\/a>
\n<\/strong>The type 5 Multiple Signal Message format for Japan\u2019s QZSS system.<\/td>\n<\/tr>\n
1116<\/span> <\/strong><\/td>\nQZSS MSM6<\/a>
\n<\/strong>The type 6 Multiple Signal Message format for Japan\u2019s QZSS system.<\/td>\n<\/tr>\n
1117<\/span> <\/strong><\/td>\nQZSS MSM7<\/a>
\n<\/strong>The type 7 Multiple Signal Message format for Japan\u2019s QZSS system.<\/td>\n<\/tr>\n
1118<\/span> <\/strong><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1119 <\/strong><\/span><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1120<\/span> <\/strong><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1121<\/span> <\/strong><\/td>\nBeiDou MSM1<\/a>
\n<\/strong>The type 1 Multiple Signal Message format for China\u2019s BeiDou system.<\/td>\n<\/tr>\n
1122<\/span> <\/strong><\/td>\nBeiDou MSM2<\/a>
\n<\/strong>The type 2 Multiple Signal Message format for China\u2019s BeiDou system.<\/td>\n<\/tr>\n
1123<\/span> <\/strong><\/td>\nBeiDou MSM3<\/a>
\n<\/strong>The type 3 Multiple Signal Message format for China\u2019s BeiDou system.<\/td>\n<\/tr>\n
1124<\/span> <\/strong><\/td>\nBeiDou MSM4<\/a>
\n<\/strong>The type 4 Multiple Signal Message format for China\u2019s BeiDou system.<\/td>\n<\/tr>\n
1125<\/span> <\/strong><\/td>\nBeiDou MSM5<\/a>
\n<\/strong>The type 5 Multiple Signal Message format for China\u2019s BeiDou system.<\/td>\n<\/tr>\n
1126<\/span> <\/strong><\/td>\nBeiDou MSM6<\/a>
\n<\/strong>The type 6 Multiple Signal Message format for China\u2019s BeiDou system.<\/td>\n<\/tr>\n
1127<\/span> <\/strong><\/td>\nBeiDou MSM7<\/a>
\n<\/strong>The type 7 Multiple Signal Message format for China\u2019s BeiDou system.<\/td>\n<\/tr>\n
1128<\/span> <\/strong><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1129 <\/strong><\/span><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1130<\/span> <\/strong><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1131<\/span> <\/strong><\/td>\nNavIC\/IRNSS MSM1
\n<\/strong>The type 1 Multiple Signal Message format for the Indian Regional Navigation Satellite System (NavIC\/IRNSS).<\/td>\n<\/tr>\n
1132<\/span> <\/strong><\/td>\nNavIC\/IRNSS MSM2
\n<\/strong>The type 2 Multiple Signal Message format for the Indian Regional Navigation Satellite System (NavIC\/IRNSS).<\/td>\n<\/tr>\n
1133<\/span> <\/strong><\/td>\nNavIC\/IRNSS MSM3
\n<\/strong>The type 3 Multiple Signal Message format for the Indian Regional Navigation Satellite System (NavIC\/IRNSS).<\/td>\n<\/tr>\n
1134<\/span> <\/strong><\/td>\nNavIC\/IRNSS MSM4
\n<\/strong>The type 4 Multiple Signal Message format for China\u2019s BeiDou system.<\/td>\n<\/tr>\n
1135<\/span> <\/strong><\/td>\nNavIC\/IRNSS MSM5
\n<\/strong>The type 5 Multiple Signal Message format for the Indian Regional Navigation Satellite System (NavIC\/IRNSS).<\/td>\n<\/tr>\n
1136<\/span> <\/strong><\/td>\nNavIC\/IRNSS MSM6
\n<\/strong>The type 6 Multiple Signal Message format for the Indian Regional Navigation Satellite System (NavIC\/IRNSS).<\/td>\n<\/tr>\n
1137<\/span> <\/strong><\/td>\nNavIC\/IRNSS MSM7
\n<\/strong>The type 7 Multiple Signal Message format for the Indian Regional Navigation Satellite System (NavIC\/IRNSS).<\/td>\n<\/tr>\n
1138<\/span> <\/strong><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1139 <\/strong><\/span><\/td>\nReserved MSM<\/a>
\n<\/strong>This Multiple Signal Message type has not yet been assigned for use.<\/td>\n<\/tr>\n
1140-1229 <\/strong><\/span><\/td>\nReserved MSM<\/a>
\n<\/strong>This range of Multiple Signal Message types has not yet been assigned for use.<\/td>\n<\/tr>\n
1230<\/span> <\/strong><\/td>\nGLONASS L1 and L2 Code-Phase Biases<\/a>
\n<\/strong>This message provides corrections for the inter-frequency bias caused by the different FDMA frequencies (k<\/em>, from -7 to 6) used.
\n<\/strong><\/td>\n<\/tr>\n
1300<\/span> <\/strong><\/td>\nService-CRS<\/a>
\n<\/strong>The formal name of the Coordinate Reference System (CRS) in use for this data stream (service) and details needed to link it to any coordinate transformation messages, typically static.<\/td>\n<\/tr>\n
1301<\/span> <\/strong><\/td>\nThe 15 Parameter Transformation<\/a>
\n<\/strong>A set of time dependent parameters used to perform a Helmert transformation between two named regional or local plate-fixed reference frames.
\n<\/strong><\/td>\n<\/tr>\n
1302<\/span> <\/strong><\/td>\nRTCM-CRS<\/a>
\n<\/strong>A message used to provide (sets of) links to external databases with information about Coordinate Reference System (CRS).
\n<\/strong><\/td>\n<\/tr>\n
1303<\/span> <\/strong><\/td>\nBDS Network RTK Residual Message<\/a>
\n<\/strong>This message provides per-SV non-dispersive interpolation residual data for the SVs used in a BDS network RTK system.\u00a0 Not often found in actual use.
\n<\/strong><\/td>\n<\/tr>\n
1304<\/span> <\/strong><\/td>\nGalileo Network RTK Residual Message<\/a>
\n<\/strong>This message provides per-SV non-dispersive interpolation residual data for the SVs used in a Galileo network RTK system.\u00a0 Not often found in actual use.
\n<\/strong><\/td>\n<\/tr>\n
4001-4095\u00a0 <\/strong><\/span><\/td>\nProprietary Messages <\/strong><\/td>\n<\/tr>\n
4095<\/span> <\/strong><\/td>\nAssigned to: Ashtech<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4094<\/span> <\/strong><\/td>\nAssigned to: Trimble Navigation Ltd.<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4093<\/span> <\/strong><\/td>\nAssigned to: NovAtel Inc.<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4092<\/span> <\/strong><\/td>\nAssigned to: Leica Geosystems <\/a><\/strong>
\nThe content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4091<\/span> <\/strong><\/td>\nAssigned to: Topcon Positioning Systems<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4090<\/span> <\/strong><\/td>\nAssigned to: Geo++<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4089<\/span> <\/strong><\/td>\nAssigned to: Septentrio Satellite Navigation<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4088<\/span> <\/strong><\/td>\nAssigned to: IfEN GmbH<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4087<\/span> <\/strong><\/td>\nAssigned to:\u00a0 Fugro<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4086 <\/strong><\/span><\/td>\nAssigned to: inPosition GmbH<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4085<\/span> <\/strong><\/td>\nAssigned to: European GNSS Supervisory Authority<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4084 <\/strong><\/span><\/td>\nAssigned to: Geodetics, Inc. <\/a><\/strong>
\nThe content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4083<\/span> <\/strong><\/td>\nAssigned to: German Aerospace Center, (DLR)<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4082 <\/strong><\/span><\/td>\nAssigned to: Cooperative Research Centre for Spatial Information<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4081 <\/strong><\/span><\/td>\nAssigned to: Seoul National University GNSS Lab<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4080<\/span> <\/strong><\/td>\nAssigned to: NavCom Technology, Inc.<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4079<\/strong><\/span><\/td>\nAssigned to: SubCarrier Systems Corp. (SCSC<\/a>)<\/a>
\n<\/strong> The makers of the SNIP<\/span> NTRIP Caster
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4078<\/strong><\/span><\/td>\nAssigned to: ComNav Technology Ltd.<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4077<\/strong><\/span><\/td>\nAssigned to: Hemisphere GNSS Inc.<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4076<\/strong><\/span><\/td>\nAssigned to: International GNSS Service (IGS)<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4075<\/strong><\/span><\/td>\nAssigned to: Alberding GmbH<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4074<\/strong><\/span><\/td>\nAssigned to: Unicore Communications Inc.<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4073<\/strong><\/span><\/td>\nAssigned to: Mitsubishi Electric Corp.<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4072<\/strong><\/span><\/td>\nAssigned to: u-blox AG<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4071<\/strong><\/span><\/td>\nAssigned to: Wuhan Navigation and LBS<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4070<\/strong><\/span><\/td>\nAssigned to: Wuhan MengXin Technology<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4069<\/strong><\/span><\/td>\nAssigned to: VERIPOS Ltd<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4068<\/strong><\/span><\/td>\nAssigned to: Qianxun Location Networks Co. Ltd<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4067<\/strong><\/span><\/td>\nAssigned to: China Transport telecommunications & Information Center<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4066<\/strong><\/span><\/td>\nAssigned to: Lantmateriet<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4065<\/strong><\/span><\/td>\nAssigned to: Allystar Technology (Shenzhen) Co. Ltd.<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4064<\/strong><\/span><\/td>\nAssigned to: NTLab<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4063<\/strong><\/span><\/td>\nAssigned to: CHC Navigation (CHCNAV)<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4062<\/strong><\/span><\/td>\nAssigned to: SwiftNav Inc.<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4061<\/strong><\/span><\/td>\nAssigned to: Zhejiang GeeSpace Technology Co.,
\nLtd.<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4060<\/strong><\/span><\/td>\nAssigned to: ALES Corp.<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4059<\/strong><\/span><\/td>\nAssigned to: Natural Resources Canada<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4058<\/strong><\/span><\/td>\nAssigned to: Anello Photonics<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4057<\/strong><\/span><\/td>\nAssigned to: Sixents Technology<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4056<\/strong><\/span><\/td>\nAssigned to: China Dayou Positioning Intelligence<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4055<\/strong><\/span><\/td>\nAssigned to: Korea Research Institute of Ships &
\nOcean engineering (KRISO)<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4054<\/strong><\/span><\/td>\nAssigned to: GEODNET <\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4053<\/strong><\/span><\/td>\nAssigned to: Qualcomm Technologies, Inc. <\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4052<\/strong><\/span><\/td>\nAssigned to: Furuno Electric Co., LTD.<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4051<\/strong><\/span><\/td>\nAssigned to: Hi-Target<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4050<\/strong><\/span><\/td>\nAssigned to: STMicroelectronics SRL<\/a>
\n<\/strong>The content and format of this message is defined by its owner.<\/td>\n<\/tr>\n
4049…<\/strong><\/span><\/td>\nMessage Types 4049 — 4001 Are Reserved
\n<\/strong>They are not assigned at this time (May 27, 2020).<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

See Also<\/h3>\n

These related message sets may also be of interest to you.<\/p>\n

A cheat sheet of common RTCM 3 Messages<\/strong><\/a><\/p>\n

A complete list of all adopted RTCM 2 Messages<\/strong><\/a> with commentary.<\/p>\n

A complete list of all adopted SAE DSRC J2735 Messages<\/strong><\/a> with commentary.<\/p>\n

Common NMEA-183 messages<\/a> of interest to GNSS NTRIP users Site-1<\/a> and Site-2<\/a><\/p>\n

The only way to truly understand the details of the RTCM 3 message set is to purchase a copy for yourself from RTCM<\/a>, please do so if you have interest.\u00a0 Here is the web page <\/a>with the standards you would need to do RTK or DGPS work.<\/p>\n

 <\/p>\n

\n

SNIP<\/strong> <\/span>is a robust NTRIP Caster<\/strong><\/a>, but it also has several built-in utilities useful for message decoding<\/p>\n

Need to see the internal contents of these messages?\u00a0 Use SNIP<\/strong><\/span>‘s RTCM3 Decoder<\/a> feature.<\/p>\n

Need to use these messages in a navigation solution?\u00a0 Use SNIP<\/strong><\/span>‘s Graphical Display<\/a> feature<\/p>\n

Need to quickly plot the ECEF<\/a> location of a base station?\u00a0 Use SNIP<\/strong><\/span>‘s Mapping<\/a> feature.<\/p>\n

Need to change the contents or format of these messages? Uses SNIP’<\/strong><\/span>s PFAT<\/strong><\/em><\/span>\u00ae<\/a> features to do so.<\/p>\n

Download your own copy of SNIP today<\/strong><\/a>, good for the Caster, good for msg decoders<\/p>\n

\n

<\/h4>\n

Note:<\/strong><\/span><\/h4>\n

Please do not copy the text of this article<\/strong>, or any other on this site, and place it on your own web page or product support guidelines passing it off as your firm’s own work.\u00a0 Like all materials found here, its copyright is held by SubCarrier Systems Corporation (SCSC).\u00a0 If you are a commercial concern, we may allow you to use it with suitable attribution (please contact us).\u00a0 It better to simply link to it.\u00a0 If your professor told you to come here and use this page as a reference for your paper (or you found it on your own); that is considered educational fair use.\u00a0 Don’t worry, just please cite the page source and\/or mention the SNIP<\/strong><\/span> NTRIP Caster. \u00a0 In all cases, the best solution includes buying a copy of the actual source standards from RTCM<\/a> to help defray the costs of further development.<\/strong><\/p>\n

\n","protected":false},"excerpt":{"rendered":"

A complete list of all adopted RTCM 3 Messages with brief commentary. The official release of the standard at this time is called: RTCM 10403.4, Differential GNSS (Global Navigation Satellite Systems) Services – Version 4\u00a0\u00a0 (published December 01, 2023) Purchase a copy from RTCM here. Comments If you are interested […]<\/p>\n","protected":false},"author":13,"comment_status":"open","ping_status":"open","template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"ht-kb-category":[341],"ht-kb-tag":[293,294,204],"class_list":["post-3592","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-message-decoding","ht_kb_tag-decoding","ht_kb_tag-message-types","ht_kb_tag-rtcm3"],"yoast_head":"\nRTCM 3 Message List - SNIP Support<\/title>\n<meta name=\"description\" content=\"A terse summary of all the RTCM 3 message types.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.use-snip.com\/kb\/knowledge-base\/rtcm-3-message-list\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"RTCM 3 Message List\" \/>\n<meta property=\"og:description\" content=\"A terse summary of all the RTCM 3 message types.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.use-snip.com\/kb\/knowledge-base\/rtcm-3-message-list\/\" \/>\n<meta property=\"og:site_name\" content=\"SNIP Support\" \/>\n<meta property=\"article:modified_time\" content=\"2024-02-17T17:22:52+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"20 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/knowledge-base\\\/rtcm-3-message-list\\\/\",\"url\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/knowledge-base\\\/rtcm-3-message-list\\\/\",\"name\":\"RTCM 3 Message List - SNIP Support\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/#website\"},\"datePublished\":\"2023-12-07T01:00:38+00:00\",\"dateModified\":\"2024-02-17T17:22:52+00:00\",\"description\":\"A terse summary of all the RTCM 3 message types.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/knowledge-base\\\/rtcm-3-message-list\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/knowledge-base\\\/rtcm-3-message-list\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/knowledge-base\\\/rtcm-3-message-list\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"RTCM 3 Message List\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/#website\",\"url\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/\",\"name\":\"SNIP NTRIP Caster Support\",\"description\":\"SNIP NTRIP Caster Support\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/#organization\",\"name\":\"SNIP Support\",\"alternateName\":\"NTRIP Caster\",\"url\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/wp-content\\\/uploads\\\/2016\\\/08\\\/SNIPwStreamUsers.png\",\"contentUrl\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/wp-content\\\/uploads\\\/2016\\\/08\\\/SNIPwStreamUsers.png\",\"width\":1132,\"height\":723,\"caption\":\"SNIP Support\"},\"image\":{\"@id\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/#\\\/schema\\\/logo\\\/image\\\/\"}}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"RTCM 3 Message List - SNIP Support","description":"A terse summary of all the RTCM 3 message types.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/rtcm-3-message-list\/","og_locale":"en_US","og_type":"article","og_title":"RTCM 3 Message List","og_description":"A terse summary of all the RTCM 3 message types.","og_url":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/rtcm-3-message-list\/","og_site_name":"SNIP Support","article_modified_time":"2024-02-17T17:22:52+00:00","twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"20 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/rtcm-3-message-list\/","url":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/rtcm-3-message-list\/","name":"RTCM 3 Message List - SNIP Support","isPartOf":{"@id":"https:\/\/www.use-snip.com\/kb\/#website"},"datePublished":"2023-12-07T01:00:38+00:00","dateModified":"2024-02-17T17:22:52+00:00","description":"A terse summary of all the RTCM 3 message types.","breadcrumb":{"@id":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/rtcm-3-message-list\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.use-snip.com\/kb\/knowledge-base\/rtcm-3-message-list\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/rtcm-3-message-list\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.use-snip.com\/kb\/"},{"@type":"ListItem","position":2,"name":"RTCM 3 Message List"}]},{"@type":"WebSite","@id":"https:\/\/www.use-snip.com\/kb\/#website","url":"https:\/\/www.use-snip.com\/kb\/","name":"SNIP NTRIP Caster Support","description":"SNIP NTRIP Caster Support","publisher":{"@id":"https:\/\/www.use-snip.com\/kb\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.use-snip.com\/kb\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.use-snip.com\/kb\/#organization","name":"SNIP Support","alternateName":"NTRIP Caster","url":"https:\/\/www.use-snip.com\/kb\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.use-snip.com\/kb\/#\/schema\/logo\/image\/","url":"https:\/\/www.use-snip.com\/kb\/wp-content\/uploads\/2016\/08\/SNIPwStreamUsers.png","contentUrl":"https:\/\/www.use-snip.com\/kb\/wp-content\/uploads\/2016\/08\/SNIPwStreamUsers.png","width":1132,"height":723,"caption":"SNIP Support"},"image":{"@id":"https:\/\/www.use-snip.com\/kb\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/3592","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/comments?post=3592"}],"version-history":[{"count":66,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/3592\/revisions"}],"predecessor-version":[{"id":8995,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/3592\/revisions\/8995"}],"wp:attachment":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/media?parent=3592"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb-category?post=3592"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb-tag?post=3592"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}