Skip to content
Submit a ticket
Sign in
  • There are no suggestions because the search field is empty.

Network API Docs

The Point One Navigation RTK NTRIP API provides GNSS corrections over the NTRIP protocol. The service supports clients using both the NTRIP 1.0 and NTRIP 2.0 specifications.

System Overview

The NTRIP stream endpoints and corresponding messages support RTCM3 streams over HTTP using basic (username and password) authentication.

Connection Details

Endpoint Port Description
truertk.pointonenav.com 2102 TLS Encrypted
truertk.pointonenav.com 2101 plaintext, not recommended for production designs

Parameters

Field Description
Username The username field should be populated with an NTRIP username provided by the webapp/GraphQL API
Password The password field should be populated with an NTRIP password that will be provided by Point One Navigation.
Mountpoint This should be ITRF2014 or LOCAL depending on the use case.

Sending locations

In order to receive corrections, the client must send a location to the Point One service. Locations can either be sent in the initial request using a NMEA GGA header, or by sending GGA lines to the server after the initial connection. See the NMEA-0183 GPGGA message section for details on the format of GGA messages.

NMEA-0183 GPGGA message

The NMEA-0183 GPGGA message type is used to send locations, and has the following format:

$GPGGA,235317.000,4003.9039,N,10512.5793,W,1,08,1.6,1577.9,M,-20.7,M,,0000*5F

This example GPGGA sentence contains the following fields:

  • Time: 235317.000 is 23:53 and 17.000 seconds in Greenwich mean time
  • Longitude: 4003.9040,N is latitude in DDmm.mm, north
  • Latitude: 10512.5792,W is longitude in DDmm.mm, west
  • Number of satellites seen: 08
  • Altitude: 1577 meters

Where DD is degrees, and mm.mm is minutes.

Additional Details

  • NTRIP 1.0
    • For NTRIP 1.0 responses, clients should include the Ntrip-Version: ntrip/1.0 header. The service will respond with ICY 200 OK followed by a new line and then the binary RTCM stream.
  • NTRIP 2.0
      • For NTRIP 2.0 responses, clients should include the Ntrip-Version: ntrip/2.0 header. The service will respond with the standard HTTP/1.1 200 OK response followed by standard HTTP headers, followed by the binary RTCM stream. For NTRIP 2.0, the RTCM stream will be sent to the client using chunked encoding, as indicated by the Transfer-Encoding: chunked header.