📄🚀 – Document additional data types
This issue will document additional data types that should be supported by TIDES (see #99). Some examples:
- Transfer Request
- Transfer Acceptance
- Transfer Hold
- Timepoint Crossing
- MDT Canned Message
- Dispatch Canned Message
- Mechanical Alarm
- Driver Violation
- Covert Alarm
- Overt Alarm
- Request to Talk
- Subsystem Health
- MDT Priority Canned Message
- Logon Verification
- Stopped Too Long
- Engine Controller Info
- MT Mobile Events
- Route Status
- Farebox Alarm
- Fallback Status
- Bike Rack Usage
- Logon Status
- IRMA Pass. Count Diagnostics
- Operator Absent Alarm
- Announcements Disabled
- Service Area Alarm
- Critical Transfer Alarm
- Wheel Chair Dwell
- Proximity Tag Event
- departure predictions
+1 for arrival and departure predictions
Some other record types touched on in #99 are
- Various onboard announcements (not sure if these overlap with the MDT messages Joey mentioned) such as upcoming stop name, destination name, stop requested, various safety/security messages, etc.
- Track circuit or signal block state changes (occupied/unoccupied).
- Track-based platform arrival, departure, door open, door close. These could live in
stop_visitsif they're combined in one record, or they could be recorded in another table as individual instantaneous events. - Generic instantaneous event records from various system logs (such as station elevators or escalator banks, farebox vaulting systems, ticket vending machines, gates, fareboxes, etc). This might be a fallback for data sources that don’t fit into any other specific table and that only need a device reference, a timestamp, some event-type code, and perhaps an optional text comment.
I have created a Google Sheet here to track the different types of event records and the fields that could be associated with each.
If you work with data for any of the listed events, please indicate which field you have data for (mark with "x") If your responses vary significantly from others, either note that with comments, or add a copy of the row to reflect your data If there are new fields, add columns for those and mark with an "x" If there are other types of events you have data for (or variations on the ones listed) add new rows
IRMA Pass. Count Diagnostics
Should we include vendor specific items? Hella is another vendor, among many others.