Editor Version Dec 19th Official Feedback Thread

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

User ignored Waze's route URs - thank you!!

Postby skbun » Thu Dec 20, 2012 1:19 am

By the way, I just want to take a moment to say to Waze - although there are always things that can improve, the new 'ignored route' UR is a huge plus!

In all of the URs I've looked over, I've almost always found something that makes me say 'Oh, man. Yep. That's just wrong, and that's why the route did that.' The automated UR is finding things that in an ideal world, a user would report, but they don't always.

So, thank you, Waze! :D :!:
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: Editor Version Dec 19th Official Feedback Thread

Postby skbun » Thu Dec 20, 2012 1:16 am

AndyPoms wrote:
shawndoc wrote:You only need to check the marked junction to make sure the turn restrictions are set properly. I'm finding the majority have some sort of mistake.
With this type of automatic error, you need to check further down the route the user(s) did take as another turn (or series of turns) they took could be incorrect, or even segments with the wrong direction.


I've found having solved a couple dozen of these that it's more useful checking the route Waze wanted a user to take, although checking both is valuable.

Checking the user's route will give you a sense for where most people go when they think they know better - and in a situation like this, sometimes they do! And, as the OP said, you can find turn restrictions at the intersection or a bit down the road on the green routes...

Checking Waze's purple route though can take a little more digging, but in my own experience I'm finding that more than 50% - maybe even 75% of the time, there's a problem a short distance away from the intersection (3-5 segments) that explains Waze's choice. Often the UR will only have the first segment or two's instructions in the error...which isn't a HUGE problem; it just means that usually you'll be looking in 'the neighborhood you were pointed into'. In those situations, I've seen things like this in the purple segment directions:

* Neighborhoods Waze wants to go into (to cut off distance), with a 'Dead end' sign that, while they had other ways in and out than the one, clearly they're not meant to be used that way (think 'two track dirt road or other clearly 'not streets'), which I marked as 'parking lot roads'.
* U-turn possibilities that are really just somebody's driveway (I delete those if they're short stubs)
* Streets Waze wants to use marked as two-way but actually one way
* Speed gone to hyperspeed plaid on a segment inside Waze's choice, meaning it's favoring it because of a bad segment

That said, it'd be useful if these URs could show...how to explain...purple routes the same way it's showing the green ones, maybe 3 segments out. Then we can see if Waze is always pointing in one single direction, or if it's just going 'wherever' after that.
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: Editor Version Dec 19th Official Feedback Thread

Postby skbun » Wed Dec 19, 2012 9:35 pm

Just a heads up, all, about the nature of the 'route ignored' URs, as well...

Some of the history for these goes back at LEAST a couple weeks. One UR in Tukwila, WA I solved was Waze showing an ignored route onto a street that I moved/fixed on December 4, because a new road opened. I would guess that once this first round of them is dealt with, new ones will probably use more recent data. Just be careful of what Waze thinks it's routing onto to see if it wasn't already addressed some days/weeks ago.
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: Editor Version Dec 19th Official Feedback Thread

Postby skbun » Wed Dec 19, 2012 8:53 pm

Correct me if I'm wrong, but the only way the 'route ignored' UR in this screen capture below makes any sense would be if Bing is providing a bad lat/long for an address, right?

It's not so much in this case 'See if it's allowed'...but...

Anyway, I just want to get a sense for what other editors think here. Why else would it route to a dead end road?

Permalink: https://www.waze.com/editor/?zoom=7&lat ... TTTFTTTTFT
Attachments
UR.jpg
UR.jpg (239.33 KiB) Viewed 464 times
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: Editor Version Dec 19th Official Feedback Thread

Postby skbun » Wed Dec 19, 2012 8:39 pm

For the 'Most ignore this route' UR...

Can you make it work the same way that 'Turn not allowed' and other URs do, where there is a user selectable checkbox for 'Ignored suggest route' and 'Route most users took' - if not that, at LEAST a color legend for it (in that gray menubar location) so that someone not familiar with this kind of UR will understand what they're looking at?

E.g., capture this essense into it. 'When selecting this problem - you'll notice a purple line representing Waze's suggested route and green lines representing the routes selected by the users + a number of users who selected this route.' Basically, what Webs101 said above.
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: Editor Version Dec 19th Official Feedback Thread

Postby sk2380 » Wed Jan 09, 2013 11:45 pm

jasonh300 wrote:
Nothing has changed in the way that points are calculated. There's just a limit to the number of edits that will give points at one time. This shouldn't have any significant effect on the score of anyone who is editing properly.


