Describe the feature you want and how it meets your needs or solves a problem
As a creator of TIDES data, I want capture the location of passenger count and fare transaction events
The current spec does not include location information (lat/long, GPS quality, etc.) for passenger_events or fare_transactions records. If an AFC or APC system includes location data, then the correct application of TIDES would be to create both a passenger_events or fare_transaction record and a vehicle_locations record.
Question 1: Does this still sound right? Or should we add location fields to the passenger_events and fare_transactions records?
Question 2: If we leave the fields as they are, do we want to be more explicit about how two records that represent the same event are related to each other.
For example, if I have single APC record that has both passenger counts and a location, I would create both a passenger_events record and a vehicle_locations record. I want to be able to link those.
Option 1: allow and require that the unique identifier for the two records match. So if the passenger_event_id and the location_ping_id are the same, that means the records are for the same event.
Option 2: add an optional reference to the a vehicle_locations record from the passenger_events and fare_transactions tables.
My preference is currently Option 2.
Describe the solution you'd like
Add field passenger_events.location_ping_id to identify the location of a passenger count
Add field fare_transactions.location_ping_id to identify the location of a fare transaction
Describe alternatives you've considered
Allow passenger_events.passenger_event_id and fare_transactions.transaction_id to match vehicle_locations.location_ping_id and define this to mean that the records are associated with the same event.
Describe the feature you want and how it meets your needs or solves a problem
As a creator of TIDES data, I want capture the location of passenger count and fare transaction events
The current spec does not include location information (lat/long, GPS quality, etc.) for
passenger_eventsorfare_transactionsrecords. If an AFC or APC system includes location data, then the correct application of TIDES would be to create both apassenger_eventsorfare_transactionrecord and avehicle_locationsrecord.Question 1: Does this still sound right? Or should we add location fields to the
passenger_eventsandfare_transactionsrecords?Question 2: If we leave the fields as they are, do we want to be more explicit about how two records that represent the same event are related to each other.
For example, if I have single APC record that has both passenger counts and a location, I would create both a
passenger_eventsrecord and avehicle_locationsrecord. I want to be able to link those.Option 1: allow and require that the unique identifier for the two records match. So if the
passenger_event_idand thelocation_ping_idare the same, that means the records are for the same event.Option 2: add an optional reference to the a
vehicle_locationsrecord from thepassenger_events andfare_transactionstables.My preference is currently Option 2.
Describe the solution you'd like
Add field
passenger_events.location_ping_idto identify the location of a passenger countAdd field
fare_transactions.location_ping_idto identify the location of a fare transactionDescribe alternatives you've considered
Allow
passenger_events.passenger_event_idandfare_transactions.transaction_idto matchvehicle_locations.location_ping_idand define this to mean that the records are associated with the same event.