Skip to content

Clarify event_count usage and APC data guidance #248

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
chrisyamas wants to merge 2 commits into
base: develop
Choose a base branch
from
Open

Clarify event_count usage and APC data guidance #248

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a8cd5ca
Clarify event_count field documentation for passenger_events table
chrisyamas Dec 30, 2025
6ad12dd
Update Changelog to include unreleased event_count clarification update
chrisyamas Dec 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

## [Unreleased]

### Changed

- `passenger_events.event_count` description clarified to specify when values > 1 are appropriate, direct aggregated APC data to stop_visits, and clarify that 0 is distinct from null ([#236](https://github.com/TIDES-transit/TIDES/issues/236))

## [1.0] - 2025-12-23

### Changed
Expand Down
2 changes: 1 addition & 1 deletion spec/passenger_events.schema.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,7 @@
"name": "event_count",
"type": "integer",
"title": "Event count",
"description": "Count for this event, e.g., 3 for a Passenger Boarding event with 3 boardings, default is `1`",
"description": "Count for this event. Default is `1`. Use values > 1 only for truly simultaneous events (e.g., a parent carrying a child through a doorway as a single boarding event). Aggregated APC counts (e.g., '6 passengers boarded at this stop') should be recorded in stop_visits, not passenger_events, since passenger_events is intended for discrete, instantaneous events. A value of `0` indicates that the event was recorded but no passengers were counted (e.g., door opened but no one boarded), which is distinct from null/missing data.",
"constraints": {
"minimum": 0
}
Expand Down