<div>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!<br/>
<br/>
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 ...<br/>
<br/>
<font color="#888888"><font color="#888888">Sent from my android device.</font></font><br/><br/>-----Original Message-----<br/>From: Tom MacWright <tom@macwright.org><br/>To: Lester Caine <lester@lsces.co.uk><br/>Cc: openstreetmap <talk@openstreetmap.org><br/>Sent: Sun, 21 Jul 2013 17:19<br/>Subject: Re: [OSM-talk] New technology ...<br/><br/></div><div dir="ltr">Hi Lester,<div><br></div><div>The most productive way to lead to better routing on OSM is to find 'bad' routes, generate permalinks on OSRM or your favorite tool, and post bug reports, including what the desired route would be and what's incorrect about the incorrect route. For OSRM in particular the bug tracker is here: <a href="https://github.com/DennisOSRM/Project-OSRM/issues">https://github.com/DennisOSRM/Project-OSRM/issues</a> and you can click 'Generate Link' on the testing instance: <a href="http://map.project-osrm.org/">http://map.project-osrm.org/</a> in order to send a specific route around.</div>
<div><br></div><div>Tom</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jul 21, 2013 at 12:02 PM, Lester Caine <span dir="ltr"><<a href="mailto:lester@lsces.co.uk" target="_blank">lester@lsces.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">Tom MacWright wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey Lester,<br>
<br>
I agree entirely - thus far we aren't focusing on the mobile version of the<br>
site. It's never been very polished, and recent changes aren't focused on<br>
improving it significantly.<br>
<br>
As far as why, it's pretty simple - changes to the site are extremely<br>
time-intensive because of its myriad uses and the necessity of having a<br>
community process. That is, we've needed to focus on specific parts of the site<br>
because, even if we agree that many things need to be done, we only have enough<br>
designers & developers to implement one or two things a month.<br>
</blockquote></div>
And some of us are hampered by the choose of tools that was made previously!<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think there are two solid ways forward here:<br>
<br>
First, which is admittedly less likely, is if anyone wants to adopt the task of<br>
maintaining, testing, and improving the mobile site, and pushing those changes<br>
through.<br>
</blockquote></div>
There are a few options as a good starting point, but your 'third' point is probably accurate here.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Second, which is more doable but more likely to get over-communicated, is for<br>
someone to write a simple page pointing to good mobile options. For instance,<br>
users of GPS units should easily find out about Garmin extracts, smartphone<br>
users should easily find editors that work on their phone or apps that use<br>
OpenStreetMap data.<br>
</blockquote>
</div><a href="http://lsces.co.uk/wiki/Mobile+Computing" target="_blank">http://lsces.co.uk/wiki/<u></u>Mobile+Computing</a> :)<br>
But I'm getting bogged down by what does not work in each of the options and I don't have time to try the options that are missing. I need to switch from Locus to one of the other options just to establish where the identified safety issues actually arise from! If you can't trust a configuration then it's unusable, and that is part of the current problem.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Independent OSM-based tools do a better job at the very specific use-cases<br>
people have on mobile - whereas the website focuses strongly on one use case,<br>
editing, and has no smartphone-compatible editors.<br>
</blockquote></div>
Adding data via the tablet is easier than actually using it on the tablet ...<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
(To tackle the inevitable points of argument that follow that: yes, there are<br>
things that do this, but we need to do better. No, there's no committee to<br>
decide and yes the best way to do it is to do it, even if it's very low-tech.)<br>
</blockquote></div>
We need well documented user reports on the available tools rather than just 'choose the option that works for you' ... I have yet to find a routing package that gives SAFE directions on UK motorways! This was the whole reason for my closer investigation.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
Tom<br>
<br>
On Sun, Jul 21, 2013 at 11:26 AM, Lester Caine <<a href="mailto:lester@lsces.co.uk" target="_blank">lester@lsces.co.uk</a><br></div><div><div class="h5">
<mailto:<a href="mailto:lester@lsces.co.uk" target="_blank">lester@lsces.co.uk</a>>> wrote:<br>
<br>
With the arrival of a 'new' set of controls, and the discussion on front<br>
page, I feel that it IS necessary to open this discussion a little wider.<br>
Having been using the new interface on mobile devices I find it much less<br>
usable than the older set-up. But that is not to say that the old one was<br>
actually usable! There is a need for a different map interface that works<br>
better with mobile devices. Even the routing demos have mixed results on<br>
tablets and mobile phones. I've been working on my own 'front end' simply to<br>
provide one that I can tailor for the devices I am using. The old N900 used<br>
to work well, but the newer devices are difficult to use 'on the go'. As an<br>
example, the old TomTom sat nav was easy to use while driving, but the<br>
current replacements I've tried to use with the Galaxy4 can be dangerous at<br>
times as they wander off doing their own thing, and you have to stop to get<br>
back to a state where you can continue following the route.<br>
<br>
It's obvious that the new map interface is not designed for mobile devices,<br>
so where should we discuss that development and how it would fit in with an<br>
improved front end. It's not just a matter of directing to 'a map' but more<br>
important is directing to safe options for those of us who ARE using the<br>
tools every day. The current options are both difficult to find, and have<br>
clear information on how safe they are when using them live! Disclaimers of<br>
accepting no responsibility may cover any legal liability, but essentially<br>
say 'here is a tool - but you should never use it!'<br>
<br>
And discussion on a more open platform would also be appreciated rather than<br>
on development platforms that we do not subscribe to because we use<br>
different development tools!<br>
</div></div></blockquote><div class="HOEnZb"><div class="h5">
<br>
-- <br>
Lester Caine - G8HFL<br>
-----------------------------<br>
Contact - <a href="http://lsces.co.uk/wiki/?page=contact" target="_blank">http://lsces.co.uk/wiki/?page=<u></u>contact</a><br>
L.S.Caine Electronic Services - <a href="http://lsces.co.uk" target="_blank">http://lsces.co.uk</a><br>
EnquirySolve - <a href="http://enquirysolve.com/" target="_blank">http://enquirysolve.com/</a><br>
Model Engineers Digital Workshop - <a href="http://medw.co.uk" target="_blank">http://medw.co.uk</a><br>
Rainbow Digital Media - <a href="http://rainbowdigitalmedia.co.uk" target="_blank">http://rainbowdigitalmedia.co.<u></u>uk</a><br>
<br>
______________________________<u></u>_________________<br>
talk mailing list<br>
<a href="mailto:talk@openstreetmap.org" target="_blank">talk@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/talk" target="_blank">http://lists.openstreetmap.<u></u>org/listinfo/talk</a><br>
</div></div></blockquote></div><br></div>