Format of the "GPS/Leveling" file  (code: eval2  26-feb-92 dgm)

01-04  Station Serial Number   integer, right justified
05-34  Station Name            character, left justified
35-36  Geodetic Lat., deg.     integer, right justified
37-38  Geodetic Lat., min.     integer, right justified
39-45  Geodetic Lat., sec.     integer, right justified, units 0.00001"
46-46  Code (N/S)              character, upper case
47-49  Geodetic Lon., deg.     integer, right justified
50-51  Geodetic Lon., min.     integer, right justified
52-58  Geodetic Lon., sec.     integer, right justified, units 0.00001"
59-59  Code (E/W)              character, upper case
60-66  Ellipsoidal Height      integer, right justified, units of 1 mm
67-67     blank
68-74  Orthometric Height      integer, right justified, units of 1 mm
75-75     blank
76-76  GPS Order (Hztl)        character, upper case
77-77  Ortho Elevation Code    character, upper case
78-78  Ortho Order             character, upper case
79-79  Ortho Datum Code        character, upper case
80-80  Reject Code             character, upper case

COMMENTS

Station Serial Number
---------------------
   Arbitrary positive index number. Not to be repeated within a given file.

GPS Order (Hztl)
----------------
Code   Explanation
 A     Length Relative Accuracy (2 sigma) better than 1:10,000,000
 B     Length Relative Accuracy (2 sigma) better than 1: 1,000,000
 1     Length Relative Accuracy (2 sigma) better than 1:   100,000
 2     Length Relative Accuracy (2 sigma) better than 1:    20,000
 3     Length Relative Accuracy (2 sigma) better than 1:     5,000

Ortho Elevation Code
--------------------
Code   Explanation
 A     OHT established using FGCS leveling specifications and
       procedures, adjusted height determined using NGS Vertical
       Network Branch procedures, leveling data is in the NGSIDB.
 B     OHT established using FGCS leveling specifications and
       procedures, adjusted height determined using NGS Vertical
       Network Branch procedures, leveling data is not in the
       NGSIDB. (USGS, COE, some state DOT data.)
 C     OHT established using FGCS leveling specifications and
       procedures, adjusted height is 'posted'.  See explanation
       in the footnote (*) below.
 H     OHT established using FGCS leveling specifications and
       procedures except for the two-mark leveling tie
       requirement.  (Horizontal field party level ties, some
       state DOTs, some GPS level ties.)
 L     OHT established using leveling RESET specifications and
       procedures.
 F     OHT established by fly-leveling.
 T     OHT established by leveling between control points which
       are not Bench Marks.
 R     OHT established by reciprocal vertical angles.
 V     OHT established by non-reciprocal vertical angles.
 P     OHT established by photogrammetry.
 M     OHT established by scaling from a contoured map.
 G     OHT established by GPS observations.
 D     OHT established by datum transformations.

* Data for level lines containing 'posted' BMs were purposely not
included in the NAVD88 general adjustment.  Subsequently, these
data were adjusted to NAVD88 by forcing them to fit the existing
NAVD88 general adjustment heights.

Ortho Order
-----------
Code   Explanation
 1     Relative Accuracy (2 sigma) better than 0.7 mm x sqrt(Km)
 2     Relative Accuracy (2 sigma) better than 1.3 mm x sqrt(Km)
 3     Relative Accuracy (2 sigma) better than 2.0 mm x sqrt(Km)

Ortho Datum Code
----------------
 Code    Explanation
 blank   North American Vertical Datum of 1988
   9     National Geodetic Vertical Datum of 1929

Reject Code
-----------
   An asterisk ("*") indicates a rejection (for various experiments)
Blank indicates no rejection.