Create a New Stop

• Recognizable landmarks
• Street intersections
• First street name is the street the stop is ON. Second street name is the intersecting street;
• Same abbreviations (if used) for all street types (eg, Ave);
• Same conjunctions (& OR and; @ OR at.)
• Matches what is posted on website and timetables

• Also known as "stop code," this is a customer-facing alphanumeric code that is usually associated with AVL/realtime arrival information.
• *If you have location codes exporting as stop id, such as for a real-time integration, you must include a location code in order to save.

No*

• Used with zone-based Fares. Zones must be created in Stop Zones.

No

Fare Zones

• Should be as exact as possible.
• Place stops on curbs and sidewalks where a rider should stand, not in the street or middle of intersections.
• For intersections with multiple service directions (eg, inbound and outbound, South and East) create a separate stop for each direction.

Yes

 GTFS.org

• Default is "Single Stop." See "Stations" for more details about creating a station with platforms and entrances.

Yes

• See "Stations" for more details about creating a station with platforms and entrances.

No

• See "Stations" for more details about creating a station with platforms and entrances.

No

• Internal-facing field for organizing stops based on cities. Useful for GTFS with zone-based Fares and sorting stops by city.

No

• Internal-facing field for organizing stops by direction. See "Directions" for more information.

No

• This field should be left blank and can not convey information to riders at this time. Use "Comments" for internal notes about a Stop.

No

• Text field for internal notes about a Stop.

No

• Customer-facing URL for this specific stop. Often associated with single-stop pages linked to AVL/realtime information.

No

• Customer-facing value. Should only be used if values available for all stops in the system.

No