Contents
Documentation
Stops
Last updated
Stops are stops.txt entities imported from GTFS, and include the same basic structure and fields, plus some additional metadata.
The location_type value indicates the purpose of each stop:
location_type | Name | Description |
|---|---|---|
0 (or empty) | Stop or platform | Where passengers board or alight from a transit vehicle. This is the most common type. |
1 | Station | A physical structure or area containing one or more platforms |
2 | Entrance or exit | Where passengers enter or exit a station from the street |
3 | Generic node | A location within a station used to link together pathways |
4 | Boarding area | A specific location on a platform where passengers board or alight |
Location types 3 and 4 are used with GTFS pathways.
Stops form hierarchical relationships using the parent_station field:
- Stops and platforms (
location_type=0) may belong to a parent station (location_type=1) - Entrances (
location_type=2) and generic nodes (location_type=3) must have a parent station - Boarding areas (
location_type=4) must have a parent platform (location_type=0) - Stations (
location_type=1) cannot have a parent station
This hierarchy is particularly important for complex transit facilities like major train stations or airports, where pathways connect multiple platforms, entrances, and boarding areas. The API returns a stop's parent and children, along with its level and pathways.
As with routes, the Onestop ID values for stops are automatically generated, from a 10-character geohash of the stop's location and the stop_name. Two very similar stops may both generate the same Onestop ID, in which case a query for that Onestop ID will return two or more stop entries.
When querying stops through the Transitland API, stops include additional context beyond the standard GTFS fields:
| Field | Description |
|---|---|
route_stops | The routes whose trips serve the stop, each with its operating agency. Parent stations have no entries, since trips serve their child platforms. In the REST API, this field is included when requesting a single stop. |
feed_version | The feed version the stop was imported from, and its source feed |
place | The country and state or province that contains the stop (see places), for example adm0_iso: "US" and adm1_iso: "US-CA" |
level | The station level the stop is on, for multi-level stations (such as platforms and mezzanines) |
parent | The stop's parent station, if any |
For detailed information about querying stops, see the REST API stops endpoint.