[Script] Highlights for Segments & Landmarks - v1.5 Nov 16

The place to get information and ask questions about everything to do with properly and successfully editing the Waze Map.

Use this forum for all general editing questions, and the sub-forums for specific types of Waze Map Editor features.

Moderators: Unholy, bextein

Re: [Script] Highlights for Segments & Landmarks - v1.4.2 Oc

Postby skbun » Thu Nov 01, 2012 12:41 am

I'm seeing an interesting bug that seems pretty predictable to reproduce. It's in the 'Average speed for segment' section dealing with nodes, and it looks like this:

If I touch any given segment, and then click 'Save' in WME, any segment which I had changed comes up with a wacky speed result. It doesn't matter whether I have any node (or the node in question) highlighted when I do click save; this result persists until I reload the page.

Before saving:
Average speed for segment
A->B: 96km/h (59.7mph)
B->A: 114km/h (70.8mph)
Average speed for segment
A->B: 9684km/h (6017.4mph)
B->A: 11449km/h (7114.1mph)

I can return sanity to the 'average speed' by reloading the editor in my browser.

Whatever is going on here, it seems to be an issue that 'WME Extended Tools' shares, in its 'Segment list', when Fwd and Rev speed are shown as columns.

I also recognize that this could be a problem with the server backend giving an oddball result, which it to say that we can't do anything about it. Thought I'd mention it, anyway.
Image

AM in SW Shasta, NW Tehama, Central Trinity Counties, CA; Mt Rainier Nat'l Park, WA
skbun
 
Posts: 425
Joined: Sun May 06, 2012 12:27 am
Location: Seattle/Tacoma WA
Has thanked: 27 times
Been thanked: 48 times

Re: Script to add Highlights for Segments & Landmarks - v1.4

Postby skbun » Wed Oct 31, 2012 5:45 am

Timbones wrote:Okay, I really think I've got it now. Tested in Firefox, Chrome and Tampermonkey.

v1.4.2 - http://userscripts.org/scripts/show/141050


This is a fantastic tool, thank you! I've spent time now cleaning up reverse connectivity and u-turns. I wonder, as a question of a future feature...is it possible to do a quicker 'scan' of visible segments, like we do for 'recently edited', or 'author', or whatnot, where 'If at least one bad node is seen in a segment, the node or segment is highlighted in a color'?

We don't need to know that any given segment has '25 reverse connectivity instances', for a sweep like that, but only that 'there is at least one'. I have a feeling a scan like this might murder the script or the editing server, but oh BOY would it save time identifying and squashing these problems!

(Of course, we can still keep the particular highlighting for one you do one single segment, to fix the actual segments one at a time! But this makes them easier to find first, if possible to do.)
Image

AM in SW Shasta, NW Tehama, Central Trinity Counties, CA; Mt Rainier Nat'l Park, WA
skbun
 
Posts: 425
Joined: Sun May 06, 2012 12:27 am
Location: Seattle/Tacoma WA
Has thanked: 27 times
Been thanked: 48 times

Suggestion to clarify 'Filter by City' selection

Postby skbun » Mon Oct 22, 2012 7:42 am

Hi all. Please consider the following Permalink for an example:

https://www.waze.com/editor/?zoom=5&lat ... TTTFTTTTFT

You will notice, if using WME Colour Highlights 1.3 in this location, that you will see TWO 'Federal Way's. The behind the scenes reason for this isn't important, but it does illustrate a problem that can make this selection tool a little difficult to use.

The real reason you see two of this identical city is because there's an (erroneous but present) other state incorrectly entered in a node near here.

Therefore, I'd like to propose for situations like this that the 'GetCity' filter dropdown display like this, when listing nearby cities:

Current:
Federal Way
Federal Way
Lakeland North
Washington

Proposed:
Federal Way, Alabama, United States
Federal Way, Washington, United States
Lakeland North, Washington, United States
(No City), Washington, United States

I know from trial and error that the 'Current' list actually means the proposed list, but it's kind of a pain to figure that out by trial and error. So I guess what I'm asking is, can

function updateCityList()

be made a little smarter on the display side, so that it can display more complete listing (thus better meaning) while identifying problems?

