Currently service date range is saved without timezone support. Introduce timezone support
Tasks
- Modify the schema in
gtfsdataset to make the service date range values support timezone. Default to date time UTC hour 0.
- In the backfill python function modify the logic to include timezones in UTC. On
service_date_range_start, the hour should be midnight and for service_date_range_end the hour should be 11:59pm. If no timezone exists assume UTC hour 0.
- Assure the feed status update function is being compared in UTC
-- post answered questions --
- Modify the schema to include timezone in
gtfsdataset
- Add timezone to the dataset endpoint (will be included in latest_dataset)
- Display the new service date range and display timezone in UI
Questions
- Do we want to save the timezone in the Feed? or in the dataset [Dataset]
- Do we want to expose the timezone in the API? (Feed endpoint) [yes]
- Should we display the timezone in the UI? [yes]
- In the UI should the dates be displayed in regards to the user's local timezone or the feed's timezone? [feed timezone]
Currently service date range is saved without timezone support. Introduce timezone support
Tasks
gtfsdatasetto make the service date range values support timezone. Default to date time UTC hour 0.service_date_range_start, the hour should be midnight and forservice_date_range_endthe hour should be 11:59pm. If no timezone exists assume UTC hour 0.-- post answered questions --
gtfsdatasetQuestions
- Should we display the timezone in the UI? [yes]