Kai Krueger wrote:
lsces wrote
The problem is more fundamental than just bad routes, but I suspect Locus
is part of the problem as all 4 routers have the same problem. Routing
instructions through any junction with link_xxx gives a 'straight on'
rather than advising to take the slip road. None of the posts to the
relevant list have been answred!
OK, this goes so much beyond the change of a few controls on the website, or
any website UI design. It really should be an entirely different topic, as
this has nothing to do with usability, but goes at the hart of the core
data-model and its applicability to turn-by-turn navigation.
It is a new topic?
That's why I started a new thread ... but this is a slight sideline off the
usability problem of the map itself on mobile devices, so changed the subject.
It is all bundled with mobile use of the map data though.
lsces wrote
While the generated instructions give better information, the lack of
'lane' information is the follow on that is also important. A standard for
this interchange would also help ...
There are proposals for lane tagging lanes
"http://wiki.openstreetmap.org/wiki/Lane"; and
"http://wiki.openstreetmap.org/wiki/Key:turn";. There are even mobile apps
that already use this information where available to provide lane assist.
MapFactor Free being one of them
(http://forum.mapfactor.com/discussion/435/how-to-make-turn-lanes-in-osm-appear-in-mapfactor-free/p1
), I think OSMAnd also supports this. The problem is that there are so far
only few roads mapped with this information
I was rush this on the move ...
The interchange *I* was talking about was the level above, and related to how a
routing engine presents the list of directions that go with a track. The slip
road for a roundabout gets described several ways between the different engines,
and none is ideal for generating the correct basic move instructions. THEN you
add improved instructions by including the appropriate lane and other road
layout details? Currently I'm getting 'straight on' for the slip road when at
the very least it should be 'take the slip road'? If I'm not careful I've passed
the slip road before I get the 'take the first exit' !
But as with any tagging schema, it is really up to the mappers and data
users to come up with good proposals that work for both and standardize
them.
I am hoping that eventually routing will become part of the main site, to
help guide and improve the whole routing situation and incentivize mappers
to really map the necessary information in a way that is processable by a
routing engine.
I have come to the conclusion that while it would perhaps be nice to have a
routing engine accessible from the map, there is even more reason to have a
number of routers each with their own optimised way of working. Once one gets to
routing, one size will never fit all, and may well be very much location driven.
The four routing engines I'm currently comparing all give different advantages
and disadvantages ... as well as quite regularly different routes for the same
journey. Which is why I'm looking into running my own engine which I can tailor
to my preferred 'short cuts' ...
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
_______________________________________________
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk
