Linux SDK (lite-qmi)  MBPL_SDK_R25_ENG3
QmiCbkLocPositionReportInd Struct Reference

#include <qaGobiApiCbk.h>

Data Fields

swi_uint256_t TlvPresenceMask
 
ULONG sessionStatus
 
BYTE sessionId
 
double * pLatitude
 
double * pLongitude
 
FLOAT * pHorUncCircular
 
FLOAT * pHorUncEllipseSemiMinor
 
FLOAT * pHorUncEllipseSemiMajor
 
FLOAT * pHorUncEllipseOrientAzimuth
 
BYTE * pHorConfidence
 
ULONG * pHorReliability
 
FLOAT * pSpeedHorizontal
 
FLOAT * pSpeedUnc
 
FLOAT * pAltitudeWrtEllipsoid
 
FLOAT * pAltitudeWrtMeanSeaLevel
 
FLOAT * pVertUnc
 
BYTE * pVertConfidence
 
ULONG * pVertReliability
 
FLOAT * pSpeedVertical
 
FLOAT * pHeading
 
FLOAT * pHeadingUnc
 
FLOAT * pMagneticDeviation
 
ULONG * pTechnologyMask
 
precisionDilutionpPrecisionDilution
 
ULONGLONG * pTimestampUtc
 
BYTE * pLeapSeconds
 
gpsTimepGpsTime
 
FLOAT * pTimeUnc
 
ULONG * pTimeSrc
 
sensorDataUsagepSensorDataUsage
 
ULONG * pFixId
 
svUsedforFixpSvUsedforFix
 
BYTE * pAltitudeAssumed
 
velocitypVelEnu
 
velocitypVelEncEnu
 
ULONGLONG * pNavSolutionMask
 
ULONG * pSensorSubTechnologyMask
 
BYTE * pGnssOnlyPosition
 
extendedPrecisionDilutionpExtendedPrecisionDilution
 
diffCorrectionSourceIDpDifferentialCorrectionSourceID
 
ULONGLONG * pSpoofReportMask
 
expandedSVspExpandedSVs
 
svsSignalTypespSvsSignalTypes
 
jammerIndicatorListpJammerIndicator
 

Detailed Description

This structure contains Event Position Report

Parameters
sessionStatus
  • Values
    • 0 - Session was successful
    • 1 - Session is still in progress; further position reports will be generated until either the fix criteria specified by the client are met or the client response timeout occurs.
    • 2 - Session failed..
    • 3 - Fix request failed because the session timed out.
    • 4 - Fix request failed because the session was ended by the user.
    • 5 - Fix request failed due to bad parameters in the request.
    • 6 - Fix request failed because the phone is offline.
    • 7 - Fix request failed because the engine is locked
sessionId
  • ID of the session that was specified in the Start request
  • Range - 0 to 255
pLatitude
  • Latitude (specified in WGS84 datum)
  • Type - Floating point
  • Units - Degrees
  • Range - -90.0 to 90.0
  • Positive values indicate northern latitude
  • Negative values indicate southern latitude
pLongitude
  • Longitude (specified in WGS84 datum)
  • Type - Floating point
  • Units - Degrees
  • Range - -180.0 to 180.0
  • Positive values indicate eastern latitude
  • Negative values indicate western latitude
pHorUncCircular
  • Horizontal position uncertainty.
  • Units - Meters
pHorUncEllipseSemiMinor
  • Semi-minor axis of horizontal elliptical uncertainty.
  • Units - Meters
pHorUncEllipseSemiMajor
  • Semi-major axis of horizontal elliptical uncertainty.
  • Units: Meters
pHorUncEllipseOrientAzimuth
  • Elliptical horizontal uncertainty azimuth of orientation.
  • Units - Decimal degrees
  • Range - 0 to 180
