Static Files
Generated by the contractor, and at option
maintained
by operator
Reference file : A single good
run, or an amalgamation of
several to
match to other runs via Map
Matching Techniques.
That Provides the ability for Precise relative data alignment.
There are one or
more reference files for each
corridor and
direction ( More for the case of an alternate track)
Special Track map
Relates the Reference File Position
Annotation to Latitude, Longitude and Geodetic Distance Along
Track. Can be Made consistent with existing Track or Fly Maps.
(Note if a point is aligned
“relatively” it will be correctly positioned
to Geodetic Truth regardless of GPS condition in the area)
Example
MAP file excerpt:
|
Distance along track, From
0pt. Milepost, Geodetic |
Distance along track, From
0pt. MP, From Reference File Odom.. |
Latitude |
Longitude |
Elevation |
Heading
|
|
: |
|
|
|
|
|
|
: |
|
|
|
|
|
|
42592.6
|
42616.5 |
40.71066163 |
-74.187029 |
7 |
-155.53 |
|
42609.0
|
42632.9 |
40.71062061 |
-74.18705371
|
7 |
-155.53 |
|
42625.4
|
42649.4
|
40.71057956 |
-74.18707807
|
7 |
-155.53 |
|
: |
|
|
|
|
|
|
: |
|
|
|
|
|
Geodetic Milepost File Milepost LAT/LON , heading ,Geodetic
Distance Along Track, Vs. Milepost number. Found by Dropping a
Perpendicular of MP LAT/LON
To Track MAP to Obtain Distance (Regardless of how a point is marked on the Original
Geometry File, output is corrected in application output)
|
Milepost Number |
Distance along track, From
0pt. Milepost, Geodetic |
Line Code ID |
Latitude |
Longitude |
Heading, Degrees
|
|
: |
|
|
|
|
|
|
: |
|
|
|
|
|
|
10 |
38781.2
|
2 |
40.71952311 |
74.17985399 |
-141.237 |
|
11 |
44221.5
|
2 |
40.70657892 |
-74.18941949 |
-155.61 |
|
12 |
49596.9
|
2 |
40.69313284 |
-74.19740816 |
-155.77 |
|
: |
|
|
|
|
|
|
: |
|
|
|
|
|
Push Back Arrow Now
<----