NTRIP & BNC para estimar Troposfera

Tamanho: px

Começar a partir da página:

Download "NTRIP & BNC para estimar Troposfera"

Letícia Almeida Maranhão
7 Há anos
Visualizações:

1 NTRIP & BNC para estimar Troposfera Galera Monico Maio de 2016

2 Comunicação para transmissão de dados GNSS É crescente o uso da comunicação via internet em aplicações GNSS. Uso da internet para transferência de dados como: IGS, RBMC e da rede São Paulo. Substituição dos links de rádio para a realização do RTK e DGPS. Receptores GNSS têm a capacidade de serem conectados diretamente à rede de computadores.

Uso da internet para transferência de dados como: IGS, RBMC e da rede São Paulo.

3 Comunicação via Internet A transmissão e as operações realizadas com dados através da Internet são baseadas na padronização através de protocolos. Os padrões de Internet em geral são desenvolvidos pela IETF (Internet Engineering Task Force Força de Trabalho de Engenharia de Internet). TCP (Transmission Control Protocol Protocolo de Controle de Transmissão). IP (Internet Protocol Protocolo de Internet). HTTP (HyperText Transfer Protocol Protocolo de Transferência de Hipertexto). SMTP (Simple Mail Transfer Protocol Protocolo de Simples Transferência de Correio).

Os padrões de Internet em geral são desenvolvidos pela IETF (Internet Engineering Task Force Força de Trabalho de Engenharia de Internet).

4 NTRIP NtripClient 1 NtripClient N Trans, HTTP NtripCaster Trans, HTTP Administrador HTTP NtripServer 1 NtripServer N Estação Base 1 Estação Base N

5 NTRIP NTRIP CLIENT SERVER

6 BKG Ntrip Client (BNC) BNC The BKG Ntrip Client (BNC) is a program for simultaneously retrieving, decoding, converting and processing real-time GNSS data streams. It has been developed within the framework of the IAG sub-commission for Europe (EUREF) and the International GNSS Service (IGS). Although meant as a real-time tool, it comes with some Post Processing functionality. You may like to use it for data coming from NTRIP Broadcasters like or

It has been developed within the framework of the IAG sub-commission for Europe (EUREF) and the International GNSS Service (IGS).

7 BNC has been written under GNU General Public License (GPL). Source code is available from Subversion software archive Binaries for BNC are available for Windows, Linux, and Mac OS X systems. It is used the MinGW Version compiler to create the Windows binaries. Please ensure that you always use the latest version of BNC available from Note that static and shared builds of BNC are made available.

Binaries for BNC are available for Windows, Linux, and Mac OS X systems. It is used the MinGW Version 4.

8 A static build would be sufficient in case you don't want BNC to trace positions using Google Map (GM) or Open StreetMap (OSM). However, GM/OSM usage requires the QtWebKit library which can only be part of BNC builds from shared libraries. Using a shared library BNC build requires that you first install your own shared Qt library. The 'README.txt' file which comes with the BNC source code describes how to install Qt on Windows, Linux and Mac systems.

However, GM/OSM usage requires the QtWebKit library which can only be part of BNC builds from shared libraries.

9 How it looks like...

10 Purpose of BNC Retrieve real-time GNSS data streams available through NTRIP transport protocol; (recupera fluxo de dados) Retrieve real-time GNSS data streams via TCP directly from an IP address without using the NTRIP transport protocol; Retrieve real-time GNSS data streams from a local UDP or serial port without using the NTRIP transport protocol; Generate RINEX Observation and Navigation files to support near real-time GNSS Post Processing applications; Generate ephemeris and synchronized or unsynchronized observations epoch by epoch through an IP port to support real-time GNSS network engines; Generate orbit and clock corrections to Broadcast Ephemeris through an IP port to support real-time Precise Point Positioning on GNSS rovers;

Observation and Navigation files to support near real-time GNSS Post Processing applications; Generate ephemeris and synchronized or unsynchronized observations epoch by epoch through an

11 Generate synchronized or unsynchronized orbit and clock corrections to Broadcast Ephemeris epoch by epoch through an IP port to support the (outside) combination of such streams as coming simultaneously from various correction providers; Monitor the performance of a network of real-time GNSS data streams to generate advisory notes in case of outages or corrupted streams; Scan RTCM streams for incoming antenna information as well as observation types and message types and their repetition rates; Feed a stream into a GNSS receiver via serial communication link; Carry out real-time Precise Point Positioning to determine a GNSS rover position; Simultaneously process several Broadcast Correction streams to produce, encode and upload combined Broadcast Corrections; Upload a Broadcast Ephemeris stream in RTCM Version 3 format;

streams for incoming antenna information as well as observation types and message types and their repetition rates; Feed a stream into a GNSS receiver via serial communication link; Carry out

