What location data should I provide for rail journeys?

Created by Olivia Gibson, Modified on Mon, 29 Jul, 2024 at 10:46 AM by Olivia Gibson

The location object in Thrust Calculator accepts many different means of identifying a place. Try to add as much detail about the place as you can; Thrust Calculator will intelligently create the best model to resolve the location for the rail segment.


Below are examples of all the location fields we accept:

  1. City Code
    1. Type: String
    2. Description: Three-letter city code (e.g., LON for London).
  1. Country Code
    1. Type: String
    2. Description: Two-letter country code (ISO 3166-1 alpha-2, e.g., GB for Great Britain).
  1. City Name
    1. Type: String
    2. Description: Name of the city, district, suburb, town, or village.
  1. Region
    1. Type: String
    2. Description: State, county, province, or region.
  1. UIC Code
    1. Type: String
    2. Description: Train station identifier.
  1. SNCF Code
    1. Type: String
    2. Description: Train station identifier for SNCF.
  1. Coordinates
    1. Type: Object
    2. Description: Latitude and longitude coordinates of the location.
  1. Trainline Normalized Code
    1. Type: String
    2. Description: Identifier from Trainline’s dataset for railway stations (e.g., urn:trainline:public:nloc).

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article