{"componentChunkName":"component---src-templates-developers-js","path":"/en/developers/apis/2-routing-data-api/","result":{"data":{"childPages":{"edges":[{"node":{"fields":{"slug":"/en/developers/"},"frontmatter":{"title":"For developers","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/architecture/"},"frontmatter":{"title":"System architecture","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/api-registration/"},"frontmatter":{"title":"API portal and registration","order":-12,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/changes/"},"frontmatter":{"title":"Changes","order":-10,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/user-interfaces/"},"frontmatter":{"title":"User interfaces","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/deprecations/"},"frontmatter":{"title":"Deprecations","order":-11,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/docker-guide/"},"frontmatter":{"title":"Docker guide","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/"},"frontmatter":{"title":"APIs","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/1-routing-api/"},"frontmatter":{"title":"Routing API","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/2-routing-data-api/"},"frontmatter":{"title":"Routing data API","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/4-map-api/"},"frontmatter":{"title":"Map API","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/architecture/x-apis/"},"frontmatter":{"title":"API architecture","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/6-api-faq/"},"frontmatter":{"title":"FAQ","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/5-realtime-api/"},"frontmatter":{"title":"Realtime APIs","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/3-geocoding-api/"},"frontmatter":{"title":"Geocoding API","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/7-terms-of-use/"},"frontmatter":{"title":"Terms of use","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/user-interfaces/1-digitransit-ui/"},"frontmatter":{"title":"Digitransit-ui","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/1-routing-api/0-graphql/"},"frontmatter":{"title":"GraphQL","order":10,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/1-routing-api/3-realtime-information/"},"frontmatter":{"title":"Real-time information","order":40,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/1-routing-api/2-glossary/"},"frontmatter":{"title":"Glossary","order":30,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/1-routing-api/canceled-trips/"},"frontmatter":{"title":"Canceled trips","order":80,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/1-routing-api/disruption-info/"},"frontmatter":{"title":"Disruption info","order":70,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/1-routing-api/4-translations/"},"frontmatter":{"title":"Translation","order":50,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/1-routing-api/routes/"},"frontmatter":{"title":"Routes","order":100,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/1-routing-api/stops/"},"frontmatter":{"title":"Stops","order":110,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/1-routing-api/bicycles-scooters-cars/"},"frontmatter":{"title":"Bicycles, cars and e-scooters","order":60,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/1-routing-api/itinerary-planning/"},"frontmatter":{"title":"Itinerary planning","order":90,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/architecture/x-apis/1-routing-api/"},"frontmatter":{"title":"Routing API","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/architecture/x-apis/2-routing-data-api/"},"frontmatter":{"title":"Routing Data","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/architecture/x-apis/4-map-api/"},"frontmatter":{"title":"Map API","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/architecture/x-apis/5-realtime-api/"},"frontmatter":{"title":"Real-time APIs","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/architecture/x-apis/3-geocoding-api/"},"frontmatter":{"title":"Geocoding API","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/1-routing-api/1-graphiql/"},"frontmatter":{"title":"GraphiQL","order":20,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/4-map-api/background-map/"},"frontmatter":{"title":"Background map","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/5-realtime-api/1-getting-started/"},"frontmatter":{"title":"Getting started","order":10,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/3-geocoding-api/address-search/"},"frontmatter":{"title":"Address search","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/3-geocoding-api/autocomplete/"},"frontmatter":{"title":"Autocomplete","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/5-realtime-api/trip-updates/"},"frontmatter":{"title":"Trip updates","order":30,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/5-realtime-api/service-alerts/"},"frontmatter":{"title":"Service alerts","order":20,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/3-geocoding-api/address-lookup/"},"frontmatter":{"title":"Address lookup","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/4-map-api/pois/"},"frontmatter":{"title":"Points of interest","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/5-realtime-api/vehicle-positions/"},"frontmatter":{"title":"Vehicle positions","order":40,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/architecture/x-apis/3-geocoding-api/data-container/"},"frontmatter":{"title":"Data builder and container","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/architecture/x-apis/3-geocoding-api/api/"},"frontmatter":{"title":"API","order":null,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/5-realtime-api/vehicle-positions/high-frequency-positioning/"},"frontmatter":{"title":"High-frequency positioning","order":20,"redirect":null}}},{"node":{"fields":{"slug":"/en/developers/apis/5-realtime-api/vehicle-positions/digitransit-mqtt/"},"frontmatter":{"title":"Digitransit MQTT broker","order":10,"redirect":null}}}]},"markdownRemark":{"fields":{"slug":"/en/developers/apis/2-routing-data-api/"},"frontmatter":{"title":"Routing data API","redirect":null,"toc":null,"description":null,"assets":null,"technologies":null,"docker":null},"html":"

The routing data API provides four OpenTripPlanner (OTP) router datasets: Finland and Estonia, HSL region,\nSouthwest Finland region and Waltti cities. The available data sets are documented in\nthe architecture page for this API.

\n

OpenTripPlanner data and configuration files

\n

The available files are split into different endpoints for each of our routers (finland, hsl, varely and waltti). The currently\nactive routing data can be viewed from the corresponding production HTTP endpoints (use of either digitransit-subscription-key\nURL parameter or a header is needed, browsing with a browser can be clumsy due to this limitation):

\n
    \n
  1. https://api.digitransit.fi/routing-data/v3/finland/
    2. \n
  2. https://api.digitransit.fi/routing-data/v3/hsl/
    3. \n
  3. https://api.digitransit.fi/routing-data/v3/varely/
    4. \n
  4. https://api.digitransit.fi/routing-data/v3/waltti/
    5. \n
\n

Contents of the endpoints

\n

There are three types of files availables (some files are used for two purposes):

\n
    \n
  1. Files that are used to run an OTP server.
    2. \n
  2. Files that are used to build a graph for OTP.
    3. \n
  3. Log files.
    4. \n
\n

See how Routing API utilizes these files on the routing API page.

\n

Contents differ for different\nendpoints, but these examples are for the HSL endpoint:

\n

Files for running OTP

\n
    \n
  1. graph-hsl-753c4cfe9f63400f0ad093bc515d1bba6b8e14a1.zip\nThis zip contains the required files to run OpenTripPlanner server. The naming convention is graph-<router_id>-<commit_hash>.zip
    2. \n
  2. graph.obj\nA graph that can be loaded into latest version of OpenTripPlanner.
    3. \n
  3. streetGraph.obj\n(only exists if prebuilt street only graph was used to generate the complete graph)\nA street only graph that is used to generate the complete graph.
    4. \n
  4. otp-config.json\nThe configuration for enabling or disabling features in OTP.
    5. \n
  5. router-config.json\nThe per-router customized runtime configuration for OTP.
    6. \n
\n

Files for building OTP graph

\n
    \n
  1. build-config.json\nThis is the OTP configuration file that is used to build the OTP Graph file.
    2. \n
  2. hsl.pbf\nOpenStreetMap data file for the HSL region (used by OTP).
    3. \n
  3. HSL.zip\nGTFS file (other routers have many different GTFS files).
    4. \n
  4. HSL-lautta.zip\nGTFS file (other routers have many different GTFS files).
    5. \n
  5. otp-config.json\nThe configuration for enabling or disabling features in OTP.
    6. \n
  6. router-config.json\nThe per-router customized runtime configuration for OTP.
    7. \n
  7. router-hsl.zip\nThis zip contains the required files to build new OpenTripPlanner graph.
    8. \n
  8. hsl.tif\nElevation data file for the HSL region (used by OTP, not mandatory).
    9. \n
\n

Build log files

\n
    \n
  1. report\nDirectory containing issues and information from the previous graph build.
    2. \n
  2. street-report\n(only exists if prebuilt street only graph was used to generate the complete graph)\nDirectory containing issues and information from the previous street only graph build.
    3. \n
  3. build.log\nLog of the previous graph build.
    4. \n
  4. street-build.log\n(only exists if prebuilt street only graph was used to generate the complete graph)\nLog of the street only graph build used for the previous complete graph build.
    5. \n
  5. version.txt\nA version file that contains a timestamp (for example '2017-08-18T02:32:45.635Z') of the time when the data was processed.
    6. \n
  6. connected.csv\nList of stops that could be linked based on OSM data (for debugging purposes).
    7. \n
  7. unconnected.csv\nList of stops that could not be linked based on OSM data but they still do exist in the graph (for debugging purposes).
    8. \n
\n

Note to users of Finland and Estonia routing data

\n

The Finland and Estonia data endpoint contains information concerning public transport services by the cities and ELY-centers as well as data relevant to long distance market based coach connections in Finland. It also contains data for Estonia.

\n

Source for coach connection data is https://finap.fi which is Finnish National Access point for multimodal data (EU/MMTIS). Data is provided by respective transport operators. Finap.fi data is licensed with CC 4.0 BY. Finap.fi service is operated by Fintraffic.

\n

Please visit https://finap.fi and https://github.com/tmfg/mmtis-national-access-point/blob/master/docs/api/README.md if you are interested more wider use of Finap datasets.

\n

For more information contact Fintraffic with support channel email: nap@fintraffic.fi

\n

Related links

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
URLProject description
https://github.com/hsldevcom/OpenTripPlanner/Digitransit fork of OpenTripPlanner
https://github.com/opentripplanner/OpenTripPlanner/OpenTripPlanner upstream
https://github.com/hsldevcom/opentripplanner-data-container/Digitransit fork of OpenTripPlanner
https://blog.openstreetmap.org/OpenStreetMap blog
","tableOfContents":"","excerpt":"The routing data API provides four OpenTripPlanner (OTP) router datasets: Finland and Estonia, HSL region,\nSouthwest Finland region and Waltti cities. The available data sets are documented in\nthe…"}},"pageContext":{"slug":"/en/developers/apis/2-routing-data-api/"}},"staticQueryHashes":["3675773199","4050193485"]}