pHorConfidence
  • Horizontal uncertainty confidence.
  • If both elliptical and horizontal uncertainties are specified in this message, the confidence corresponds to the elliptical uncertainty.
  • Units - Percentage
  • Range 0-99
pHorReliability
  • Values
    • 0 - Location reliability is not set.
    • 1 - Location reliability is very low; use it at your own risk
    • 2 - Location reliability is low; little or no cross-checking is possible.
    • 3 - Location reliability is medium; limited cross-check passed
    • 4 - Location reliability is high; strong cross-check passed
pSpeedHorizontal
  • Horizontal speed.
  • Units - Meters/second
pSpeedUnc
  • 3-D Speed uncertainty.
  • Units - Meters/second.
pAltitudeWrtEllipsoid
  • Altitude With Respect to WGS84 Ellipsoid.
  • Units - Meters
  • Range -500 to 15883
pAltitudeWrtMeanSeaLevel
  • Altitude With Respect to Sea Level.
  • Units - Meters
pVertUnc
  • Vertical uncertainty.
  • Units - Meters
pVertConfidence
  • Vertical uncertainty confidence.
  • Units - Percentage
  • Range 0 to 99
pVertReliability
  • Values
    • 0 - Location reliability is not set.
    • 1 - Location reliability is very low; use it at your own risk.
    • 2 - Location reliability is low; little or no cross-checking is possible
    • 3 - Location reliability is medium; limited cross-check passed
    • 4 - Location reliability is high; strong cross-check passed
pSpeedVertical
  • Vertical speed.
  • Units - Meters/second
pHeading
  • Heading.
  • Units - Degree
  • Range 0 to 359.999
pHeadingUnc
  • Heading uncertainty.
  • Units - Degree
  • Range 0 to 359.999
pMagneticDeviation
  • Difference between the bearing to true north and the bearing shown on a magnetic compass. The deviation is positive when the magnetic north is east of true north.
pTechnologyMask
  • Values
    • 0x00000001 - Satellites were used to generate the fix
    • 0x00000002 - Cell towers were used to generate the fix
    • 0x00000004 - Wi-Fi access points were used to generate the fix
    • 0x00000008 - Sensors were used to generate the fix
    • 0x00000010 - Reference Location was used to generate the fix
    • 0x00000020 - Coarse position injected into the location engine was used to generate the fix
    • 0x00000040 - AFLT was used to generate the fix
    • 0x00000080 - GNSS and network-provided measurements were used to generate the fix
-pPrecisionDilution
pTimestampUtc
  • UTC timestamp
  • Units - Milliseconds since Jan. 1, 1970
pLeapSeconds
  • Leap second information. If leapSeconds is not available, timestampUtc is calculated based on a hard-coded value for leap seconds.
  • Units - Seconds
-pGpsTime
pTimeUnc
  • Time uncertainty.
  • Units - Milliseconds
pTimeSrc
  • Values
    • 0 - Invalid time.
    • 1 - Time is set by the 1X system.
    • 2 - Time is set by WCDMA/GSM time tagging.
    • 3 - Time is set by an external injection.
    • 4 - Time is set after decoding over-the-air GPS navigation data from one GPS satellite.
    • 5 - Time is set after decoding over-the-air GPS navigation data from multiple satellites.
    • 6 - Both time of the week and the GPS week number are known.
    • 7 - Time is set by the position engine after the fix is obtained
    • 8 - Time is set by the position engine after performing SFT, this is done when the clock time uncertainty is large.
    • 9 - Time is set after decoding GLO satellites.
    • 10- Time is set after transforming the GPS to GLO time
    • 11- Time is set by the sleep time tag provided by the WCDMA network.
    • 12- Time is set by the sleep time tag provided by the GSM network
    • 13- Source of the time is unknown
    • 14- Time is derived from the system clock (better known as the slow clock); GNSS time is maintained irrespective of the GNSS receiver state
    • 15- Time is set after decoding QZSS satellites.
    • 16- Time is set after decoding BDS satellites.
