HOME -> RTNet

Introduction

Template Input
    (svn 15512)

  Realtime Proc.

  Post-Processing

  NRT Processing


RTnet Output

RTes FAQ

RTnet FAQ



RTNet Software -Realtime Processing of GNSS Data-


RTES and RTNet Data Flow

RTNet system consists of two parts; RT Epoch Server (RTES) for handling realtime streaming data and RTNet processing engine.

RTES has multiple support modules to handle different type of realtime data streaming format. They handle raw data and it trasfer data to RTNet with realtime.

RTNet handles real-time data came from RTES, and also it can directly handle RINEX data file for post-processing and near real-time processing.


GUI RTnet controler

Operational processing system can be set with command line, but it's much easier to use RTNetUser for variable real-time test processing and post-processing camapign. RTNetManager runnning in the processing server control RTNet job with request from RTNetUser.

User can choose specific template input file from multiple choice.


RTNet (Real-Time Network Software)

RTNet handles real-time data came from RTES, and also it can directly handle RINEX data file for post-processing and near real-time processing.

Most of processing information from raw data to solutions is written in standard output file (OUT). The files which have tropospheric delay, ionospheric delay, satellite clock corrections, and other DGPS correction information, and binary output with solutions are also generated with setting of option parameters in RTNet input file (INP). Such information can be tranferred to other servers through specific scokets.

RTNet Software Philosophy

  • Highest accuracy model of observables (i. e. includes ocean loading, tides, absolute phase centers, latest mapping functions etc.)
  • Stay at cutting edge of new developments - i.e. development of PPP with ambiguity resolution
  • Separate filter (for real-time positions, clocks, troposphere, ionosphere) from orbit determination
  • Server mode: generating correction (PPPAR, Ionospheric model, Satellite clock)
  • Client mode: Use DGPS correction from server visa socket or file
  • Global, regional, and local processing is possible
  • Ambiguity resolution in 1,000 km baseline
  • Seamless processing with batch data (no jump in day boundaries)
  • All applications must work in real-time and post processing mode