--- title: "Computes all reachable locations from a given stop within a set duration. Each result entry will contain the fastest travel duration and the number of connections used." method: GET path: "/api/v6/one-to-all" tags: ["routing"] --- # Computes all reachable locations from a given stop within a set duration. Each result entry will contain the fastest travel duration and the number of connections used. `GET /api/v6/one-to-all` ## Query parameters - `one` string, required - `time` string, date-time - `maxTravelTime` integer, required - `arriveBy` boolean - `maxTransfers` integer - `minTransferTime` integer - `additionalTransferTime` integer - `transferTimeFactor` number - `maxMatchingDistance` number - `useRoutedTransfers` boolean - `pedestrianProfile` 'FOOT' | 'WHEELCHAIR' — Different accessibility profiles for pedestrians. - `pedestrianSpeed` number — Average speed for pedestrian routing in meters per second - `cyclingSpeed` number — Average speed for bike routing in meters per second - `vehicleHeight` number — Vehicle height for HGV routing in meters - `vehicleWidth` number — Vehicle width for HGV routing in meters - `vehicleLength` number — Vehicle length for HGV routing in meters - `vehicleWeight` number — Vehicle gross weight for HGV routing in tons - `vehicleHazmat` boolean — Whether the vehicle carries hazardous materials for HGV routing - `vehicleHazmatWater` boolean — Whether the vehicle carries hazardous materials dangerous to water for HGV routing - `vehicleAxleCount` integer — Axle count for HGV routing - `vehicleAxleLoad` number — Maximum axle load for HGV routing in tons - `vehicleTrailer` boolean — Whether the vehicle has a trailer for HGV routing - `vehicleTopSpeed` integer — Vehicle top speed for HGV routing in km/h - `vehicleLezAccess` boolean — Whether the vehicle is allowed to use low-emission zones for HGV routing - `elevationCosts` 'NONE' | 'LOW' | 'HIGH' — Different elevation cost profiles for street routing. Using a elevation cost profile will prefer routes with a smaller incline and smaller difference in elevation, even if the routed way is longer. - `NONE`: Ignore elevation data for routing. This is the default behavior - `LOW`: Add a low penalty for inclines. This will favor longer paths, if the elevation increase and incline are smaller. - `HIGH`: Add a high penalty for inclines. This will favor even longer paths, if the elevation increase and incline are smaller. - `transitModes` Mode[] - `preTransitModes` Mode[] - `postTransitModes` Mode[] - `requireBikeTransport` boolean - `requireCarTransport` boolean - `noCompulsoryReservation` boolean - `maxPreTransitTime` integer - `maxPostTransitTime` integer ## Response `200` The starting position and a list of all reachable stops If no paths are found, the reachable list is empty. - Reachable — Object containing all reachable places by One-to-All search - `one` Place - `name` string, required — name of the transit stop / PoI / address - `stopId` string — The ID of the stop. This is often something that users don't care about. - `parentId` string — If it's not a root stop, this field contains the `stopId` of the parent stop. - `importance` number — The importance of the stop between 0-1. - `lat` number, required — latitude - `lon` number, required — longitude - `level` number — level according to OpenStreetMap If no level is given, the field will be unset. For older versions (v1-v5), this field is mandatory and therefore set to 0. Affected endpoints: plan, trip, stoptimes, one-to-all, map/stops, map/trips - `tz` string — timezone name (e.g. "Europe/Berlin") - `arrival` string, date-time — arrival time - `departure` string, date-time — departure time - `scheduledArrival` string, date-time — scheduled arrival time - `scheduledDeparture` string, date-time — scheduled departure time - `scheduledTrack` string — scheduled track from the static schedule timetable dataset - `track` string — The current track/platform information, updated with real-time updates if available. Can be missing if neither real-time updates nor the schedule timetable contains track information. - `stopCode` string — Short, abbreviated identifier of the stop intended for users (e.g. printed on signage, used in SMS / passenger info systems). Comes from the GTFS `stop_code` field. - `description` string — description of the location that provides more detailed information - `vertexType` 'NORMAL' | 'BIKESHARE' | 'TRANSIT' — - `NORMAL` - latitude / longitude coordinate or address - `BIKESHARE` - bike sharing station - `TRANSIT` - transit stop - `pickupType` 'NORMAL' | 'NOT_ALLOWED' — - `NORMAL` - entry/exit is possible normally - `NOT_ALLOWED` - entry/exit is not allowed - `dropoffType` 'NORMAL' | 'NOT_ALLOWED' — - `NORMAL` - entry/exit is possible normally - `NOT_ALLOWED` - entry/exit is not allowed - `cancelled` boolean — Whether this stop is cancelled due to the realtime situation. - `alerts` Alert[] — Alerts for this stop. - `code` string — Attribute or notice code (e.g. for HRDF or NeTEx) - `communicationPeriod` TimeRange[] — Time when the alert should be shown to the user. If missing, the alert will be shown as long as it appears in the feed. If multiple ranges are given, the alert will be shown during all of them. - `start` string, date-time, required — If missing, the interval starts at minus infinity. If a TimeRange is provided, either start or end must be provided - both fields cannot be empty. - `end` string, date-time, required — If missing, the interval ends at plus infinity. If a TimeRange is provided, either start or end must be provided - both fields cannot be empty. - `impactPeriod` TimeRange[] — Time when the services are affected by the disruption mentioned in the alert. - `start` string, date-time, required — If missing, the interval starts at minus infinity. If a TimeRange is provided, either start or end must be provided - both fields cannot be empty. - `end` string, date-time, required — If missing, the interval ends at plus infinity. If a TimeRange is provided, either start or end must be provided - both fields cannot be empty. - `cause` 'UNKNOWN_CAUSE' | 'OTHER_CAUSE' | 'TECHNICAL_PROBLEM' | 'STRIKE' | 'DEMONSTRATION' | 'ACCIDENT' | 'HOLIDAY' | 'WEATHER' | 'MAINTENANCE' | 'CONSTRUCTION' | 'POLICE_ACTIVITY' | 'MEDICAL_EMERGENCY' | 'SPECIAL_EVENT' — Cause of this alert. - `causeDetail` string — Description of the cause of the alert that allows for agency-specific language; more specific than the Cause. - `effect` 'NO_SERVICE' | 'REDUCED_SERVICE' | 'SIGNIFICANT_DELAYS' | 'DETOUR' | 'ADDITIONAL_SERVICE' | 'MODIFIED_SERVICE' | 'OTHER_EFFECT' | 'UNKNOWN_EFFECT' | 'STOP_MOVED' | 'NO_EFFECT' | 'ACCESSIBILITY_ISSUE' — The effect of this problem on the affected entity. - `effectDetail` string — Description of the effect of the alert that allows for agency-specific language; more specific than the Effect. - `url` string — The URL which provides additional information about the alert. - `headerText` string, required — Header for the alert. This plain-text string will be highlighted, for example in boldface. - `descriptionText` string, required — Description for the alert. This plain-text string will be formatted as the body of the alert (or shown on an explicit "expand" request by the user). The information in the description should add to the information of the header. - `ttsHeaderText` string — Text containing the alert's header to be used for text-to-speech implementations. This field is the text-to-speech version of header_text. It should contain the same information as headerText but formatted such that it can read as text-to-speech (for example, abbreviations removed, numbers spelled out, etc.) - `ttsDescriptionText` string — Text containing a description for the alert to be used for text-to-speech implementations. This field is the text-to-speech version of description_text. It should contain the same information as description_text but formatted such that it can be read as text-to-speech (for example, abbreviations removed, numbers spelled out, etc.) - `severityLevel` 'UNKNOWN_SEVERITY' | 'INFO' | 'WARNING' | 'SEVERE' — The severity of the alert. - `imageUrl` string — String containing an URL linking to an image. - `imageMediaType` string — IANA media type as to specify the type of image to be displayed. The type must start with "image/" - `imageAlternativeText` string — Text describing the appearance of the linked image in the image field (e.g., in case the image can't be displayed or the user can't see the image for accessibility reasons). See the HTML spec for alt image text. - `flex` string — for `FLEX` transports, the flex location area or location group name - `flexId` string — for `FLEX` transports, the flex location area ID or location group ID - `flexStartPickupDropOffWindow` string, date-time — Time that on-demand service becomes available - `flexEndPickupDropOffWindow` string, date-time — Time that on-demand service ends - `modes` Mode[] — available transport modes for stops - `all` ReachablePlace[] — List of locations reachable by One-to-All - `place` Place - `name` string, required — name of the transit stop / PoI / address - `stopId` string — The ID of the stop. This is often something that users don't care about. - `parentId` string — If it's not a root stop, this field contains the `stopId` of the parent stop. - `importance` number — The importance of the stop between 0-1. - `lat` number, required — latitude - `lon` number, required — longitude - `level` number — level according to OpenStreetMap If no level is given, the field will be unset. For older versions (v1-v5), this field is mandatory and therefore set to 0. Affected endpoints: plan, trip, stoptimes, one-to-all, map/stops, map/trips - `tz` string — timezone name (e.g. "Europe/Berlin") - `arrival` string, date-time — arrival time - `departure` string, date-time — departure time - `scheduledArrival` string, date-time — scheduled arrival time - `scheduledDeparture` string, date-time — scheduled departure time - `scheduledTrack` string — scheduled track from the static schedule timetable dataset - `track` string — The current track/platform information, updated with real-time updates if available. Can be missing if neither real-time updates nor the schedule timetable contains track information. - `stopCode` string — Short, abbreviated identifier of the stop intended for users (e.g. printed on signage, used in SMS / passenger info systems). Comes from the GTFS `stop_code` field. - `description` string — description of the location that provides more detailed information - `vertexType` 'NORMAL' | 'BIKESHARE' | 'TRANSIT' — - `NORMAL` - latitude / longitude coordinate or address - `BIKESHARE` - bike sharing station - `TRANSIT` - transit stop - `pickupType` 'NORMAL' | 'NOT_ALLOWED' — - `NORMAL` - entry/exit is possible normally - `NOT_ALLOWED` - entry/exit is not allowed - `dropoffType` 'NORMAL' | 'NOT_ALLOWED' — - `NORMAL` - entry/exit is possible normally - `NOT_ALLOWED` - entry/exit is not allowed - `cancelled` boolean — Whether this stop is cancelled due to the realtime situation. - `alerts` Alert[] — Alerts for this stop. - `code` string — Attribute or notice code (e.g. for HRDF or NeTEx) - `communicationPeriod` TimeRange[] — Time when the alert should be shown to the user. If missing, the alert will be shown as long as it appears in the feed. If multiple ranges are given, the alert will be shown during all of them. - `start` string, date-time, required — If missing, the interval starts at minus infinity. If a TimeRange is provided, either start or end must be provided - both fields cannot be empty. - `end` string, date-time, required — If missing, the interval ends at plus infinity. If a TimeRange is provided, either start or end must be provided - both fields cannot be empty. - `impactPeriod` TimeRange[] — Time when the services are affected by the disruption mentioned in the alert. - `start` string, date-time, required — If missing, the interval starts at minus infinity. If a TimeRange is provided, either start or end must be provided - both fields cannot be empty. - `end` string, date-time, required — If missing, the interval ends at plus infinity. If a TimeRange is provided, either start or end must be provided - both fields cannot be empty. - `cause` 'UNKNOWN_CAUSE' | 'OTHER_CAUSE' | 'TECHNICAL_PROBLEM' | 'STRIKE' | 'DEMONSTRATION' | 'ACCIDENT' | 'HOLIDAY' | 'WEATHER' | 'MAINTENANCE' | 'CONSTRUCTION' | 'POLICE_ACTIVITY' | 'MEDICAL_EMERGENCY' | 'SPECIAL_EVENT' — Cause of this alert. - `causeDetail` string — Description of the cause of the alert that allows for agency-specific language; more specific than the Cause. - `effect` 'NO_SERVICE' | 'REDUCED_SERVICE' | 'SIGNIFICANT_DELAYS' | 'DETOUR' | 'ADDITIONAL_SERVICE' | 'MODIFIED_SERVICE' | 'OTHER_EFFECT' | 'UNKNOWN_EFFECT' | 'STOP_MOVED' | 'NO_EFFECT' | 'ACCESSIBILITY_ISSUE' — The effect of this problem on the affected entity. - `effectDetail` string — Description of the effect of the alert that allows for agency-specific language; more specific than the Effect. - `url` string — The URL which provides additional information about the alert. - `headerText` string, required — Header for the alert. This plain-text string will be highlighted, for example in boldface. - `descriptionText` string, required — Description for the alert. This plain-text string will be formatted as the body of the alert (or shown on an explicit "expand" request by the user). The information in the description should add to the information of the header. - `ttsHeaderText` string — Text containing the alert's header to be used for text-to-speech implementations. This field is the text-to-speech version of header_text. It should contain the same information as headerText but formatted such that it can read as text-to-speech (for example, abbreviations removed, numbers spelled out, etc.) - `ttsDescriptionText` string — Text containing a description for the alert to be used for text-to-speech implementations. This field is the text-to-speech version of description_text. It should contain the same information as description_text but formatted such that it can be read as text-to-speech (for example, abbreviations removed, numbers spelled out, etc.) - `severityLevel` 'UNKNOWN_SEVERITY' | 'INFO' | 'WARNING' | 'SEVERE' — The severity of the alert. - `imageUrl` string — String containing an URL linking to an image. - `imageMediaType` string — IANA media type as to specify the type of image to be displayed. The type must start with "image/" - `imageAlternativeText` string — Text describing the appearance of the linked image in the image field (e.g., in case the image can't be displayed or the user can't see the image for accessibility reasons). See the HTML spec for alt image text. - `flex` string — for `FLEX` transports, the flex location area or location group name - `flexId` string — for `FLEX` transports, the flex location area ID or location group ID - `flexStartPickupDropOffWindow` string, date-time — Time that on-demand service becomes available - `flexEndPickupDropOffWindow` string, date-time — Time that on-demand service ends - `modes` Mode[] — available transport modes for stops - `duration` integer — Total travel duration - `k` integer — k is the smallest number, for which a journey with the shortest duration and at most k-1 transfers exist. You can think of k as the number of connections used. In more detail: k=0: No connection, e.g. for the one location k=1: Direct connection k=2: Connection with 1 transfer ## Other responses - `400` — Bad Request - `404` — Not Found - `422` — Unprocessable Entity - `500` — Internal Server Error --- [API](https://skmtc.net/motis-project/apis/motis-api.md) · [All operations](https://skmtc.net/motis-project/apis/motis-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/motis-project/motis-api/revisions/faf7ed029357/schema)