905 Miovision Open Data

[gabrielwol]

What this pull request accomplishes:

Some Miovision Open Data tables ready for discussion/comments.

A 15 minute view, based off of volumes_15min_mvt (TMC table), but extended to have ATR columns for the purpose of covering both TMC and ATR style data requests we currently handle.

• volumes/miovision/sql/open_data/create-function-insert_miovision_open_data_15min.sql
• volumes/miovision/sql/open_data/create-table-miovision_open_data_15min.sql

A monthly summary by intersection. I simplified this somewhat versus our discussions, because I wanted it to be difficult to misinterpret (1 row per intersection per month), and let the 15min view answer detailed questions.

• ...es/miovision/sql/open_data/create-function-insert_miovision_open_data_monthly_summary.sql
• volumes/miovision/sql/open_data/create-table-miovision_open_data_monthly_summary.sql

A new DAG to insert into these tables each month. Scheduled for the 3rd of each month. Runs a sqlcheck to make sure there is data for every day of the month before summarizing. Sends a status message when complete.

• dags/miovision_open_data.py

This was a draft in case we wanted to have a wide TMC view, like https://open.toronto.ca/dataset/traffic-volumes-at-intersections-for-all-modes/. We can delete when we're satisfied with the other approach above.

• volumes/miovision/sql/open_data/create-view-miovision_wide_tmc.sql

Issue(s) this solves:

• #905

What, in particular, needs to reviewed:

• What to do about bicycle volumes (I naively grouped classifications 2,7,10 together for now)
• The grouping of Trucks/Buses (Since streetcars have moved between classifications, I thought it was easiest to group these together...)
• The ATR style columns added to TMC view

What needs to be done by a sysadmin after this PR is merged

Convert all these gwolofs tables to miovision_api schema.