Platform Doors

[georgevicbell]

Summary

Adds an optional stop_doors field to stops.txt with the following values:
0 - No doors installed
1 - Full Height Doors or Screen
2 - 3/4 Height Doors or Screen
3 - Half Height Doors or Screen
4 - Full Height Fence or Panel
5 - 3/4 Height Doors or Screen
6 - Half Height Doors or Screen
7 - Under Construction
8 - Partially Out of Order
9 - Completely Out of Order

Describe the Problem

Resolves #612

Include whether a stop is protected with full, 3/4, 1/2 height platform doors. This could apply to subway, LRT, or even bus stops (many examples). We also see on some systems the use of static platform fences or panels - again 1/2, 3/4 or full height.

Practically this provides information for parents, users with accessibility needs or those who are anxious about platform safety.

In some stations individual platforms may vary as to the level of protection or platform design.

Use Cases

• Information for users, apps (for example an app that helps folks with mental health issues navigate a transit system safely may be able to prioritize alternate stations or routes to ensure safer travel)
• Allow for analysis of different systems and stations
• Track the ongoing construction and status of platform doors (this is similar to elevators, escalators etc.)

Type of change

GTFS Schedule

• Functional Change
• Non-Functional Change
• Documentation Maintenance

GTFS Realtime

• Specification Change
• Specification Change (Experimental Field)

Additional Information

I run a website - platformdoors.info - it is currently very difficult to determine if individual platforms at stations have platform doors, whether they are working, or what style they are. I had thought GTFS would have had this information but it appears it doesn't.

Proposed Discussion Period

I think 1 month of discussion would make sense, but am open to whatever the community believes is reasonable.

Testing Details

• Consumer(s): www.platformdoors.info
• Producer(s):
• Estimated Testing Period:

Proposal Update Tracker

Date	Update Description
(2026-02-16)	PR Created in Draft

Checklist

• I have read and understood the GTFS Change process.
• I have read and understood the GTFS Guiding Principles.
• I understand the Role of Advocate and the Responsibilities attached to it.
• I have signed the Contributor License Agreement (CLA).
• I have ensured that this proposal is not covered by an existing Pull Request.

[gcamp]

It make more sense to me to have this information in something like stop amenities than one-more-field approach that's suggested here.