12 Read GNSS orbits and clocks in a plain ASCII format from an IP port. They can be produced by a real-time GNSS engine such as RTNet and should be referenced to the IGS Earth-Centered-Earth- Fixed (ECEF) reference system. BNC will then Convert the IGS Earth-Centered-Earth-Fixed orbits and clocks into Broadcast Corrections with radial, along-track and cross-track components; Upload Broadcast Corrections as an RTCM Version 3 stream to an NTRIP Broadcaster; Refer the orbit and clock corrections to a specific reference system; Log the Broadcast Corrections as Clock RINEX files for further processing using other tools than BNC; Log the Broadcast Corrections as SP3 files for further processing using other tools than BNC; Edit or concatenate RINEX files or check their quality; Plot stream distribution map from NTRIP Broadcaster sourcetables;

BNC will then Convert the IGS Earth-Centered-Earth-Fixed orbits and clocks into Broadcast Corrections with radial, along-track and cross-track components; Upload Broadcast Corrections as an RTCM

13 Plot positions derived from RTCM streams or RINEX files on maps from Google Map or Open StreetMap. BNC supports decoding the following GNSS stream formats and message types: RTCM Version 2 message types for GPS and GLONASS observations; RTCM Version 3 'conventional' message types for observations and Broadcast Ephemeris for GPS and GLONASS; RTCM Version 3 'State Space Representation' (SSR) messages for GPS and GLONASS; RTCM Version 3 'Multiple Signal Messages' (MSM) and 'High Precision Multiple Signal Messages' (HP MSM) including X-type observations for GPS, GLONASS, Galileo, BeiDou, QZSS, and SBAS (draft); RTNET, a plain ASCII format defined within BNC to receive orbits and clocks from a serving GNSS engine.

types for observations and Broadcast Ephemeris for GPS and GLONASS; RTCM Version 3 'State Space Representation' (SSR) messages for GPS and GLONASS; RTCM Version 3 'Multiple Signal

17 Canvas.. Tela

18 ROSA, PPTE, SPJA, Estações com PTU devices Coordenadas from SIRGAS. 01/01/2005 PPTE A PPTE A

19 BNC allows using different Point Positioning processing options depending on the capability of the involved receiver and the application in mind. It also allows introducing specific sigmas for code and phase observations as well as for reference coordinates and troposphere estimates. You may also like to carry out your PPP solution in Quick-Start mode or enforce BNC to restart a solution if the length of an outage exceeds a certain threshold. Use Phase Obs - optional By default BNC applies a Point Positioning solution using an ionosphere free P3 linear combination of code observations. Tick 'Use phase obs' for an ionosphere free L3 linear combination of phase observations.

You may also like to carry out your PPP solution in Quick-Start mode or enforce BNC to restart a solution if the length of an outage exceeds a certain threshold.

20 Estimativa da Troposfera no BNC Estimate Tropo - optional BNC estimates the tropospheric delay according to equation T(z) = T_apr(z) + dt / cos(z) where T_apr is the a-priori tropospheric delay derived from Saastamoinen model. By default BNC does not estimate troposphere parameters. Tick 'Estimate tropo' to estimate troposphere parameters together with the coordinates and save T_apr and dt/cos(z) in BNC's log file.

Saastamoinen model. By default BNC does not estimate troposphere parameters.

21 Tropo Init - mandatory if 'Estimate tropo' is set Enter a sigma in meters for the a-priory model based tropospheric delay estimation. A value of 0.1 (default) may be an appropriate choice. Tropo White Noise - mandatory if 'Estimate tropo' is set Enter a sigma in meters per second to describe the expected variation of the tropospheric effect. Supposing 1Hz observation data, a value of 3e-6 (default) would mean that the tropospheric effect may vary for 3600 * 3e-6 = 0.01 meters per hour.

24 Trabalho prático Instalar o BNC e baixar dados de uma ou mais estação GNSS porta 2101 User: teste01 Passwd: umteste Realizar PPP (em tempo real e/ou pos procesado) BNC ou outro software que permita obter ZTD Analisar a qualidade dos dados Obter uma série de valores de atraso zenital troposférico Com o arquivo de dados meteorológicos, converter o atraso para IWV. Ver a possibilidade de correlacionar IWV com precipitação. Estações com dados Meteorológicos: ROSA, ILHA, SPFR, PPTE, UBA1, OURI, SPBO

Documentos relacionados

PPP PÓS PROCESSADO E EM TEMPO REAL. Prof. Dr. Haroldo Antonio Marques - UFPE Prof. Dr. João Francisco Galera Monico - UNESP

PPP PÓS PROCESSADO E EM TEMPO REAL Prof. Dr. Haroldo Antonio Marques - UFPE Prof. Dr. João Francisco Galera Monico - UNESP Introdução Posicionamento GNSS em tempo real (ex.: RTK e DGPS): RTPPP (Real Time