实例介绍
【实例简介】
全新RTCM3.3协议完整版 RTCM STANDARD 10403.3 DIFFERENTIAL GNSS (GLOBAL NAVIGATION SATELLITE SYSTEMS) SERVICES – VERSION 3 DEVELOPED BY RTCM SPECIAL COMMITTEE NO. 104 OCTOBER 7, 2016 COPYRIGHT©2016 RTCM Radio Technical Commission for Maritime Services 1611 N. Kent St., Suite 605 Arlington, Virginia 22209-214
RTCM Paper 141-2016-SC104-STD 000oc RTCM co00c30 RTCM 10403. 3, Differential GNSS Global Navigation Satellite Systems) Services- Version 3, October 7, 2016 This standard (referred to as version 3 has been developed by rtCm special Committee 104 as a more efficient alternative to the standards entitled rtcm recommended standards for diffe rential Recommended Standards for Differential gNss Global Navigation Satellite Systems Service, Version 2.x (Current version is 2. 3, now designated as RTCM 10402. 3. Service providers and vendors represented on the SC104 Committee wanted a new standard that would be more efficient, easy to use, and more easily adaptable to new situations. The main complaint was that the version 2. x parity scheme, which uses words with 24 bits of data followed by 6 bits of parity, was wasteful of bandwidth. Another complaint was that the parity was not independent from word to word. Still another was that even with so many bits devoted to parity the actual integrity of the message was not as high as it should be. Plus, 30-bit words are awkward to handle. the new standard version 3 is intended to correct these weaknesses Unlike Version 2. x, this standard does not include tentative messages The messages in Version 3 have undergone testing for validity and interoperability and are considered to be permanent. amendments to the standard may change the meaning of reserved bits or provide additional clarifying text, but no changes will be made in the data fields. Changes will require new messages to be developed. In addition to the messages described in the current standard the committee continues to develop new messages which are described in separately published amendments and periodically gathered into a new edition of the standard. RTCM 10403x for dgNSS services is proving useful in supporting highly accurate differential and kinematic positioning as well as a wide range of navigation applications worldwide Note that Version 3 messages are not compatible with Version 2. x. Since many receivers have been designed and programmed for use with Version 2. x messages, rtCm is maintaining both standards 0402 3 and 10403, 3 as" standards Version 3.0 The initial edition consisted primarily of messages designed to support real-time kinematic (RTK) operations. The reason for this emphasis is that rtk operation involves broadcasting a lot of information and thus benefits the most from an efficient data format. Version 3.0 provided messages that support GPS and gloNaSs rTK operations including code and carrier phase observables antenna parameters and ancillary system parameters Version 3. 1(RTCM Standard 10403.1: The next edition, Version 3. 1 (RTCM Standard 10403. 1), incorporated GPS Network Corrections, which enable a mobile receiver to obtain accurate rtk information valid over a large area. In addition, new GPS and GLoNaSS messages provide orbital parameters to assist in rapid acquisition a Unicode text message is also provided for the transmission of textual data. Finally a set of messages are reserved for vendors who want to encapsulate proprietary data in their broadcasts the gps Network Corrections enable a mobile receiver to obtain accurate rtk information valid over a large area. the network rtk correction information provided to a rover can be considered as interpolated corrections between the reference stations in the rtk network this interpolation is not perfect and varies with the actual conditions of the atmosphere. A residual interpolation error has to be expected. With sufficient redundancy in the RtK network, the network server process can provide an estimate for residual interpolation errors. Such quality estimates may be used by the rover to optimize the performance of rtk solutions The values may be considered by the rover as a priori estimates only with sufficient tracking data available the rover might be able to judge residual geometric and ionospheric errors itself Version 3. 1. Amendment 1: Amendments 1 was an extensive addition that adds rtcm messages containing transformation data and information about Coordinate reference Systems. For rtCm data supporting a rtk service, coordinates are measured within the itrf or a regional realization surve yors and other users of rtk services must normally present their results in the coordinates of local datums. Therefore, coordinate transformations are necessary. by having RTCM messages that contain transformation data and information about the Coordinate reference systems the users of the rtk service can obtain their results in the desired datum without any manual operations. the rtk service providers can then ensure that current information for the computation of the transformations is always used. the convenience of this method will promote the acceptance of rtK services Version 3. 1. amendment 2: Amendment 2 added residual error messages to support the use of Non-Physical or Computed reference Stations in a network rtk environment Version 3. 1. amendment 3: Amendment 3 addressed differences in the way gnss receiver manufacturers have implemented carrier phase encoding of some Version 3 messages so that carrier phase observations are in phase for all carrier phases of a specific frequency i e. they correct for quarter cycle phase shifts. others retain the quarter cycle offset between the carrier phase observations in the data. this amendment documents the way different manufacturers have handled the phase shift issue and prescribes a uniform approach for future products. ∨ersiⅰon3.1, Amendment4: Amendment 4 added sections 3.5.13 on glONASS Network rtK Correction Messages and 3.5. 14 on FKP Network Rtk Correction Messages Related revisions were also made elsewhere in the document. Version 3. 1. amendment 5 Amendment 5 added section 3. 5. 12 on State Space Representation related revisions are also made elsewhere in the document, along with some editorial corrections Version 3. 2(RTCM Standard 10403.2) Version 3.2 consolidates Version 3. 1 and all five amendments into a new edition, and it adds Multiple Signal Messages (MSM)as well. the Multiple Signal Message (MSm)format generates receiver observables in the same way for all included satellite systems. the messages include compact and full messages for Pseudorange, PhaseRange, Carrier to Noise Ratio (standard and high resolution), and PhaseRangerate a table near the beginning of the standard lists which messages were included in each separate edition and amendment, so it should not be necessary for users to refer to older versions. Multiple signal Messages are a generic format that will be followed for all GNSs systems. version 3 originally consisted of messages for GPS and GLONASS, each in their own format Now with the imminent addition of signals for BeiDou, Galileo, and QZSS, as well as new signals provided by modernized GPS and GloNASS satellites the need for a consistent generic format became evident. service providers and users are urged to migrate to the MsM messages to make it easier to accommodate new gNss services (See The RTCM Multiple Signal Messages: A New Step in GNSS Data Standardization")Another new message is the gloNaSS Bias Information message. This message provides information which is intended to compensate for the first-order inter-frequency phase range biases introduced by the reference receiver code- phase bias Version 3.2, Amendment 1: Added Galileo F/NAv Satellite Ephemeris Data(msg. 1045 )and Bds MSM(msgs. 1121-1127) Version 3.2 amendment 2 Added qzss ephemeris(msg. 1044 )and QZss MSm (msgs. 1111-1117 Version 3. 3(RTCM Standard 10403.3) This new edition adds Satellite-Based Augmentation System Multiple Signal Messages to previously dopted messages for GPS, GLONASS, Galileo, and Qzss A new ephemeris message has been added for BeiDou(BDS)and a new I/NAV ephemeris message has been added for Galileo. The new edition also reserves 100 messages be used exclusively by sc104 for new message development Finally, the new edition makes consolidates previous amendments and makes numerous editorial Improvements Navstar GPS Service, Version 2. x. Service providers and vendors represented on the sc co000c30z1O2 co00c30 Contents co00c30 【实例截图】
【核心代码】
全新RTCM3.3协议完整版 RTCM STANDARD 10403.3 DIFFERENTIAL GNSS (GLOBAL NAVIGATION SATELLITE SYSTEMS) SERVICES – VERSION 3 DEVELOPED BY RTCM SPECIAL COMMITTEE NO. 104 OCTOBER 7, 2016 COPYRIGHT©2016 RTCM Radio Technical Commission for Maritime Services 1611 N. Kent St., Suite 605 Arlington, Virginia 22209-214
RTCM Paper 141-2016-SC104-STD 000oc RTCM co00c30 RTCM 10403. 3, Differential GNSS Global Navigation Satellite Systems) Services- Version 3, October 7, 2016 This standard (referred to as version 3 has been developed by rtCm special Committee 104 as a more efficient alternative to the standards entitled rtcm recommended standards for diffe rential Recommended Standards for Differential gNss Global Navigation Satellite Systems Service, Version 2.x (Current version is 2. 3, now designated as RTCM 10402. 3. Service providers and vendors represented on the SC104 Committee wanted a new standard that would be more efficient, easy to use, and more easily adaptable to new situations. The main complaint was that the version 2. x parity scheme, which uses words with 24 bits of data followed by 6 bits of parity, was wasteful of bandwidth. Another complaint was that the parity was not independent from word to word. Still another was that even with so many bits devoted to parity the actual integrity of the message was not as high as it should be. Plus, 30-bit words are awkward to handle. the new standard version 3 is intended to correct these weaknesses Unlike Version 2. x, this standard does not include tentative messages The messages in Version 3 have undergone testing for validity and interoperability and are considered to be permanent. amendments to the standard may change the meaning of reserved bits or provide additional clarifying text, but no changes will be made in the data fields. Changes will require new messages to be developed. In addition to the messages described in the current standard the committee continues to develop new messages which are described in separately published amendments and periodically gathered into a new edition of the standard. RTCM 10403x for dgNSS services is proving useful in supporting highly accurate differential and kinematic positioning as well as a wide range of navigation applications worldwide Note that Version 3 messages are not compatible with Version 2. x. Since many receivers have been designed and programmed for use with Version 2. x messages, rtCm is maintaining both standards 0402 3 and 10403, 3 as" standards Version 3.0 The initial edition consisted primarily of messages designed to support real-time kinematic (RTK) operations. The reason for this emphasis is that rtk operation involves broadcasting a lot of information and thus benefits the most from an efficient data format. Version 3.0 provided messages that support GPS and gloNaSs rTK operations including code and carrier phase observables antenna parameters and ancillary system parameters Version 3. 1(RTCM Standard 10403.1: The next edition, Version 3. 1 (RTCM Standard 10403. 1), incorporated GPS Network Corrections, which enable a mobile receiver to obtain accurate rtk information valid over a large area. In addition, new GPS and GLoNaSS messages provide orbital parameters to assist in rapid acquisition a Unicode text message is also provided for the transmission of textual data. Finally a set of messages are reserved for vendors who want to encapsulate proprietary data in their broadcasts the gps Network Corrections enable a mobile receiver to obtain accurate rtk information valid over a large area. the network rtk correction information provided to a rover can be considered as interpolated corrections between the reference stations in the rtk network this interpolation is not perfect and varies with the actual conditions of the atmosphere. A residual interpolation error has to be expected. With sufficient redundancy in the RtK network, the network server process can provide an estimate for residual interpolation errors. Such quality estimates may be used by the rover to optimize the performance of rtk solutions The values may be considered by the rover as a priori estimates only with sufficient tracking data available the rover might be able to judge residual geometric and ionospheric errors itself Version 3. 1. Amendment 1: Amendments 1 was an extensive addition that adds rtcm messages containing transformation data and information about Coordinate reference Systems. For rtCm data supporting a rtk service, coordinates are measured within the itrf or a regional realization surve yors and other users of rtk services must normally present their results in the coordinates of local datums. Therefore, coordinate transformations are necessary. by having RTCM messages that contain transformation data and information about the Coordinate reference systems the users of the rtk service can obtain their results in the desired datum without any manual operations. the rtk service providers can then ensure that current information for the computation of the transformations is always used. the convenience of this method will promote the acceptance of rtK services Version 3. 1. amendment 2: Amendment 2 added residual error messages to support the use of Non-Physical or Computed reference Stations in a network rtk environment Version 3. 1. amendment 3: Amendment 3 addressed differences in the way gnss receiver manufacturers have implemented carrier phase encoding of some Version 3 messages so that carrier phase observations are in phase for all carrier phases of a specific frequency i e. they correct for quarter cycle phase shifts. others retain the quarter cycle offset between the carrier phase observations in the data. this amendment documents the way different manufacturers have handled the phase shift issue and prescribes a uniform approach for future products. ∨ersiⅰon3.1, Amendment4: Amendment 4 added sections 3.5.13 on glONASS Network rtK Correction Messages and 3.5. 14 on FKP Network Rtk Correction Messages Related revisions were also made elsewhere in the document. Version 3. 1. amendment 5 Amendment 5 added section 3. 5. 12 on State Space Representation related revisions are also made elsewhere in the document, along with some editorial corrections Version 3. 2(RTCM Standard 10403.2) Version 3.2 consolidates Version 3. 1 and all five amendments into a new edition, and it adds Multiple Signal Messages (MSM)as well. the Multiple Signal Message (MSm)format generates receiver observables in the same way for all included satellite systems. the messages include compact and full messages for Pseudorange, PhaseRange, Carrier to Noise Ratio (standard and high resolution), and PhaseRangerate a table near the beginning of the standard lists which messages were included in each separate edition and amendment, so it should not be necessary for users to refer to older versions. Multiple signal Messages are a generic format that will be followed for all GNSs systems. version 3 originally consisted of messages for GPS and GLONASS, each in their own format Now with the imminent addition of signals for BeiDou, Galileo, and QZSS, as well as new signals provided by modernized GPS and GloNASS satellites the need for a consistent generic format became evident. service providers and users are urged to migrate to the MsM messages to make it easier to accommodate new gNss services (See The RTCM Multiple Signal Messages: A New Step in GNSS Data Standardization")Another new message is the gloNaSS Bias Information message. This message provides information which is intended to compensate for the first-order inter-frequency phase range biases introduced by the reference receiver code- phase bias Version 3.2, Amendment 1: Added Galileo F/NAv Satellite Ephemeris Data(msg. 1045 )and Bds MSM(msgs. 1121-1127) Version 3.2 amendment 2 Added qzss ephemeris(msg. 1044 )and QZss MSm (msgs. 1111-1117 Version 3. 3(RTCM Standard 10403.3) This new edition adds Satellite-Based Augmentation System Multiple Signal Messages to previously dopted messages for GPS, GLONASS, Galileo, and Qzss A new ephemeris message has been added for BeiDou(BDS)and a new I/NAV ephemeris message has been added for Galileo. The new edition also reserves 100 messages be used exclusively by sc104 for new message development Finally, the new edition makes consolidates previous amendments and makes numerous editorial Improvements Navstar GPS Service, Version 2. x. Service providers and vendors represented on the sc co000c30z1O2 co00c30 Contents co00c30 【实例截图】
【核心代码】
标签:
好例子网口号:伸出你的我的手 — 分享!
小贴士
感谢您为本站写下的评论,您的评论对其它用户来说具有重要的参考价值,所以请认真填写。
- 类似“顶”、“沙发”之类没有营养的文字,对勤劳贡献的楼主来说是令人沮丧的反馈信息。
- 相信您也不想看到一排文字/表情墙,所以请不要反馈意义不大的重复字符,也请尽量不要纯表情的回复。
- 提问之前请再仔细看一遍楼主的说明,或许是您遗漏了。
- 请勿到处挖坑绊人、招贴广告。既占空间让人厌烦,又没人会搭理,于人于己都无利。
关于好例子网
本站旨在为广大IT学习爱好者提供一个非营利性互相学习交流分享平台。本站所有资源都可以被免费获取学习研究。本站资源来自网友分享,对搜索内容的合法性不具有预见性、识别性、控制性,仅供学习研究,请务必在下载后24小时内给予删除,不得用于其他任何用途,否则后果自负。基于互联网的特殊性,平台无法对用户传输的作品、信息、内容的权属或合法性、安全性、合规性、真实性、科学性、完整权、有效性等进行实质审查;无论平台是否已进行审查,用户均应自行承担因其传输的作品、信息、内容而可能或已经产生的侵权或权属纠纷等法律责任。本站所有资源不代表本站的观点或立场,基于网友分享,根据中国法律《信息网络传播权保护条例》第二十二与二十三条之规定,若资源存在侵权或相关问题请联系本站客服人员,点此联系我们。关于更多版权及免责申明参见 版权及免责申明
网友评论
我要评论