That is indeed a bug, thanks.
Fixed in v1.11, and also made working in Firefox. Chrome version will follow shortly.
1.11 seems to work much better, both the oilyfork version and the auto-updated Chrome web store version.
Neither allows deselecting one of the pair of segments (I sometime would do that to move one of the ends of the route, to trouble shoot a problem), but I can live with out that feature. The new options more than compensate.
Thank you for your excellent contribution(s) to improving the editing experience.
Thanks for the feedback. I think this issue is caused by the route layer now being on top of all other layers, including the select-a-segment layer. Iāll see if I can refine that a little moreā¦
^^^ That would be nice. I still have to use the alt shift R quick refresh, before i can select other segments to try different route info.
Or you coudl just turn off the route checker layer briefly.
Good tip! Layer can be quickly toggled with Shift+t.
What are the chances of adding the option for fastest / shortest?? 
BUG report *2
- This script is now conflicting with Toolbox, when both are running, Iāve isolated it to this script. The Fancy PL links to PM the last editor or creator of a segment in the left pane do not show. The link to display the list of area manager which should display below the segment history info also doesnāt show.
- When this script is running (with TB I havenāt tested it without TB) there is a vertical scroll bar added to the map frame which allows a scroll of about 1/4 inch more of the screen (on a 720p screen in chrome)
If you need more data please tell me what you are looking for to debug if you are not able to reproduce.
PZ, on bug #2, for some reason lately TBās minimap sometimes drops below the visible frame. Even if it is hidden, this causes Chrome to think that it needs to allow you to scroll down.
Just enable the minimap and drag it up. I think it only happened once, during a recent update, so you can do this once and forget about it.
This bug2 is not the TB minimap bug, I donāt get it with just TB, only when route chcker is also enabled. Iām aware of the mini map bug, and I even tested with mini map enabled and in middle of screen.
Sent using Tapatalk for Android 4.4.2
New Version v1.12 - on Greasemonkey and Chrome Web Store (soon)
- Fixed bug with PM link by Toolbox
- Added fastest/shortest option
- Display TOLL marker for routes that use toll road
- Show distance (km) and time for route (miles in tooltip)
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.
1 Like
Great job!!!
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.
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?
The route is like this:
https://www.waze.com/livemap?lon=-75.91688921403907&lat=42.11145257510245&from_lon=-75.93815692677028&from_lat=42.115937110173334&to_lon=-75.90877001329581&to_lat=42.114329862302085
But it should be like this:
Thanks for this really amazing script. It has allowed me to find all kinds of things that need to be fixed.
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.
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.
Sent using Tapatalk for Android 4.4.2
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.
awesome!!
https://www.waze.com/editor/?env=usa&lon=-83.53676&lat=42.65770&layers=0&zoom=3&segments=63822317,23767319
select āshortest routeā with the checkbox for āAvoid Dirt Trailsā left unchecked, and then show routes. The shortest route is definitely not returned.
New version uploaded to Greasyfork; Chrome version will be available in a few days.
- Show āexit leftā instructions (thanks FZ69617)
- Show instruction text on the map (primary route only)
- Follow rules for navigation instructions for unnamed segments
- Donāt show ācontinueā instructions for name change
- Refactored code and general improvements
Feedback and bug reports please.
:ugeek: