4.2 Port-to-Port Route Planning

Description

The Port-to-Port Route Planning queries the route plan between two ports, and obtain the total mileage of the route as well as the latitude and longitude coordinates of the points the route passes through.

Use Case

Logistics Tracking
Save the planned fixed route and match it against the vessel’s real-time position to monitor whether the vessel sails in compliance with the predefined route. Route deviation alerts can be triggered by calculating the distance between the vessel’s real-time position and the planned path. You may also overlay historical vessel tracks with the planned route for visualization, and compare discrepancies between the actual voyage track and the planned path.

Request Limits

An API key must be created before using this service. API calls are subject to quota restrictions according to your permission type. To view your current service access permissions, please contact our support team: support@elaneglobal.com.

Endpoint

Endpoint	HTTP Method
`https://api.elaneglobal.com/v1/Prediction/RoutePlanPortToPort`	Get

Example API Call

https://api.elaneglobal.com/v1/Prediction/RoutePlanPortToPort?key=1F6D701272402D1E7D8D316CCE519123&start_port_code=CNGZG&end_port_code=CNSHG&avoid=11

Note:
The key 1F6D701272402D1E7D8D316CCE519123 is the official key of elaneglobal.com, bound to the domain api.elaneglobal.com.
Users are not authorized to use this key for data access—utilizing it will return a status code 14, indicating an error in the source domain.
To trial the service, please contact our support team: support@elaneglobal.com.

Request Code Samples

Shell

JavaScript

Java

Swift

PHP

Python

HTTP

Objective-C

Ruby

OCaml

Dart

Responses

⚪0success

application/json

Body

Example

{
  "status": 0,
  "msg": "",
  "data": {
    "distance": 915.22,
    "route": [
      {
        "lng": 113.571144,
        "lat": 22.844316
      },
      {
        "lng": 113.56867,
        "lat": 22.82417
      },
      {
        "lng": 113.59017,
        "lat": 22.81067
      },
      {
        "lng": 113.6135,
        "lat": 22.78583
      },
      {
        "lng": 113.66833,
        "lat": 22.69617
      },
      {
        "lng": 113.68733,
        "lat": 22.64817
      },
      {
        "lng": 113.80333,
        "lat": 22.52833
      },
      {
        "lng": 114,
        "lat": 22
      },
      {
        "lng": 116,
        "lat": 22
      },
      {
        "lng": 117,
        "lat": 22.5
      },
      {
        "lng": 122.5,
        "lat": 28
      },
      {
        "lng": 123,
        "lat": 29
      },
      {
        "lng": 123,
        "lat": 30
      },
      {
        "lng": 122.5,
        "lat": 30.5
      },
      {
        "lng": 122.064,
        "lat": 31.1225
      },
      {
        "lng": 121.87067,
        "lat": 31.17867
      },
      {
        "lng": 121.73775,
        "lat": 31.28425
      },
      {
        "lng": 121.58414,
        "lat": 31.37979
      }
    ]
  }
}

4.2 Port-to-Port Route Planning

Description#

Use Case#

Request Limits#

Endpoint#

Example API Call#