Nautical API

Overview

DTN Nautical API delivers high-quality marine weather forecast and hindcast data.

Data sources used for the Nautical API

The data source for the Nautical API is DTN Nautical MeteoBase (NMB) that combines the largest intake of available weather models, interpreted and enriched by DTN in-house meteorologists. This is also the source of data used in SPOS.

Value proposition of the Nautical API

The value proposition of the Nautical API is as listed in the following table, which emphasizes where DTN adds value to core data.

Practical use examples of the Nautical API

The Nautical API can be used in the following domains as listed in the following table.

Using credentials

When you have your client credentials, request an access token from the authorization server as follows:

POST /accounts/identity/connect/token HTTP/1.1
Host: api.routeguard.eu

Authorization: Basic {ClientSecret}
Content-Type: String
cache-control: no-cache

grant_type=password&username={Username}&password={password}&scope=web default rights claims openid
            

Use Case: Request marine weather parameters by location

You can request marine weather parameters for one or more location and timestamp combinations. When setting the timestamp value in the request body, make sure that the value falls within the range from one year in the past up until nine days in the future.

Table 5-22 lists the required API endpoint, body examples, and the HTTP method used.

{
 "items": [
   {
    "locatedAt": [73.4, -62.1],
    "validAt":"2018-07-12T21:00Z"
   },
   {
    "locatedAt": [52, -48],
    "validAt":"2018-02-22T18:00Z"
   }]
}
              

Request parameters

To request marine weather parameters for a location, supply the following items in the body of your API call.

Note: When you provide a location for anywhere on land, the API does not return any weather parameters for this location.

Sample response

The following is a sample response.

All parameters provided in the response are valid for a single location (as specified with locatedAt) and a specific time (as specified with validAt). Because the timestamp is in the past, this is a hindcast.

{
    "items": [
        {
            "locatedAt": [
                -27.97,
                -49.8078
            ],
            "validAt": "2018-05-02T00:00Z",
            "source": "hindcast",
            "airPressureInHectoPascal": 1009.09,
            "windSpeedInKnots": 20,
            "windDirectionInDegrees": 160,
            "seaHeightInMeters": 1.43,
            "seaPeriodInSeconds": 5,
            "swellDirectionInDegrees": 240,
            "swellHeightInMeters": 1.6,
            "swellPeriodInSeconds": 9,
            "visibilityCode": 0,
            "visibility": "Good",
            "weatherCode": 1,
            "weather": "Partly cloudy",
            "precipitationProbabilityInPercent": 1,
            "heightOf500HectoPascalLevelInMeters": 5380,
            "seaTemperatureInCelsius": 6,
            "airTemperatureInCelsius": 3,
            "windSpeedAt50MetersInKnots": 22,
            "windDirectionAt50MetersInDegrees": 160,
            "icingClass": 0,
            "icing": "None",
            "riskWindSpeedInKnots": 21,
            "windGustInKnots": 25,
            "windGustAt50MetersInKnots": 28,
            "totalWaveHeightInMeters": 2.2,
            "totalWaveDirectionInDegrees": 240,
            "riskWaveHeightInMeters": 2.4,
            "seaCurrentSpeedInKnots": 0.41,
            "seaCurrentDirectionInDegrees": 200
        }
    ]
}

Response definitions

The table below describes each item in the response.