You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Routing between start and end points is done with a shortest path. which is not always what's desired. This for example is meant to stick to the Gardiner, but deviates onto Lakeshore to save a few meters.
Having the ability to snap the middle to the Gardiner with a control point would be great, but would also necessarily add complexity to the API if the query couldn't be decomposed and then pieced back together.
The text was updated successfully, but these errors were encountered:
Routing between start and end points is done with a shortest path. which is not always what's desired. This for example is meant to stick to the Gardiner, but deviates onto Lakeshore to save a few meters.
https://trans-bdit.intra.prod-toronto.ca/tt-request-backend/aggregate-travel-times/30415837/30335200/7/10/2024-02-01/2024-03-09/false/1234567
Having the ability to snap the middle to the Gardiner with a control point would be great, but would also necessarily add complexity to the API if the query couldn't be decomposed and then pieced back together.
The text was updated successfully, but these errors were encountered: