Updating Bluetooth Segments: process should use routing now

[radumas]

After matching intersections to Bluetooth detector locations, should be using routing in the centreline network rather than drawing a straight line between the two points as outlined here.

• [x] Identify routes which are missing segments.
• [ ] Update process for drawing in segments using routing on centreline
• [ ] Update documentation on how to use
• [ ] Draw segments for the new ~Bloor~ Routes

[radumas]

Natalie has explained how to use routing https://github.com/CityofToronto/bdit_data-sources/issues/234 should just update the documentation to use that process. Some commentary on that issue and the two linked issues might also help understand what is up with these inconsistencies.

[radumas]

I think the only segment that needs to be drawn will be the new Bloor routes.

• [x] Check that all the "missing segments" in mohan.missing_segments are actually drawn in natalie.bluetooth_routed see #234

[webgisgeek]

I think the only segment that needs to be drawn will be the new Bloor routes.

• [x] Check that all the "missing segments" in mohan.missing_segments are actually drawn in natalie.bluetooth_routed see #234

All the mohan.missing_segments are actually drawn in natalie.bluetooth_routed.

[radumas]

Thanks for checking!

I just updated the first comment text to clarify we want to draw all newly created segments.

Plopping the image of those here too

[chmnata]

It is now using routing!