TPC 2026
TPC 2026

 

 

Navigation: Using GPS / GNSS > Importing GPS/GNSS >

Imported GPS/GNSS Data

 

 

 

 

Imported GPS/GNSS data can include either a geodetic position, a coordinate position based on some CRS, or both.

In addition, other data like RMS (Root Mean Squared), PDOP (Degradation of Precision), etc. may be available, depending on the GPS/GNSS data provider.


A GPS/GNSS Point Record

A GPS/GNSS data filter includes a line (record) for each point.  Each point record need only enough information to create the position of the point, but may also include additional information.

Here is a sample report of an imported GPS/GNSS point.

h7  Desc:

  Lat=44.0437884dN,  Lng=124.0807210dW, Ht=182.29

  Y=4168.283 X=4759.289 Z=0.00

  Origin: Global

  Antenna ht=6.34 Feet  Tilt Angle: 0.8 degrees

  Solution=FIX

    RMS: Y=0.036  X=0.035  Z=0.050 Horiz=0.050 Feet

    PDOP=1.90  GDOP=2.20

  Time=2024-05-29 12:57:12.0 UTC-07:00

    Sample size=51

    Satellites=8  GPS=6 GLONASS=2 Galileo=0 BeiDou=0 QZSS=0

  Base

    Base1 Y=-17459.123  X=-3270.513  Z=178.958 Feet

    Base1 Lat=43.9836020dN  Lng=124.1076920dW  Ht=-19.83 Feet

    Baseline Dist=23060.314 Feet  Mile=4.367

    CRS=NAD83(2011) / Oregon South (6) + NAVD88(GEOID18) height

 


Data Type (format character)

Each data type will be listed below, along with it's format character in parenthesis ().


Point (P)

Point label.  If provided, it can be modified to avoid conflicts with existing point labels, or used to update existing survey points.  See Importing Matching Points.


Description (D)

Point description.  Each point in TPC can have a description with any data, including point codes, dimensions, etc.


Attribute (A)

Point Attribute.  Each point in TPC can have an attribute. Some data collectors store a Code that TPC converts to an attribute.  Others include additional information specific to the point described, like an inventory ID on a power pole.


Easting (X), Northing (Y), Elevation (Z)

These are the CRS coordinates and elevation (orthometric height) of the point.

The elevation is the ground / mark elevation at that point.  For a monument like a brass cap, this mark elevation is the elevation at the top of the cap.

Unless otherwise specified, the coordinates are in the survey's units.


Longitude (x), Latitude (y), Ellipsoidal height (z)

These are the geodetic position and ellipsoide height of the point.

The ellipsoid height is the ground / mark elevation of that point.  For a monument like a brass cap, this mark elevation is the elevation at the top of the cap.

When importing GPS/GNSS CSV files, you can tell TPC if these values are decimal degrees or DMS.


RMS Easting (i), Northing (j), Elevation (k), Lateral (l)

RMS is the Root Mean Squared of the observed position, given in distance units that match the survey's coordinate unless otherwise specified.  So an RMS value of 0.03 would be 0.03 feet for a survey set to feet.

RMS values are sometimes thought of as 1 standard deviation of the true position being measured. 

Unless otherwise specified, the coordinates are in the survey's units.


Antenna height (t), Antenna height units (u)

This is the antenna height and units. TPC does not use these values if ellipsoid height is provided for that point.

Unless otherwise specified, the coordinates are in the survey's units.


Origin (Q)

emlid uses this to differentiate between Local (from coordinate position) and Global (from geodetic position).  A points may show both coordinates and geodetic position, just like in TPC.  This indicates which one is held and which one is computed from the CRS.

Beginning with TPC V24.0.4.0 7/11/2024, if TPC imports a point (from a GNSS file) with a sample size of 0, that point is considered to be a local point (non-geodetic) even if the Origin is not specified.  This allows TPC to properly handle local points that may have been exported to GNSS and then localized (calibrated) by the GNSS field software.


Title angle (a)

Angle, in decimal degrees, from vertical.  This values does not include the direction of the tilt, just the angle.


Solution status (n)

For RTK observations, TPC expects the solution status to be Fixed, Float or Single, although the values used to convey the status may vary by manufacturer.

When importing GPS/GNSS data, you can choose to accept solutions of a specific status, like Fixed.

Fixed

Fixed solutions are observations that are generally within 1 cm or 0.03 ft of the true position.

Float

Fixed solutions are observations that are generally within 0.5 to 1 m or 1 - 2 ft of the true position.

Single

Fixed solutions are observations that are generally within 3 to 5 m or 10 - 30 ft of the true position.

Note: GPS/GNSS points computed from PPK solutions may not provide a solution status.


Quality (q)

Quality of GPS Fix, specific to the manufacturer.


Averaging start (d), Averaging end (e), Samples (f)

When multiple observations are averaged to compute a position, this information provides the start / end times and the number of observations sampled.


PDOP (p), GDOP(b), HDOP, VDOP

These Degradation of Precision (DOP) values help indicate the quality of the observation(s) used to compute a point's position.

PDOP (Positional DOP) is derived from all the others and is considered a single value that can be used to evaluate an individual reading.  PDOP < 1.0 is always good.  PDOP < 2.0 is still considered acceptable.

TDOP (Time DOP) TPC does not currently read or store TDOP values.

GDOP (Geometric DOP) is a measure of the geometry of the satellite constellation.  A better spread of satellites means you get less dilution and hence a better signal. 

GDOP = square root(PDOP squared + TDOP squared).

GDOP values are typically >= PDOP values because they include the additional TDOP measurements.

See GPS Accuracy Explained, Dilution of Precision


Base easting (1), northing (2), elevation (3)

These are the coordinates of the base station / CORS / VRS / NTRIP Mount  used for the corrections applied to RTK observations.

Unless otherwise specified, the coordinates are in the survey's units.


Base longitude (4), latitude (5), ellipsoidal height (6)

These are the geodetic position of the base station / CORS / VRS / NTRIP Mount  used for the corrections applied to RTK observations.

When importing GPS/GNSS CSV files, you can tell TPC if these values are decimal degrees or DMS.


Baseline (7)

This is the distance from the base station / CORS / VRS / NTRIP Mount  to the point observed.  Unless otherwise specified, the distance is in the survey's units.


CS name (c)

Name of Base Station / CORS / VRS / NTRIP Mount used for the corrections applied to RTK observations. 


Satellites (BCEFH)

Number of satellites observed for each point recorded.

emlid uses the column headers GPS Satellites (B), GLONASS Satellites (C), Galileo Satellites (E), BeiDou Satellites (F), QZSS Satellites (H)


Related Topics

Using GPS/GNSS

Editions

Premium, Professional

 

 

 

Copyright © 2026 Traverse PC, Inc.