Opened 15 years ago

Closed 14 years ago

#127 closed defect/bug (fixed)

"unpaved" from osm is wrongly considered "undriveable"

Reported by: hafting Owned by: somebody
Priority: major Milestone: version 0.2.0
Component: core Version:
Severity: Keywords:


Unpaved roads from osm are considered un-driveable. Navit recommended a trip across the sea to the closest paved road. However, there were a much closer unpaved road, a secondary road, no less.

For OSM maps, I recommend: The "highway" type should decide, not the paved/unpaved status. An unpaved secondary road is still a secondary road. Driving on a good gravel road is not a problem, gravel roads are used in places where there is so little traffic that asphalt is considered too expensive. The unpaved status might reduce the estimated speed some, but that's it. I suggest 80% of the speed otherwise associated with the "highway" tag.

Roads of type highway=track are the ones that might not work well for an ordinary car.

Change History (2)

comment:1 Changed 14 years ago by KaZeR

  • Milestone set to version 0.1.0

Are you able to make the relevant change using navit.xml?

comment:2 Changed 14 years ago by KaZeR

  • Resolution set to fixed
  • Status changed from new to closed

Currently, unpaved tracks have a speed of 10 km/h for routing. You can change the value if you wish in navit.xml, the item is named track_unpaved.

Note: See TracTickets for help on using tickets.