|
1
|
- Delivery of some CORS data in near real-time via Ntrip
- OPUS-RS to process 15 minute data sets
- OPUS projects
|
|
2
|
- Process multiple files as network
- Reduce occupation time to ~ 15 min
- Process single frequency (L1) data
- Publish OPUS results
|
|
3
|
- Process multiple files as network
- Reduce occupation time to ~ 15 min
- Process single frequency (L1) data
- Publish OPUS results
|
|
4
|
- What format?
- What stations?
- What software?
- What distance?
- What data rate?
- What latency?
|
|
5
|
|
|
6
|
- Uses RSGPS program instead of PAGES
- (based on OSU MPGPS program)
- Uses P1 and P2 as well as L1 and L2 obs
- Resolves all ambiguities with LAMBDA
- Geometry free linear combination used to determine DD ionospheric
delays
|
|
7
|
|
|
8
|
- May be used in two modes :
- Network and Rover
- In network mode, only reference stations are used and to solve for
ambiguities and double difference ionospheric delays
- In rover mode, ionospheric delays and troposphere parameters are
interpolated from reference stations to rover.
|
|
9
|
- Expected to produce solution with 15 minutes of data (vs. 2 hours for
current OPUS)
- Network solution (rather than individual baselines)
- Expected accuracy approx. 2 cm horizontal and 4 cm vertical
|
|
10
|
|
|
11
|
- Interface will be almost identical to regular OPUS
- Output report will be similar to regular OPUS, but with quality
indicators based on the W-ratio from the LAMBDA validation tests
|
|
12
|
|
|
13
|
|
|
14
|
|
|
15
|
|
|
16
|
- Add project planning / monitoring
- Automated file management
- Review repeat measurements
- Network adjustment with GPSCOM
- Publish in NGS Integrated Data Base
|
|
17
|
|