Routing bug - node network

anyways-open / cycling-backend

This is the backend for the cycling routeplanners of Anyways.

https://genk.anyways.eu/

MIT License

0 stars 0 forks source link

Routing bug - node network #13

Closed xivk closed 5 years ago

xivk commented 5 years ago

We need to:

[ ] Verify that only the node networks are in fact used and not the other networks.
[ ] Relax the prefer factor until these routes start making more sense.

xivk commented 5 years ago

These two narrow down the issue nicely:

7.21km

https://genk.anyways.eu/staging/?loc1=4.126588,51.189253&loc2=4.069880,51.211151&zoom=13.19&lat=51.207082&lng=4.125155&p=network&

This one:

5.38km

https://genk.anyways.eu/staging/?loc1=4.126251,51.190189&loc2=4.069880,51.211151&zoom=12.70&lat=51.198023&lng=4.118711&p=network&

Both seem to be taking the cycling network, one of them probably is on a different network or there is some unknown bug.

he-ulg commented 5 years ago

Screenshot (67)

Upon reporting the above issue by Wim (going through Antwerp), I changed the origin to BXL and tested every 3 existing route planning modes. For 2 of them, I noticed a persistence for routing alongside the border with France:

Screenshot (69) Screenshot (70)

Though I got the most strange routing result when I selected the fastest route mode as you can see below :

Screenshot (71)