Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
Used in:
Used in:
One of these 3
All the samples are stored in this sample attribute
Information on position error deduced from a GPS fix This data will be produced when TREX identifies an important "jump" during a gps fix (in the order of tens to hundreds of meters): As this information will come after the samples are propagated the receiver of the message may need to apply this error to previously received samples. The way to apply it is the following for all sample such as gps_fix.from_time <= sample.utime < gps_fix.to_time sample.northing = sample.northing + (sample.utime-gps_fix.from_time)*gps_fix.northing_rate sample.easting = sample.easting + (sample.utime-gps_fix.from_time)*gps_fix.easting_rate end for
Used in:
Date where the error started to apply
Date where the error was identified
northing at to_time (m)
easting at to_time (m)
May add lat,lon info in the future optional float longitude = 5; optional float latitude = 6;
northing navigation error (m/s)
easting navigation error (m/s)
One data sample Location (northing,easting) is not corrected as it is sampled in real-time. Do also note that we used UTM instead of lat,lon here. This is mostly due to the fact that TREX uses this reference for navigation and his lat,lon information is pretty bad (2 decimal places of accuracy which can result on an error of 100s of m) Note : based on Mike McCann suggestion northing and easting have been made optional as they may be replaced in the future by lat/lon
Used in:
unix time for the sample (seconds)
UTM nothing (m)
UTM easting (m)
Vehicle depth (m)
temperature (C)
salinity
Nitrate
indicate which gulper was fired (if any)