Natalie

Recreated `here.routing_streets_21_1`, the pond road is still missing. It is also not a part of `here_gis.traffic_streets_21_1`. Checked `here_gis.streets_att_21_1` and it is a func_class 5 road, not sure why this is...

Turns out I did not do something wrong in `here.routing_streets_21_1`, just forgot to add a suffix to here.routing_nodes`, no need to rematch.

### Summary one For the old links with no match in sharedstreet lookup, I did a spatial join with endcap=flat buffers ranging from 5 - 30m. These are the 60...

Did another round of spatial joins + manual updates of visible gaps in the network. Investigated missing segment_id, and dealt with them accordingly. Below is a map of all 38...

Got rid of double matched link_dir for gardiner and lakeshore with an sql (hyperlink later). Will now do a final check on complete segments_v6 network.

Version 6 of congestion network is finally ready for review @aharpalaniTO ! It is conflated with a combination of sharedstreets matcher and spatial join, process found in `sql/conflate_segments_21_1.sql`. Completed several...

> > > Total number of links, by functional class, for the last 3 versions > Versions 1 2 3 4 5 > 18_3 605 1166 3542 26894 145376 >...

I am here a year later to investigate the mystery of Pond Road. **We do indeed have data in `here.ta` for the Pond Road.** :meow_dio: The reason why the Pond...

Notes of changing table names: `bluetooth.route_points` (which doesn't exist in mohan and bluetooth schema), BUT `mohan.route` does exist, and instead of `bluetooth.route_point_status_history` we have `bluetooth.route_status_history` so I'm assuming `mohan.route` =...

Seems like `mohan.routes` is supposed to be a table that has all the information of each route (or segment). This table is originally called bluetooth.segments in the bluetooth schema, with...