Data Types

This chapter lists all data types that HERE GNSS API supports divided into four sections.

Each section describes the data types that belong to one group, for example, GNSS assistance data.

The description has the number of the data type, the symbolic name of the data type, and the format of the payload. If the payload format is BER encoded LPP data, the description tells also which the LPP schema elements are present in the LPP data.

Chapter LPP ASN.1 Schema shows the full LPP schema and chapter Use Assistance Data shows how to decode the BER encoded data.

Assign the number of the data type to Request.data_type when requesting or subscribing to the data.

GNSS Assistance Data

18005 DATATYPE_AGNSS_GPS

Assistance data for GPS constellation.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child elements: gnss-ReferenceTime, gnss-IonosphericModel, gnss-TimeModels, gnss-NavigationModel, gnss-RealTimeIntegrity, gnss-Almanac, gnss-UTC-Model, gnss-AuxiliaryInformation

18006 DATATYPE_AGNSS_GLO

Assistance data for GLONASS constellation.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child elements: gnss-ReferenceTime, gnss-NavigationModel, gnss-RealTimeIntegrity, gnss-Almanac, gnss-UTC-Model, gnss-AuxiliaryInformation

18007 DATATYPE_AGNSS_GAL

Assistance data for Galileo constellation.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child elements gnss-ReferenceTime, gnss-IonosphericModel, gnss-TimeModels, gnss-NavigationModel, gnss-RealTimeIntegrity, gnss-Almanac, gnss-UTC-Model

18008 DATATYPE_AGNSS_BEI

Assistance data for Beidou constellation.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child elements: gnss-ReferenceTime, gnss-IonosphericModel, gnss-TimeModels, gnss-NavigationModel, gnss-RealTimeIntegrity, gnss-Almanac, gnss-UTC-Model

18030 DATATYPE_AGNSS_QZS

Assistance data for QZSS constellation.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child elements: gnss-ReferenceTime, gnss-IonosphericModel, gnss-TimeModels, gnss-NavigationModel, gnss-RealTimeIntegrity, gnss-Almanac, gnss-UTC-Model

HD GNSS Correction Data

17000 DATATYPE_IONEX

Global ionospheric maps (GIM) in IONEX 1.1 format. Contains 1-day to 2-day predicted GIMs.

Format: IONEX 1.1

Note: This datatype is deprecated. Use DATATYPE_XXX_IONO instead.

17001 DATATYPE_BSX

Differential code bias (DCB) data in BSX (Bias Solution INdependent EXchange Format (Bias-SINEX)) format.

Format: Bias-SINEX 1.00

Note: This datatype is deprecated. Use DATATYPE_XXX_CODE_BIAS instead.

18009 DATATYPE_GPS_CLOCKS

Clock corrections for GPS constellation.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child element: gnss-SSR-ClockCorrections-r15

18010 DATATYPE_GLO_CLOCKS

Clock corrections for GLONASS constellation.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child element: gnss-SSR-ClockCorrections-r15

18011 DATATYPE_GAL_CLOCKS

Clock corrections for Galileo constellation.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child element: gnss-SSR-ClockCorrections-r15

18012 DATATYPE_BEI_CLOCKS

Clock corrections for Beidou constellation.

Format: BER encoded LPP Root element: A-GNSS-ProvideAssistanceData

Child element: gnss-SSR-ClockCorrections-r15

18013 DATATYPE_GPS_ORBITS

Orbit corrections for GPS constellation.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child element: gnss-SSR-OrbitECEFCorrections-r15

18014 DATATYPE_GLO_ORBITS

Orbit corrections for GLONASS constellation.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child element: gnss-SSR-OrbitECEFCorrections-r15

18015 DATATYPE_GAL_ORBITS

Orbit corrections for Galileo constellation.

Format: BER encoded LPP

Root element A-GNSS-ProvideAssistanceData

Child element: gnss-SSR-OrbitECEFCorrections-r15

18016 DATATYPE_BEI_ORBITS

Orbit corrections for Beidou constellation.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child element: gnss-SSR-OrbitECEFCorrections-r15

18020 DATATYPE_GPS_ORBITS_RAC

Orbit corrections for GPS constellation in RAC-coordinate system.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child element: gnss-SSR-OrbitCorrections-r15

