I found a couple of bugs when testing a route through a roundabout: take a look at this screenshot. First, the directions say to take the "0th exit" from the roundabout at the point of entry, not exit; second, the map label at the point of entry to the roundabout has a visible HTML tag.

iainhouse -- thanks. That's the workaround I used.PesachZ -- So obvious -- once you point it out. Doesn't have to junction anything, be saved, or even be in ones editing area. Only there to generate an endpoint. Thanks.

Another slightly more time consuming but accurate workaround is to create a new short helper segment, so you can choose where the mid point will be that is passed to livemap. Ensure that midpoint is nearest to the segment you want to start/end on. You can manipulate this segment for the desired result. You don't need to worry about the segment being connected to anything or interfering with results, since the results are drawn strictly from the segments in the live map.

Tim isn't around this week, but I can identify the problem. With Livemap, you can get a route between 2 points which you select on the map. The script doesn't allow you to select discrete points. It takes the segments you have selected and calculates their mid-points: these two points are then passed to Livemap to return a route.

I think that there is some very slight difference in the way the GPS coordinates are calculated in WME and Livemap. This occasionally results in issues like this - where a coordinate passed to Livemap is actually closer to another segment. I find it frequently happens with split carriageway segments which are long and curved.

The general workaround for this is to try and select earlier or later start/end segments on the same route. In this case, my gut tells me that trying this segment as the destination might work better - assuming I've followed the route you're trying to test.

I am having a problem with a route -- route checker seems to be picking the wrong destination point/segment. Perhaps this is because another segment crosses at the midpoint of the selected segment. Is it possible to drag the destination point a little further along the segment?

Timbones wrote:There's still the issue that when you have a route showing, you cannot deselect one of the segments to select another. You can only click to deselect all of them, and start again. This is because the route layer is now shown on top of the segment selection layer, and I can't figure out a work around.

Any reason why the obvious solution - adding a "pointer-events:none" style to the layer container div - isn't suitable? A quick play around with this version of the script suggests there's no need for it to capture any mouse events on the route layer, so letting them all fall through to the underlying WME layers seems safe enough.

There's still the issue that when you have a route showing, you cannot deselect one of the segments to select another. You can only click to deselect all of them, and start again. This is because the route layer is now shown on top of the segment selection layer, and I can't figure out a work around.