API, Map, RDS Improvements

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.

End-to-end Processor and RDS

An end-to-end processor that takes the JSON files and processes them into a relational data base in AWS.

The code base has been re-written using Terraform.io to be cloud agnostic, though this release focuses on AWS.

The scope is part of this Phase 1 project:
https://github.com/LouisvilleMetro/WazeCCPProcessor/projects/1

And spans these issues/tasks:
https://github.com/LouisvilleMetro/WazeCCPProcessor/issues?q=label%3A%22v2.0+release%22

Notes:
Updates to schema and readme.

Storing Waze JSON Files to Cloud

This release uses Cloud Formation to store JSON files from your Waze CCP data feed to an S3 bucket in AWS.

This is important since it's up to you to save these files, so the sooner you start saving the farther back in time you can do historic analysis later when we get the database up and running.