-pSensorDataUsage
pFixId
  • Fix count for the session. Starts with 0 and increments by one for each successive position report for a particular session.
-pSvUsedforFix
pAltitudeAssumed
  • Indicates whether altitude is assumed or calculated.
  • Value
    • 0x00 - Altitude is calculated
    • 0x01 - Altitude is assumed
Parameters
pVelEnu
  • Velocity ENU (East, North, Up)
  • Values: East, North, Up velocity. Units: Meters/second
  • See velocity
    Parameters
    pVelEncEnu
    • Velocity Uncertainty ENU
    • Values: East, North, Up velocity uncertainty. Units: Meters/second
  • See velocity
    Parameters
    pNavSolutionMask
    • Navigation solutions that are used to calculate the GNSS position report.
    • Valid bitmasks:
      • QMI_LOC_NAV_MASK_SBAS_ CORRECTION_IONO (0x00000001) - Bitmask specifying whether SBAS ionospheric correction is used
      • QMI_LOC_NAV_MASK_SBAS_ CORRECTION_FAST (0x00000002) - Bitmask specifying whether SBAS fast correction is used
      • QMI_LOC_NAV_MASK_SBAS_ CORRECTION_LONG (0x00000004) - Bitmask specifying whether SBAS long-tem correction is used
      • QMI_LOC_NAV_MASK_SBAS_ INTEGRITY (0x00000008) - Bitmask specifying whether SBAS integrity information is used
      • QMI_LOC_NAV_MASK_ CORRECTION_DGNSS (0x00000010) - Bitmask specifying whether DGNSS information is used
      • QMI_LOC_NAV_MASK_ONLY_ SBAS_CORRECTED_SV_USED (0x00000020) - Bitmask specifying whether only SBAS corrected SVs are used for the fix; if mask is not set, all-in-view SVs are used for fix
    pSensorSubTechnologyMask
    • Sensor subtechnology information.
      • Valid bitmasks:
      • QMI_LOC_SENSOR_SUB_MASK_ PDR_ENABLED (0x00000001) - Bitmask specifying whether PDR is enabled or disabled
      • QMI_LOC_SENSOR_SUB_MASK_ PEDOMETER_ENABLED (0x00000002) - Bitmask specifying whether a pedometer was used
      • QMI_LOC_SENSOR_SUB_MASK_ VEHICULAR_ENABLED (0x00000004) - Bitmask specifying whether vehicular sensor assistance is enabled or disabled
    pGnssOnlyPosition
    • GNSS Only Position Report
      • Indicates if this position report is generated from GNSS only technology.
      • Values:
        • 0x00 (FALSE) - Position is generated with other technologies (default)
        • 0x01 (TRUE) - Position is generated from GNSS technology only
    pExtendedPrecisionDilution
    • Extended Dilution of Precision Dilution of precision associated with this position.
  • See extendedPrecisionDilution
Parameters
pDifferentialCorrectionSourceID
  • Differential correction source ID
Parameters
pSpoofReportMask
  • Spoof report
    • Valid bitmasks:
    • QMI_LOC_POSITION_SPOOFED (0x00000001) - Set bit indicates suspected spoofing in position
    • QMI_LOC_TIME_SPOOFED (0x00000002) - Set bit indicates suspected spoofing in time
    • QMI_LOC_NAVIGATION_DATA_ SPOOFED (0x00000004) - Set bit indicates suspected spoofing in navigation data
pExpandedSVs
  • Expanded SVs Used to Calculate the Fix.
  • See expandedSVs
    Parameters
    pSvsSignalTypes
    • SVs Signal Types in the SVs Used list.
  • See svsSignalTypes
    Parameters
    pJammerIndicator
    • Jammer Indicator of each GNSS Signal Indicates the jammer indicator of each signal.
  • See jammerIndicatorList

The documentation for this struct was generated from the following file: