Digital service to publish road, sidewalk and parking status information including closings, lane reductions and reservations. Generates feeds for Waze Connected Cities program.
The system was original written using a Google Calendar as the primary storage of events. It used to be that users would add events first to the Google Calendar, then import them into inRoads.
This is starting to be a bit of a hassle now that we're starting to write automated testing. Also, our users now come to the inRoads web interface to add events, instead of adding them manually to the Google Calendar.
We should modify the system so that the local mysql database of events is the primary storage. Publishing the events to a Google Calendar should be optional.
inghamn
commented
6 years ago
The system was original written using a Google Calendar as the primary storage of events. It used to be that users would add events first to the Google Calendar, then import them into inRoads.
This is starting to be a bit of a hassle now that we're starting to write automated testing. Also, our users now come to the inRoads web interface to add events, instead of adding them manually to the Google Calendar.
We should modify the system so that the local mysql database of events is the primary storage. Publishing the events to a Google Calendar should be optional.