Skip to content

Update min_transfer_time requirement for transfers - #668

Open
skalexch wants to merge 1 commit into
google:masterfrom
MobilityData:fix_min_transfer_time_req
Open

skalexch wants to merge 1 commit into
google:masterfrom
MobilityData:fix_min_transfer_time_req

Conversation

@skalexch

@skalexch skalexch commented Oct 19, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

This proposal corrects the requirements for min_transfer_time, making the field forbidden when transfers are not possible (transfer_type=3) or are in-seat transfers (transfer_type=4).

Describe the Problem

min_transfer_time is optional for all transfers where transfer_type is not 2. However, transfer_type = 3 and 4 are respectively "no transfers possible" and "in-seat transfer", which cannot be associated with any minimum time window.

Proposed Solution

Forbid min_transfer_time when transfers are not possible (transfer_type=3) or are in-seat transfers (transfer_type=4).

Type of change

GTFS Schedule

  • Functional Change
  • Non-Functional Change
  • Documentation Maintenance

Proposed Discussion Period

We will leave this PR open one week for discussion, one week for review (minimum per governance). Then we will raise a vote to adopt this fix.

Proposal Update Tracker

Date Update Description
(2026-10-19) (Raised proposal)
(2026-10-19) (Discussion period started)

Checklist

@skalexch

Copy link
Copy Markdown
Collaborator Author

Tagging @gcamp and @rudiejd for awareness since the last additions to min_transfer_time and transfer_type were #303 and #640

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant