google / google/transit

frequencies.txt primary key: add end_time, headway_secs & exact_times?

Open
#514 9 comments 0 reactions 0 assignees View on GitHub
Change type: Functional Discussion Period GTFS Schedule Status: Stale Support: Needs Feedback
Dominant language
No language data
Stars
1.1k
Forks
225
Avg merge
7d 17h
Merged PRs (30d)
3

Description

### Describe the problem

Currently, [`frequencies.txt`]()'s primary key does not include `exact_times`:

> Primary key (`trip_id`, `start_time`)

### Use cases

*Isn't it a perfectly valid use case to have >1 frequencies entries** for the same trip and starting at the same time? Some examples:
- two frequencies-based "windows" a different `end_time` & `headway_secs` – e.g. `trip_id=t1`/`start_time=07:00:00`/`end_time=22:00:00`/`headway_secs=600`, and `trip_id=t1`/`start_time=07:00`/`end_time=09:00`/`headway_secs=300` for additional "supporting" buses during rush hour
- two "windows" with all fields equal except `exact_times`

### Proposed solution

I propose to extend the primary key to the other columns (`end_time`, `headway_secs`, `exact_times`), too.

### Additional information

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.