GuidesAPI Reference
API Reference
  1. HERE GNSS Data API v2
  2. GNSS Data

Real-time assistance data

get
https://gnss.hereapi.com/v2/assistance

Request real-time A-GNSS data for GPS, GLONASS, Galileo, BeiDou, or QZSS satellite systems.

This service provides following GNSS Assistance Data Elements,
see 3GPP TS 37.355 specification
for detailed information.

  • GNSS-ReferenceTime
  • GNSS-IonosphericModel
  • GNSS-TimeModelList
  • GNSS-NavigationModel
  • GNSS-RealTimeIntegrity
  • GNSS-Almanac
  • GNSS-UTC-Model
  • GNSS-AuxiliaryInformation

Note, these values are based on the current service configuration and may be changed in future.
Availability of the above data elements depend on the GNSS system.

GNSS assistance data is typically updated every 30 - 60 minutes depending on the GNSS system.

Query Params
gnss
array of strings

Specifies the GNSS system(s) for which real-time assistance data is requested.
Data for multiple GNSS systems can be requested by specifying several supported values
separated by comma.

Supported values are:

  • gps: Global Positioning System (GPS)
  • glo: Global Navigation Satellite System (GLONASS)
  • gal: Galileo Navigation Satellite System
  • bds: BeiDou Navigation Satellite System
  • qzs: Quasi-Zenith Satellite System (QZSS)

If this parameter is not provided, data for all supported GNSS systems is returned.

string
enum
Defaults to uper

Specifies the encoding format for the LPP messages in the response.
Supported values as per ASN.1 specification are:

  • jer: JSON Encoding Rules (JER).
    The response content type depends on Accept header and can be either of the following:
    • application/json-seq (default) - JSON text sequences with each item containing a single LPP message in JER format.
    • application/json - single JSON object, which contains one or more LPP messages in JER format.
    • application/x-ndjson - newline-delimited JSON objects, each containing a single LPP message in JER format.
  • uper: Unaligned Packed Encoding Rules (UPER).
    The response content type is multipart/mixed and it consists of
    one or more binary LPP messages in application/octet-stream format.
Allowed:
string
enum
Defaults to data

Specifies the LPP ASN.1 element to be used as the root element for the LPP messages in the response.
Supported values are:

  • data: The root element is the A-GNSS-ProvideAssistanceData sequence.
  • full: The root element is the LPP-Message sequence.

Clients might be able to reduce the size of the code used to parse ASN.1 messages
by requesting data as the root element, especially for binary encodings, such as UPER.

Allowed:
string
length between 4 and 101

A list of up to six billing tags, separated by the + sign. This parameter provides a way to track your platform usage. For details, refer to the Cost Management Developer Guide section on Billing Tags.

Headers
string

Indicates preferred content encodings in the response. The server uses content negotiation (see RFC 9110) to select the best option and informs the choice in the Content-Encoding response header. Supported encodings are: "gzip", "deflate", "br" (and "identity"). If this header is missing, the response may or may not be compressed, client has to check the response headers for that information. If all supported encodings are disabled (e.g. "*;q=0"), the server will respond with status code 406 "Not Acceptable".

string

User-provided token that can be used to trace a request or a group of requests sent to the service. Can be any string, but UUID is recommended. It will be echoed in the response.

string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Updated 4 days ago

Did this page help you?
Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
multipart/mixed
application/json
application/x-ndjson
application/json-seq

Updated 4 days ago

Did this page help you?