API, Map, RDS Improvements
Pre-release
This release contains API, Map, RDS, and Power BI features, and has a targeted release of the end of August 2019 if we can gather the right funding. We have some funding now from Centennial, CO and InterDev, and are looking for about $5,000 more to finish.
Some funding has come from Amazon. We are looking to other cities and companies for help. Work is being done by Slingshot and Louisville government project managing with input from the community.
Here is what is new in this release (updated May 2019):
An API that you can use to query the database and return data as JSON:
- jam details endpoint, with filters
- see endpoints 1a and 1b in this document for details
- other API calls coming in future releases
A browser map that shows current and historic Waze data:
- Built on Leaflet, uses the API
- can select date and time in the past
- shows jam information
- alerts and filters coming in future releases
Updates to the relational database and schema including:
- indexes for query speed improvements
- a read-only database user you can share with people doing analysis
- a type_id in the alerts table for better speed with type queries
- field enrichment for better analysis
- direction (N/S and E/W) field for jams
- specify your local timezone when installing - new DB fields in local time
Improved Power BI Traffic Study Tool:
- includes direction (N/S/E/W) of analysis
- includes each intersection analysis along a corridor
- adds interactive map view
- Existing tool is here which has this functionality
Track progress and see details here:
https://github.com/LouisvilleMetro/WazeCCPProcessor/issues?q=is%3Aissue+is%3Aopen+label%3Av3.0
Work being done on these branches:
https://github.com/LouisvilleMetro/WazeCCPProcessor/tree/schema/refactoring-1
https://github.com/igNew/WazeCCPProcessor/tree/feature/basic-api
We are looking for funding to help our developer finish this release, so please contact us if you are willing to help.