1 / 11

Real-time Format Issues and Recommendations for GNSS Data Streaming

This presentation discusses the current issues with real-time streaming formats for GNSS data and proposes recommendations, focusing on the use of RTCM format. It explores the choices available, the case for RTCM, and provides suggestions on how to solve this issue, including becoming a member of RTCM.SC.104 and defining clear requirements. Recommendations also include using RINEX 3.0 to define RTIGS requirements and initiating a requirements definition phase for Real Time products within the RT-Pilot Project.

erachael
Download Presentation

Real-time Format Issues and Recommendations for GNSS Data Streaming

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Real-time Format IssuesMark Caissy –Natural Resources Canadapresented at theInternational GNSS Service WorkshopMiami, June 6th 2008

  2. Outline • Current issue • What are our choices • A Case for RTCM • Recommendations

  3. Current Issue • Streaming formats are required for: • Real-time data • Real-time orbits / clocks / biases / iono / topo / etc? • No streaming format available and in use today meets the essential needs of the RT-IGS community

  4. What Choices Are There? • SOC format (used in RTIGS streams) • GPS only and extending is not being considered • BINEX (GPS) format supported by RTIGS • Proposed extensions to GNSS look promising • Acceptance by manufactures is an unknown • RTCM format (used in NTRIP streams) • Covers data, orbits and clocks • Most promising from the standpoint of acceptance by manufactures • Versions 2 and 3 lack certain essential features

  5. How Are We Going To Solve This Issue • RTPP Key Activity • Investigate standards and formats for real-time data collection, data dissemination and delivery of derived products

  6. How Are We Going To Solve This Issue • Show document in preparation

  7. A Case for RTCM (1/2) • Manufactures develop their proprietary formats in order to give themselves what they perceive to be a competitive edge • likely to increase with new signals and constellations • there is evidence of a decreased willingness to disclose this information

  8. A Case for RTCM (2/2) • RTCM SC-104 is the common playing field where manufacturers discuss and make decisions on topics that are impacting the RT-IGS • Most notable are discussions and decisions that have resulted in RTCM version 2 and 3 formats • RTCM is now discussing formats for state space representation of orbit and clock corrections for use in applications including PPP

  9. How Should IGS Proceed • Define clear and definitive requirements for formats • In the areas of real-time GNSS data and correction information ( orbits, clocks, biases, etc ) • Make these requirements known to the RTCM community • We must influence the decision making process in the area of streaming GNSS data and state space correction information

  10. Recommendations • (RTPP-01) IGS – become a member of RTCM SC 104 • (RTPP-02) That RINEX 3.0 be used to define RTIGS requirements for streamed data content and observation resolution • (RTPP-03) That SP3c and Clock RINEX be used to define RTIGS requirements for streamed content and resolution for state space orbits and clocks

  11. Recommendations • (RTPP-04) Process to adopt in the development of RT product formats and protocols for the RT Pilot Project: • Both NTRIP and UDPRelay will support dissemination of the Pilot Project Real Time products • The Pilot Project Analysis and RT-Data Centre participants will initiate a requirements definition phase for formats of all Real Time products that are within the scope of the Pilot Project. The RT-Data Centre participants will also cover the perspective of the User Community. • A prototype format for orbits and clocks will be developed and hosted by the RT Data Centers. The timescale for this will be compatible with the schedule for the availability of the products (by January 2009 for individual ACs and March 2009 for the combination product). • Participants in the RT Pilot Project will take an active role in the definition of final formats to support IGS requirements for all RT products, placing emphasis on influencing the evolution of existing international standards and in particular RTCM.

More Related