GTFS Stops To Features (Public Transit Tools)
Summary
Converts a GTFS stops.txt file from a GTFS public transit dataset to a feature class of public transit stops.
Usage
A file geodatabase feature class is recommended for tool output instead of a shapefile because shapefile field names have a maximum of 10 characters. Longer GTFS field names will be shortened if the output table is a shapefile.
To edit GTFS stop locations and attributes, use this tool to import an existing
stops.txtfile, make edits in the map, and export the edited table back to GTFS format using the Features To GTFS Stops tool.The
stop_latandstop_lonfields in the GTFSstops.txtfile define the latitude and longitude of stops. These fields are permitted by the specification to be null if the stop'slocation_typefield has a value of 3 or 4. However, because this tool creates geographical features to represent stops, it cannot map stops that have no latitude or longitude. Consequently, stops withlocation_typevalues of 3 or 4 that have null values forstop_latorstop_lonwill be skipped and not included in the tool's output.When the folder containing the
input_stops.txtfile also includes GTFSstop_times.txt,trips.txt, androutes.txtfiles, aroute_infofield will be added to the output. This field will contain information about the GTFS routes that use each stop. The field values are JSON strings consisting of the following keys and a list of values:route_id—The route IDs the stop serves (GTFSroute_id)route_type—The modes of public transit that use the stop (GTFSroute_type)
For example, a value can be structured as
{"route_id":["route_1","route_2","route_3"],"route_type":["0", "2"]}.This field can be parsed for use in symbology and pop-ups.
Parameters
| Label | Explanation | Data type |
|---|---|---|
|
Input GTFS Stops File |
A valid |
File |
|
Output Feature Class |
The output feature class. |
Feature Class |
Environments
Licensing information
- Basic: Yes
- Standard: Yes
- Advanced: Yes