18021 DATATYPE_GLO_ORBITS_RAC

Orbit corrections for GLONASS constellation in RAC-coordinate system.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child element: gnss-SSR-OrbitCorrections-r15

18022 DATATYPE_GAL_ORBITS_RAC

Orbit corrections for Galileo constellation in RAC-coordinate system.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child element: gnss-SSR-OrbitCorrections-r15

18023 DATATYPE_BEI_ORBITS_RAC

Orbit corrections for Beidou constellation in RAC-coordinate system.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child element: gnss-SSR-OrbitCorrections-r15

18050 DATATYPE_GPS_CODE_BIAS

Code bias data for GPS constellation.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child element: gnss-SSR-CodeBias-r15

18051 DATATYPE_GLO_CODE_BIAS

Code bias data for GLONASS constellation.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child element: gnss-SSR-CodeBias-r15

18052 DATATYPE_GAL_CODE_BIAS

Code bias data for Galileo constellation.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child element: gnss-SSR-CodeBias-r15

18053 DATATYPE_BEI_CODE_BIAS

Code bias data for Beidou constellation.

Format: BER encoded LPP

Root element: A-GNSS-ProvideAssistanceData

Child element: gnss-SSR-CodeBias-r15

23000 DATATYPE_GPS_IONO

Ionospheric corrections for GPS constellation.

Format: BER encoded LPP. Two different message types.

Root element: A-GNSS-ProvideAssistanceData

Possible child elements:

  • gnss-SSR-CorrectionPoints-r16
  • gnss-SSR-STEC-Correction-r16, gnss-SSR-GriddedCorrection-r16

23001 DATATYPE_GLO_IONO

Ionospheric corrections for GLONASS constellation.

Format: BER encoded LPP. Two different message types.

Root element: A-GNSS-ProvideAssistanceData

Possible child elements:

  • gnss-SSR-CorrectionPoints-r16
  • gnss-SSR-STEC-Correction-r16, gnss-SSR-GriddedCorrection-r16

23002 DATATYPE_GAL_IONO

Ionospheric corrections for Galileo constellation.

Format: BER encoded LPP. Two different message types.

Root element: A-GNSS-ProvideAssistanceData

Possible child elements:

  • gnss-SSR-CorrectionPoints-r16
  • gnss-SSR-STEC-Correction-r16, gnss-SSR-GriddedCorrection-r16

23003 DATATYPE_BEI_IONO

Ionospheric corrections for Beidou constellation.

Format: BER encoded LPP. Two different message types.

Root element: A-GNSS-ProvideAssistanceData

Possible child elements:

  • gnss-SSR-CorrectionPoints-r16
  • gnss-SSR-STEC-Correction-r16, gnss-SSR-GriddedCorrection-r16

Predicted GNSS Assistance Data

22000 DATATYPE_NAV_MODEL_PREDICTIONS_GPS

Predicted navigation models for GPS for 14 days.

Format: several consecutive BER encoded LPP A-GNSS-ProvideAssistanceData elements.

Each element provides predicted navigation models for same Toe (Time of Ephemeris) for all valid GPS satellites. The validity of the navigation models starts 2 hours before the Toe and ends 2 hours after the Toe.

The interval between A-GNSS-ProvideAssistanceData elements is 2 hours. Therefore, 12 elements are needed to provide predictions for one day.

Typically, HERE GNSS Service calculates new predictions every 15 minutes, but the update rate is not fixed and may vary.

Root element: A-GNSS-ProvideAssistanceData

Child elements: gnss-ReferenceTime, gnss-NavigationModel

22020 DATATYPE_NAV_MODEL_PREDICTIONS_GLO

Predicted navigation models for Glonass for 14 days

Format: several consecutive BER encoded LPP A-GNSS-ProvideAssistanceData elements.

Each element provides predicted navigation models for same time for all valid Glonass satellites.

Each navigation model contains tb value that is the index of a 0.5 hour time interval within current day. The validity of the navigation models starts at the beginning of the specified time interval and ends when the time interval ends.

The interval between A-GNSS-ProvideAssistanceData elements is 0.5 hours. Therefore, 48 elements are needed to provide predictions for one day.

