Misalignment between node and routed corridor

[Nate-Wessel]

From this comment, it can be seen that a node and a corresponding routed corridor in at least one case do not quite align spatially.

Here is a similar query to the one shown in that comment:
https://trans-bdit.intra.prod-toronto.ca/tt-request-backend/aggregate-travel-times/30414902/30415730/12/17/2025-01-01/2025-01-04/true/1234567

Not a huuuuuge deal, bu I'd like to understand why this is happening. Which underlying dataset is to blame?

[chmnata]

What layer is it querying from? here.routing_nodes and here.routing_streets?

[Nate-Wessel]

Here's the relevant code for the node location: https://github.com/CityofToronto/bdit_tt_request_app/blob/deploy/backend/app/nodes/nearby/here.py

Geometry is pulled from congestion.network_nodes which has perhaps become a bit out of sync with the geometries in here.routing_nodes_23_4?

[chmnata]

Yea totttttttttttally possible, In this map version change (like last year), there were cases where they kept link_dir and node_id the same but the spatial definition changed. My process of updating nodes only drops old ones and insert new node_id, I did not update the geometry of node_id that did not change in between versions. Quick fix would be to pull geometry form routing_nodes_23_4