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.
I’ll fix the HTML tag, but I feel that the entry point is the correct place to put it as that is where the driver hears the instruction.
0th exit is an error in the map - you must not have two exits from the same node on the roundabout. I suggest the ‘inner roadway’ should connect to ‘Massachusetts Ave’ a few feet before/after the roundabout, and not to the roundabout itself.
I’ll tell DDOT that they made an error designing Dupont Circle. :lol: Which I’m sure they will enter in volume 37 of their compendium of poorly designed streets.
Or you could fix it by having a single no name segment exit that node, and then fork into the two roads. So the RA sees it as one numbered exit, and the prompt will still carry the same names do to the no name segment properties.
When Chrome installed a recent WME Route Checker update, I got a message saying that the new version needed new permissions - I believe it said to write to all websites visited.
Not sure which version it was updating from/to. I think the target was 1.15, that’s what I have installed now.
Any comment on what caused this? I didn’t see it mentioned in any recent discussion.
In wme beta when i select 3 segments for deletion only the first selected will be deleted and the save button stay greyed out, for n>=3 only n-2 segments are deleted
I don’t know if it’s important
Max
If routes cannot be generated with LiveMap due to a problem on Waze’s end, Route Checker keeps trying indefinitely. It never stops, and doesn’t give the user any feedback.
Can a time to live or similar be put in place with a message?
This script has never worked in beta, and it is not possible because secure browsers prevent cross-site scripting. A link is provided to show the route in the Livemap instead.
Can you give a specific example? It was working for me when I tested some routes around Gateshead…
It is possible that either the restriction is not correct, or there’s a [gasp] bug in the routing server.