search

aerostitch / testnavit

0 stars 0 forks source link

No route found around the town of Midpines #270

Open aerostitch opened 9 years ago

aerostitch commented 9 years ago

Issue migrated from trac ticket # 1296

component: core | priority: major

2015-04-13 12:42:05: @pgrandin created the issue

Navit was unable to find a round along the CA 140 near the town of Midpines.

Past a certain area, the route was found.

aerostitch commented 9 years ago

2015-04-13 12:45:40: @pgrandin commented

Related QA test

aerostitch commented 9 years ago

2015-04-13 12:45:40: @pgrandin

aerostitch commented 9 years ago

2015-04-13 17:50:18: @pgrandin commented

Jan suggested that this issue could be caused by 4537

Reverting the change in a github branch seems to fix the issue indeed :

This has been tested in build 245 and a route was found.

[[Image(Screen Shot 2015-04-13 at 5.54.49 PM.png)]]

aerostitch commented 9 years ago

2015-04-13 17:50:18: @pgrandin

aerostitch commented 9 years ago

2015-04-13 17:51:31: @pgrandin uploaded file Screen Shot 2015-04-13 at 5.54.49 PM.png (129.5 KiB)

Screen Shot 2015-04-13 at 5.54.49 PM.png

aerostitch commented 9 years ago

2015-04-15 10:50:10: tryagain commented

Hi!

I suppose, deeper vehicle profiles ("pedantic" one being extreme case) solve the problem with the default map?

Then we had an adaptive solution suggested at http://trac.navit-project.org/ticket/456#comment:70.

Another idea would be to use additional tags to distinguish important roads, maybe some ref mask (together with relations processing) could be usable to distinguish road networks like E-roads in Europe.

Some per-country maptool rules could be usable too.

I'm afraid that simply reverting 4537 would make our tiles too huge.

Does anybody have actual osm ids of ways missing from route graph with default maptool?