Raphael Dumas

Results 186 comments of Raphael Dumas

Let's see if this works ```sql ALTER TABLE miovision_api.volumes_2018 SET (autovacuum_enabled = TRUE); ALTER TABLE miovision_api.volumes_2019 SET (autovacuum_enabled = TRUE); ALTER TABLE miovision_api.volumes_2020 SET (autovacuum_enabled = TRUE); ALTER TABLE miovision_api.volumes_2021...

Noting that updates to the addresses of the following signs didn't get updated (in the mat view). api_id IN (33956, 33953). I ended up editing the earlier address to be...

So all that was necessary was changing from `__dict__` to `__json__()` to eliminate this ugliness? ![image](https://user-images.githubusercontent.com/10623872/178749370-f060fa2c-de4e-4e62-b6da-8c0bed80d57d.png)

Added the "check the pipeline worked" task to the list. I don't recommend replicating the logic of `broken_readers.py` because it means the table of broken readers needs to be refreshed...

Also new classifications from bike approaches. Also documentation on bike approaches should be explicit there are entrance (7) and exit volumes (8) https://github.com/CityofToronto/bdit_data-sources/blob/master/volumes/miovision/README.md?plain=1#L73-L75

Good check. I'm guessing those other four are already installed as signalized intersections.

CodeFactor is spitting an error for "No exception type(s) specified". If `strptime` spits out a specific exception that should be caught and a separate generic one could also be logged....

It happened ``` *** Reading local file: /etc/airflow/logs/wys_monthly_summary/wys_views/2021-08-02T07:00:00+00:00/1.log [2021-09-02 03:00:14,467] {taskinstance.py:670} INFO - Dependencies all met for [2021-09-02 03:00:14,505] {taskinstance.py:670} INFO - Dependencies all met for [2021-09-02 03:00:14,505] {taskinstance.py:880} INFO...

As part of fixing this, the `wys_views` task defined below which calls the [`wys.refresh_mat_views()` function](https://github.com/CityofToronto/bdit_data-sources/blob/master/wys/api/sql/function-refresh_mat_views.sql) should be broken up so that mobile data doesn't depend on stationary data & vice-versa....

So this part of the SQL (which is joining `locations` so that each mobile installation will have an `api_id` to match with speed data) should account for the sign start_date...