Raphael Dumas

Realize this wasn't introduced in this PR but the below bullets didn't render properly https://github.com/CityofToronto/bdit_data-sources/blob/404501559b3fb7ba9db3e3c9814223ec4706a649/volumes/vds/readme.md?plain=1#L146-L148

Phase 1 can: * exclude bike volumes * include unacceptable gaps (filter out the hour with a missing 15-min bin) * include anomalous gaps (filter out do-not-use, questionable, include valid-*)...

# Open Data views Unfortunately the `open_data` views depend on it (not that they are being actively updated), but this is evidence that elements within it were used for reporting....

`miovision_new.int_time_bin_avg` is also being used by `open_data.ksp_miovision_summary` so am going to migrate it to `miovision_csv` https://github.com/CityofToronto/bdit_data-sources/blob/6d01d093d1696770d87fb6ac584babdf89f1fc90/volumes/miovision/sql/csv_data/materialized-view_intersection_time_bin_avg.sql#L2

Kind of super weird that a bunch of stuff in the `miovision_csv` schema seems to be the old, uncommitted versions, but the `king_pilot` objects depend on `miovision_new`. I kind of...

## `Report_daily` & `report_summary` ```sql -- View: miovision_csv.report_summary DROP VIEW miovision_csv.report_summary; DROP VIEW miovision_csv.report_daily; ALTER VIEW miovision_cursed.report_daily SET SCHEMA miovision_csv; CREATE OR REPLACE VIEW miovision_csv.report_summary AS SELECT report_daily.class_type, report_daily.street_main, report_daily.street_cross,...

##WIP ROLLBACK; BEGIN; DROP VIEW miovision_csv.veh_tod; DROP MATERIALIZED VIEW IF EXISTS miovision_csv.report_volumes_15min_all; DROP MATERIALIZED VIEW miovision_csv.report_volumes_15min; DROP MATERIALIZED VIEW miovision_csv.volumes_15min_by_class; DROP MATERIALIZED VIEW miovision_csv.report_dates_view; ALTER MATERIALIZED VIEW miovision_cursed.report_dates_view SET SCHEMA...

Thinking I should try to do a SQL backup of the two schemas and compare with what's committed to GitHub

Writing this down so it can now be documented, both in the README and maybe the schema comment. They are effectively different data sources, which is why they've been kept...

All of my non-admin users get this error when they login successfully. ### EDIT Figured out the problem: I forgot to add the user to the `jupyterhub` group and also...