Started by Menion, August 03, 2011, 15:53:48
0 Members and 1 Guest are viewing this topic.
<rte> <rtept lat="51.17500" lon="4.39630"></rtept> <rtept lat="51.17600" lon="4.39630"></rtept> <rtept lat="51.17700" lon="4.39630"> <desc>Head south on Perckhoevelaan, 0.1 km</desc> <extensions> <turn-angle>269.0</turn-angle> </extensions> </rtept> <rtept lat="51.17600" lon="4.39630"></rtept> ...
Quote from: svartbjornphoneguy100:---------------- what Menion explains here, works incredibly well! I just tried it again this morning when driving car to work. I took an alternative road one place and the blue arrow showed up with the great guiding line pointing to where the closest point was at the CloudMade route (continuously updating). When I joined the calculated route again, the blue arrow changed back to the car symbol and the navigation was back on track. Works perfectly!Thanks alot for that menion and thanks for helping so muc svartbjorn.I know exactly what you mean svartbjorn and that is exactly how I thought it would work as it tested it like that - but it didnt. Now in all fairness, it did seem to fail in 'guide reverse', but I will try it again properly today and report back.Also got the new version this morning and am really looking forward to testing it,
Quote from: "menion"In cloudMade data isn't current name of road, so I get this info from decsription of actual navigation point (to be precise - from previous nav point), so if there will be some problem (like you describe), please send me start and end point of track that goes over some problematic place and I'll compute on my phone and fix this text problem.
Quote from: "phoneguy100"using the voice navigation
Quote from: "menion"yes, tap on turn arrow