On 17 Jul 2010, at 12:29 , Marcus Wolschon wrote: >> >> the cloudmade route choose 80degree + 160 degree turn when it was >> possible with nearly exact same length to do 110 degree + 5 degree >> I think something like a exponential cost increase for the angle >> of a turn will result in 90% of the unclear situations > > - From what I saw the links where oneway-streets. > Else it would already have chosen the correct one because > it´s simply the shortest path. >
the rendering at cloudmade is not up to date, now looking at the raw data and satellite image tells another story. http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Portland,+OR&sll=38.203655,-93.251953&sspn=52.089643,80.859375&ie=UTF8&hq=&hnear=Portland,+Multnomah,+Oregon&ll=45.418324,-122.318784&spn=0.002899,0.004935&t=k&z=18 this is a masterpiece of road design. there is no access at all. a trunk where exit is possible in both directions from both directions. But now way to enter the trunk from both sides to go both directions. this can be mapped only with turn restrictions or dual carriage ways. any heuristic will fail for such a bad road design. > >> >> >> >> I haven't done any of this or looked into the code. Mark explained >> a bit in some postings in the mkgmap dev list. just to be clear. >> this is not for the routing itself just for the announcements. >> Don't announce if the angle is small and roads continue with >> similar tags. the routing itself is done by the Garmin device > > What do you mean with "announcement"? > turn by turn instructions are announced at all intersections > _______________________________________________ Routing mailing list [email protected] http://lists.openstreetmap.org/listinfo/routing
