Natalie

The earliest data backfilled for (1514906,1515280,1514986,1514879,1514850,1515251) is 2022-05-17, even though some of them has a `date_active` of Aug 2018 and Aug 2020.

`reportFields= [LOCATION_REF, DATE, EPOCH, LENGTH, FREEFLOW, SPDLIMIT, COUNT, MEAN, HARMONIC_MEAN, VDT, PROBE_COUNT, STDDEV, MIN, MAX, CONFIDENCE, PERCENTILES]`

The new columns only applied for path data... and not probe_mix. The selection for those columns does not show up for probe_mix requests.

The oldest date we can backfill is 2018-01-01, the oldest data we have currently in the database is 2017 Sept. So if we were to backfill we will only loss...

You could try `bluetooth.routes_temp`, and `bluetooth.readers_history_corrected_temp` and possibly `bluetooth.reader_status_history_temp`

Seems like centreline_intersection_point has more points. ``` -- returns 7753 select intersection_id from gis_core.centreline_intersection_point where version_Date = '2024-02-29' except select intersection_id from gis_core.intersection where version_Date = '2024-02-29' ``` Looking at...

Re discussion with @gabrielwol today, I summarized issues Gabe identified so I make sure I'm understanding this correctly. Identified issues: 1) Gaps are not in daily chunk by spans over...

@tankedman can you create a new script on top of the original miovision pulling script so we run a range of date (start_date, end_date) that: - log the days that...

Thanks for putting together the table, @tankedman Looking at the log file from your processes, there are 484 counts of `warning! you are trying to insert duplicate data` throughout different...

Added in anomalous_ranges uid: 897