(I am aware that there's a beta for this tool that I don't have access to, so I don't know if this has already been discussed there!)
Image

AM in SW Shasta, NW Tehama, Central Trinity Counties, CA; Mt Rainier Nat'l Park, WA
skbun
 
Posts: 425
Joined: Sun May 06, 2012 12:27 am
Location: Seattle/Tacoma WA
Has thanked: 27 times
Been thanked: 48 times

Re: [Script] Highlights for Segments & Landmarks - v1.5 Nov

Postby skapur1 » Sun Feb 10, 2013 2:55 am

CrackedLCD wrote:
Timbones wrote:And it's not even specific to the JNF script - any editor can use QW on every junction node they see with red arrows, blindly allowing all turns without adding value to the map and destroying any information that may have been there.

Displaying 'measles' to every road just presented another excuse to 'fix' junctions that didn't need fixing.


This line of thinking may be appropriate for where you live, but in my part of the US, minor roads on Waze are often very heavily travelled despite not qualifying for primary or minor/major highway status. And in suburban areas, we don't have one way streets or, for that matter, much in the way of turn restrictions, so blindly allowing turns and fixing revcons are actually not that harmful for 99% of the area that I cover.


I agree but only for residential areas.

In rural and suburban US residential areas one way streets and turn restrictions are extremely rare. They are other mapping sources/satellite images that can be scanned to see if there are any such turn restrictions or one way streets in an area and if there are none, but every intersection in Waze has them, then Waze is grossly incorrect and may need some "blind" correction.

It is better to remove them to improve routing for 99% of the routes then to leave them be so that only 1% of the routes are correct. A driver who should always obey posted signs and not follow Waze blindly.

In suburban and rural US one way roads or turn restrictions are usually for parking lots, drive thrus, split roads and private roads leading to building entrances (e.g. schools, hotels, office buildinngs, shopping malls etc.).

Urban areas and even rural towns are completely different and do have many one way roads and loads of turn restrictions. This is one of the reasons a lot of people like to live in the 'burbs.
Image
skapur1
 
Posts: 81
Joined: Sat Oct 06, 2012 2:08 pm
Has thanked: 16 times
Been thanked: 6 times

Re: [Script] Highlights for Segments & Landmarks - v1.4.2 Oc

Postby rotus8 » Mon Nov 05, 2012 4:18 pm

Works for me in Firefox/Greasemonkey.
rotus8
 
Posts: 219
Joined: Thu Feb 02, 2012 1:01 am
Location: La Honda, CA
Has thanked: 0 time
Been thanked: 6 times

Re: Script to add Highlights for Segments & Landmarks - v1.2

Postby rotus8 » Mon Sep 10, 2012 8:23 pm

How about highlighting unnecessary nodes: a node between only two segments, with the same street and city name.

Loving this script! Thanks.

Edit: Oops, just went back and read all posts in the thread and this suggestion has already been requested (and rejected).
rotus8
 
Posts: 219
Joined: Thu Feb 02, 2012 1:01 am
Location: La Honda, CA
Has thanked: 0 time
Been thanked: 6 times

Re: Script to add Highlights for Segments & Landmarks - v1.2

Postby rotus8 » Fri Sep 07, 2012 6:07 pm

Thank you, thank you for this script. I don't know why I never read this thread before, but I installed the script and it is fantastic. I have been going back over some areas I thought were in good shape, and keep finding unterminated roads, unknown direction, and one-way cul-de-sacs I missed, and have been able to find some city xxx(2) I have been looking for. Excellent.
rotus8
 
Posts: 219
Joined: Thu Feb 02, 2012 1:01 am
Location: La Honda, CA
Has thanked: 0 time
Been thanked: 6 times

Re: [Script] Highlights for Segments & Landmarks - v1.5 Nov

Postby rottielover » Tue Dec 11, 2012 5:00 pm

fvwazing wrote:As for reconnecting segments: I made it a habit to move the node a bit, then deselect, then select it again and drag it back. Didn't know it can be done in one move ;-)

And please - configure your PC to show a extra-BIG mousecursor next time. And move it slower.


I've found you can usually do it all in one move, but I have run into some segments and nodes on a "case by case" basis that required "fiddling" with the editor to get them right. I had a loop road just a min ago that I ended up having to completely disconnect all segments, save, then reconnect to get this thing to save properly. Most of the time you can do it all in a few steps then save.

Good point on the mouse cursor, the speed is slightly increased due to the video encoding. I'll make it giant size next time ;)
rottielover
Area Manager
Area Manager
 
Posts: 261
Joined: Sat Oct 06, 2012 2:14 am
Location: St. Louis, MO
Has thanked: 14 times
Been thanked: 19 times

Re: [Script] Highlights for Segments & Landmarks - v1.5 Nov

Postby rottielover » Tue Dec 11, 2012 4:57 pm

BlazeTool wrote:Only criticism is that you should tell users to check existing turn restrictions before doing a QW or disconnect/reconnect. You mention double checking when you are finished, but they might not know what restrictions they need to put back in without checking existing restrictions before modifying.


I felt it was a bit redundant to keep saying "check, check, check". Plus I've found plenty of nodes that had incorrect turn restrictions already set (by fixing the revcon or uturn you end up fixing improper turn restrictions sometimes). Remember this video is targeted to more "advanced" map editor's (AM's and above).

However, I'll add some overlay text via YouTube to put a reminder in .
Last edited by rottielover on Tue Dec 11, 2012 5:00 pm, edited 1 time in total.
rottielover
Area Manager
Area Manager
 
Posts: 261
Joined: Sat Oct 06, 2012 2:14 am
Location: St. Louis, MO
Has thanked: 14 times
Been thanked: 19 times

Re: [Script] Highlights for Segments & Landmarks - v1.5 Nov

Postby rottielover » Tue Dec 11, 2012 1:18 pm

I didn't see any video's on youtube about how to fix U-Turn and RevCon nodes (using the highlight script to find them).

I tried my hand at creating one : http://youtu.be/IFNXGQjA4kc

I had some trouble with the volume. Let me know what you think.
rottielover
Area Manager
Area Manager
 
Posts: 261
Joined: Sat Oct 06, 2012 2:14 am
Location: St. Louis, MO
Has thanked: 14 times
Been thanked: 19 times

PreviousNext

Return to Waze Map Editor

Who is online

Users browsing this forum: Google [Bot]