|
1
|
|
|
2
|
|
|
3
|
|
|
4
|
|
|
5
|
|
|
6
|
|
|
7
|
|
|
8
|
- Estimate position for remote station
- Compute distance to every available CORS
- Sort CORS by increasing distance
- Select the 5 closest CORS
- Look at 1st 3 CORS with TEQC program. Criteria:
- ● data cover time span
for remote station
- ● > 80% of data
available
- ● low multipath
- ● if not, replace with
4th CORS (then 5th)
- 6. Start single baseline solutions using 1st 3 CORS
- ● check solution
quality
- ● if bad solution,
replace CORS with 4th (then 5th)
|
|
9
|
|
|
10
|
|
|
11
|
|
|
12
|
- Compressed archive of multiple files. Archive must contain RINEX
“site123h.04o” or Hatanaka “site123h.04d”
|
|
13
|
|
|
14
|
|
|
15
|
|
|
16
|
|
|
17
|
|
|
18
|
|
|
19
|
|
|
20
|
|
|
21
|
|
|
22
|
|
|
23
|
|
|
24
|
|
|
25
|
- “The OPUS positioning software is only available for use for datasets taken/recorded in one of
the areas determined to be valid for OPUS A solution will not be
performed on the dataset
submitted.
- The time span of the submitted dataset is too short. OPUS needs a minimum of one hours
worth of data to begin
processing.
- The dataset submitted to OPUS does not meet the RINEX standard. Please re-submit the data in RINEX
2.0 or 2.1 standard. Aborting...
- The dataset submitted to OPUS contained too many data gaps or a large
number of sampling interval changes.
Aborting...
- WARNING! No antenna type
selected. An antenna pattern will
not be applied.
- The observations to slip ratio is too low. There were an unusually high number of
cycle slips in the dataset.
Aborting...
- ERROR! Opus terminated abnormally
in one of the processing modules.
|
|
26
|
|
|
27
|
|
|
28
|
|
|
29
|
|
|
30
|
|
|
31
|
- On a typical bridge job, NCDOT
- Sets an azimuth pair (
)
- Uses approximately 6-7 control panels ( )
- Controls the site with 2 receivers
|
|
32
|
|
|
33
|
|
|
34
|
- The following steps need to be taken to finish the process:
|
|
35
|
|
|
36
|
|
|
37
|
|
|
38
|
|
|
39
|
|
|
40
|
|
|
41
|
|
|
42
|
|
|
43
|
|
|
44
|
|
|
45
|
|
|
46
|
|
|
47
|
|
|
48
|
|
|
49
|
- * Exploring the use of NTRIP to stream GPS data from selected CORS via
the Internet.
- * Developing OPUS-GIS which will process a few minutes of GPS code
range data (for sub-meter accuracy)
- * Developing OPUS-RS (rapid static) that will enable users to obtain
positional coordinates with cm-level accuracy using only 15 minutes of
GPS carrier phase data
|
|
50
|
- OPUS files identified as belonging to a project are directed to
appropriate directories
- Project data submission organized
- Reports sent to project managers
- Station data checked and edited as needed
- PAGES GPS processing accomplished
- ADJUST run
|