Typically, HERE GNSS Service calculates new predictions every 15 minutes, but the update rate is not fixed and may vary.

Root element: A-GNSS-ProvideAssistanceData

Child elements: gnss-ReferenceTime, gnss-NavigationModel

22040 DATATYPE_NAV_MODEL_PREDICTIONS_GAL

Predicted navigation models for Galileo for 7 days.

Format: several consecutive BER encoded LPP A-GNSS-ProvideAssistanceData elements.

Each element provides predicted navigation models for same Toe (Time of Ephemeris) for all valid Galileo satellites. The validity of the navigation models starts 2 hours before the Toe and ends 2 hours after the Toe.

The interval between A-GNSS-ProvideAssistanceData elements is 1 hour. Therefore, 24 elements are needed to provide predictions for one day.

Typically, HERE GNSS Service calculates new predictions every 15 minutes, but the update rate is not fixed and may vary.

Root element: A-GNSS-ProvideAssistanceData

Child elements: gnss-ReferenceTime, gnss-NavigationModel

22060 DATATYPE_NAV_MODEL_PREDICTIONS_BEI

Predicted navigation models for Beidou for 7 days.

Format: several consecutive BER encoded LPP A-GNSS-ProvideAssistanceData elements.

Each element provides predicted navigation models for same Toe (Time of Ephemeris) for all valid Beidou satellites. The validity of the navigation models starts 2 hours before the Toe and ends 2 hours after the Toe.

The interval between A-GNSS-ProvideAssistanceData elements is 2 hour. Therefore, 12 elements are needed to provide predictions for one day.

Typically, HERE GNSS Service calculates new predictions every 15 minutes, but the update rate is not fixed and may vary.

Root element: A-GNSS-ProvideAssistanceData

Child elements: gnss-ReferenceTime, gnss-NavigationModel

Note

Predicted navigation models are provided only for the operational satellites of each constellation.
For example, if there is a known outage period when the satellite will not be available, we don't calculate a prediction for the satellite for that time period.

Miscellaneous Data

20000 DATATYPE_UNIX_TIMESTAMP

Number of milliseconds since the Unix Epoch. This timestamp can be used, for example, for service monitoring and testing purposes.

Note

the standard Unix time is in seconds. In order to get the value in milliseconds, divide the value by 1000 and round down to the nearest integer value. Otherwise, the value is the same as the Unix time, just with a higher resolution (milliseconds vs. seconds) and without the Year 2038 Problem. Leap second handling is similar to that in the stardard Unix time.

By default, the server sends this data once per second. Less frequent updates can be requested by specifying the interval in a subscription request. Set the desired interval to Request.params[1]. The interval must be a 16-bit unsigned integer value (1 - 65535), which corresponds to a time interval from 1 seconds to about 18 hours. (Value 0 results in the default 1-second interval.)

Format: the data is a 64-bit unsigned integer value; 8 bytes in the little-endian order.

Example:
d9 7e 1b 0d 6b 01 00 00   = 1559293034201 = 2019-05-31T08:57:14.201Z

20001 DATATYPE_ISO_8601_DATETIME

Human-readable ISO-8601 formatted date-time string, which can be used, for example, for service monitoring and testing purposes.

By default, the server sends this data once per second. Less frequent updates can be requested by specifying the interval in a subscription request. Set the desired interval to Request.params[1]. The interval must be a 16-bit unsigned integer value (1 - 65535), which corresponds to a time interval from 1 seconds to about 18 hours. (Value 0 results in the default 1-second interval.)

The response data can be modified according to the user timezone by specifying the timezone to be used (defaults to UTC, specifically, +00:00). Set the desired timezone to Request.params[2] as an utf-8 string. The timezone string can be either:

  • a timezone name, for example, "America/Vancouver" or "Asia/Kolkata", or
  • UTC DST offset ±hhmm, for example, "-0700" or "+0530"

If the timezone name is not recognized, the server falls back to use UTC = +0000

Format: ascii/utf-8 string (without null-termination), up to 29 bytes.

Example:
   32 30 31 39 2d 30 35 2d 33 31 54 31 31 3a 35 35 3a 33 39 2e 30 39 31 2b
   30 33 3a 30 30    = "2019-05-31T11:55:39.091+03:00"

results matching ""

    No results matching ""