Enum gpsd_proto::ResponseData[−][src]

pub enum ResponseData {
    Device {
        path: Option<String>,
        activated: Option<String>,
        flags: Option<i32>,
        driver: Option<String>,
        subtype: Option<String>,
        bps: Option<u16>,
        parity: Option<String>,
        stopbits: Option<u8>,
        native: Option<u8>,
        cycle: Option<f32>,
        mincycle: Option<f32>,
    },
    Tpv {
        device: Option<String>,
        mode: Mode,
        time: Option<String>,
        ept: Option<f32>,
        lat: Option<f64>,
        lon: Option<f64>,
        alt: Option<f32>,
        epx: Option<f32>,
        epy: Option<f32>,
        epv: Option<f32>,
        track: Option<f32>,
        speed: Option<f32>,
        climb: Option<f32>,
        epd: Option<f32>,
        eps: Option<f32>,
        epc: Option<f32>,
    },
    Sky {
        device: Option<String>,
        xdop: Option<f32>,
        ydop: Option<f32>,
        vdop: Option<f32>,
        tdop: Option<f32>,
        hdop: Option<f32>,
        gdop: Option<f32>,
        pdop: Option<f32>,
        satellites: Vec<Satellites>,
    },
}

Responses from gpsd after handshake (i.e. the payload)

Variants

Device information

Fields of Device

Name the device for which the control bits are being reported, or for which they are to be applied. This attribute may be omitted only when there is exactly one subscribed channel.

Time the device was activated as an ISO8601 timestamp. If the device is inactive this attribute is absent.

Bit vector of property flags. Currently defined flags are: describe packet types seen so far (GPS, RTCM2, RTCM3, AIS). Won't be reported if empty, e.g. before gpsd has seen identifiable packets from the device.

GPSD's name for the device driver type. Won't be reported before gpsd has seen identifiable packets from the device.

Whatever version information the device returned.

Device speed in bits per second.

N, O or E for no parity, odd, or even.

Stop bits (1 or 2).

0 means NMEA mode and 1 means alternate mode (binary if it has one, for SiRF and Evermore chipsets in particular). Attempting to set this mode on a non-GPS device will yield an error.

Device cycle time in seconds.

Device minimum cycle time in seconds. Reported from ?DEVICE when (and only when) the rate is switchable. It is read-only and not settable.

GPS position.

A TPV object is a time-position-velocity report. The "mode" field will be emitted before optional fields that may be absent when there is no fix. Error estimates will be emitted after the fix components they're associated with. Others may be reported or not depending on the fix quality.

Fields of Tpv

Name of the originating device.

NMEA mode, see Mode enum.

Time/date stamp in ISO8601 format, UTC. May have a fractional part of up to .001sec precision. May be absent if mode is not 2 or 3.

Estimated timestamp error (%f, seconds, 95% confidence). Present if time is present.

Latitude in degrees: +/- signifies North/South. Present when mode is 2 or 3.

Longitude in degrees: +/- signifies East/West. Present when mode is 2 or 3.

Altitude in meters. Present if mode is 3.

Longitude error estimate in meters, 95% confidence. Present if mode is 2 or 3 and DOPs can be calculated from the satellite view.

Latitude error estimate in meters, 95% confidence. Present if mode is 2 or 3 and DOPs can be calculated from the satellite view.

Estimated vertical error in meters, 95% confidence. Present if mode is 3 and DOPs can be calculated from the satellite view.

Course over ground, degrees from true north.

Speed over ground, meters per second.

Climb (positive) or sink (negative) rate, meters per second.

Direction error estimate in degrees, 95% confidence.

Speed error estinmate in meters/sec, 95% confidence.

Climb/sink error estimate in meters/sec, 95% confidence.

Satellites information.

A SKY object reports a sky view of the GPS satellite positions. If there is no GPS device available, or no skyview has been reported yet.

Many devices compute dilution of precision factors but do not include them in their reports. Many that do report DOPs report only HDOP, two-dimensional circular error. gpsd always passes through whatever the device actually reports, then attempts to fill in other DOPs by calculating the appropriate determinants in a covariance matrix based on the satellite view. DOPs may be missing if some of these determinants are singular. It can even happen that the device reports an error estimate in meters when the corresponding DOP is unavailable; some devices use more sophisticated error modeling than the covariance calculation.

Fields of Sky

Name of originating device.

Longitudinal dilution of precision, a dimensionless factor which should be multiplied by a base UERE to get an error estimate.

Latitudinal dilution of precision, a dimensionless factor which should be multiplied by a base UERE to get an error estimate.

Altitude dilution of precision, a dimensionless factor which should be multiplied by a base UERE to get an error estimate.

Time dilution of precision, a dimensionless factor which should be multiplied by a base UERE to get an error estimate.

Horizontal dilution of precision, a dimensionless factor which should be multiplied by a base UERE to get a circular error estimate.

Hyperspherical dilution of precision, a dimensionless factor which should be multiplied by a base UERE to get an error estimate.

Spherical dilution of precision, a dimensionless factor which should be multiplied by a base UERE to get an error estimate.

List of satellite objects in skyview.

Trait Implementations

impl Debug for ResponseData
[src]

Formats the value using the given formatter. Read more

Auto Trait Implementations