Maritime Routing API
      Back to home
      1. Help Center
      2. Spire Sense Maritime
      3. Maritime Routing API

      Spire Maritime Predicted Routing V1

      Details of the Spire Maritime Routing Features V1

      Predicted Route And Calculated ETA To Destination Port

      For premium subscribers only, Predicted Routing and Predicted ETA at a matched destination port will be returned as demonstrated below in the Spire Sense Vessels API. 
      The ETA provided in AIS can often be missing or not kept up to date when the vessels want to delay providing updated information or hide their ETA for commercial reasons. In these instances Spire predicted ETA can show the real ETA. Also when the ETA is reported correctly, Spire Predicted ETA helps validate that it is correct.
       
      For in depth analysis of the value of these features see our blog stories
       
      Trial Access
      Sample the features of Spire's Predict AI - Routing for free with our ETA Route Calculator shown below. Register here https://insights.spire.com/port-eta-distance-calculator   to test all the features of Spire's Predict AI - Routing for free .
      port-eta-distance-sample_USHOU_QINGDAO
       
      Routing Algorithm
      When a vessels AIS reported destination port is matched for a vessel, we predict the route it will take from it's current position to the matched port location.  Matched destination ports are detailed in the FAQ article here

      The algorithm is based on machine learning from historic tracks of similar vessels. For dry bulk vessels the predicted route takes account of the vessel size, for other vessels the shortest route is returned.

      The following data is added to the premium Vessels API response:

                 "predicted_route": {

                      "distance": "141.0",

                      "ETA": "2020-05-14 01:48:04"

                      "time_of_calculation": "2020-05-13 12:00:10.974008" 

                      "start_position": {

                                             "type": "Point",

                                             "coordinates": [ -87.51667, 18.85167 ]

                                          },

                      "end_position": UNLOCODE,

                      "route": { "type": "LineString",

                             "coordinates": [ [4.65874, 54.27595], [4.4617, 54.0367],

                                                      [4.4025, 53.795], [4.4683, 53.56], [4.5325, 53.3921],

                                                      [4.41, 53.187075], [4.3283, 52.965],

                                                      [4.25585, 52.84915], [4.16415, 52.7],

                                                      [4.125, 52.5017], [4.045425, 52.302525],

                                                      [4.01415, 52.05915], [4.0, 52.0]

                                                    ] },

                                       }

       

      Below is a plot of many sample routes returned by Predict AI Route, showing the predicted routes from a sample of vessels recognised with a destination of Rotterdam
      Release Notes
      Release 1. In the initial release July 2020, routing is only provided to dry bulk ports. Other ports which do not handle dry bulk will be added in future updates.
      Release 2. September 2020, routing is only provided for all ports and all types of vessels

      NOTE: 2021-10-19 Spire Maritime launched a new version of the Maritime Routing API. 

      The V1 routing API will be replaced by the predictedVesselRoute feature of the Maritime 2.0 graphQL service which is documented here https://maritime-docs.spire.com/api/maritime_20/fundamentals#predictedvesselroute-query-arguments

       

      Predicted Routing V1 is a feature of the Vessels API and both Vessels API and Predicted Routing V1 will be sunset in 2022 and users migrated to Maritime 2.0 GraphQL and the predictedVesselRoute feature of the Maritime 2.0 graphQL service

       

      Customer Support
      If you have any questions about this feature upgrade then please reach out to the Spire Sales Engineering team using our client request web form here https://spire.com/developers/support/