Jay comments

Results 7 comments of

Jay

📄🚀 Accommodate other types of instantaneous events

Shall we remove the v1 tag from this issue?

📄🚀 – Document additional data types

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...

🐛📄 – TODS and TIDES Alignment: Mid-Trip Reliefs

I like @wmata-eajensen 's option 1 (move `operator_id` to `stop_visits`) because it resolves this issue and is simple, and I also like @botanize 's idea of a `vehicle_crew` table because...

Query tab goes blank when viewing empty geometry

Thanks, @pravesh-sharma . The log is below. I replaced some values with `***` for privacy. The last thing logged is the launching of pdAdmin. I Then replicated the bug but...

🚀💻 – Passenger Counts at Fare Gates Without Fare Transactions

I think it's useful to have a flexible file/table definition for instantaneous events in general. For vehicle data, I see `passenger_events` as a catch-all for any instantaneous vehicle-based event that...

🐛📄 – Resolving Conflict between Multiple Operators + Primary Key in trips_performed

I aggree with @botanize that this can be handled with #220, and that `trips_performed` shouldn't be split just because operators change.

🐛📄 – Improve event_type naming convention in passenger_events

I agree with what seemed to be the consesus (or majority view) on today's Contributors Group call: that something both human- and machine-readable like `passenger_boarded` is what should be used...