Thanks, could you please explain I am getting confused. :o it will be helpful if you could give me some example in terms of edit.

Thanks...
sk2380
CM India

ImageImageImageImageImageImageImageImage
sk2380
 
Posts: 178
Joined: Thu Nov 18, 2010 8:41 pm
Location: India
Has thanked: 42 times
Been thanked: 59 times

Re: Editor Version Dec 19th Official Feedback Thread

Postby sk2380 » Wed Jan 09, 2013 9:51 pm

* We deployed a new limit to massive editing due to misusage of extended tools by some abusers.
This new limit doesn't block you from performing the massive edit (based on your permissions of course) but only 150 edits per save will be granted with points and calculated for ranks.

clarifications:
How do we count edits for points and editing-ranks (those you see in the dashboard)?
we count the number of objects that have been edited within one "Save".
An object can be count only once in 24 hours.

That means that a user who used ET to edit a city containing 1000 segments, then selected again the same city -and had saved again - will be credited for 150 edits only.

What's an object?
segment
node
landmark
camera
update request
map problem
city (create new)
street (create new)


Can somebody please explain me the calculations how the points,edits,bonus candies will be calculated as per the new rule.
thanks in advance!!
sk2380
CM India

ImageImageImageImageImageImageImageImage
sk2380
 
Posts: 178
Joined: Thu Nov 18, 2010 8:41 pm
Location: India
Has thanked: 42 times
Been thanked: 59 times

Editor Version Dec 19th Official Feedback Thread

Postby shirlig » Wed Dec 19, 2012 1:52 pm

Hi guys,

We released today a new version of the Editor:

What's new?


* New problem type: "suggested route frequently ignored": this new problem locates places where many users didn't follow Waze's instructions and therefore we assume that something's wrong there.
When selecting this problem - you'll notice a purple line representing Waze's suggested route and green lines representing the routes selected by the users + a number of users who selected this route.
* improved map problems and UR look
* UK and US now using imperial system in speed cams and archived routes
* Default city in new landmarks based on location
* Roundabout radius is limited to 100 meters.
* We deployed a new limit to massive editing due to misusage of extended tools by some abusers.
This new limit doesn't block you from performing the massive edit (based on your permissions of course) but only 150 edits per save will be granted with points and calculated for ranks.

clarifications:
How do we count edits for points and editing-ranks (those you see in the dashboard)?
we count the number of objects that have been edited within one "Save".
An object can be count only once in 24 hours.

That means that a user who used ET to edit a city containing 1000 segments, then selected again the same city -and had saved again - will be credited for 150 edits only.

What's an object?
segment
node
landmark
camera
update request
map problem
city (create new)
street (create new)

Please feel free to share your feedback here!

Thanks,

Shirli
Last edited by shirlig on Wed Dec 19, 2012 6:12 pm, edited 2 times in total.
Reason: Changed thread title and stickied
Image
shirlig
Waze Team
Waze Team
 
Posts: 1693
Joined: Wed Dec 23, 2009 10:40 am
Has thanked: 45 times
Been thanked: 2254 times

Re: Editor Version Dec 19th Official Feedback Thread

Postby runningbandit » Wed Jan 02, 2013 10:00 pm

I have tried several browsers including Chrome...Mozilla & IE are not working either.
I am in the United states
runningbandit
 
Posts: 7
Joined: Wed Dec 12, 2012 6:43 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Editor Version Dec 19th Official Feedback Thread

Postby runningbandit » Wed Jan 02, 2013 9:32 pm

porubcan wrote:on INTL, red segments I have checked are not visible in client.

if devs will consider to force city/street for new segments, they should first get rid of current bug (sometimes mainly after changing zoom level to closer zoom it is unable to select segments - not displaying properties of selected segments & unable to submit city/street as no country is listed, which is somehow related to landmarks layer - at least errors are less often when this layer is off). it happened to me many times that after I drow new segment I was unable to set city/street due to no country in dropdown. so I saved segment without name, reloaded page (permalink) and edited properties then. if it wouldn't be possible to save unnamed segment I will loose whole segment I just created. sometimes I draw new roads long several kilometers with many "dots" to ensure proper geometry. it takes lot of effort to recreate such segments again.


I am unable to edit at all... I can go to add items, or edit, but once i am in there is no properties menu on the left. It does not allow save either. all i can do is hit "esc"
runningbandit
 
Posts: 7
Joined: Wed Dec 12, 2012 6:43 pm
Has thanked: 0 time
Been thanked: 0 time

PreviousNext

Return to Waze Map Editor

Who is online

Users browsing this forum: SyukrieRazak