Get a sneak peek at whats next for Permanent Hazards on our April 7th Office Hours!
Post by krikketdoug
Bigbear, there is nothing wrong with the location of where the places marker for Bistro Wasabi is. The address was throwing off results, if searching that way. I was using it as an example between the end point for a places marker versus address.

As a side-note, I loathe the system Google has with street-view. But that's just my not-so-humble-opinion. For some reason the senior Google staffers haven't consulted me on the matter... 8^)

I have another few comments to make, this time regarding another location some of us have been working on, but it probably belongs in the Waze App thread, as it's about the application implementation about places, not the editing. I'll post a reference thread if people want to follow, as it's related to what we've been talking about.. In the mean-time I have screen-shots I need to edit down to size.

And finally, since I'm a level 2 editor, could someone please delete the "house" marker at 3001 Finley Rd, Downers Grove, IL. From all the discussion here, it appears that it's best to just let the now-correctly placed Google marker for that Red Lobster handle things.

Thanks in advance, and thanks for all the help!

Krikket
krikketdoug
Posts: 160
Has thanked: 56 times
Been thanked: 16 times
Send a message

krikketdoug
Posts: 160
Has thanked: 56 times
Been thanked: 16 times
Send a message

Post by krikketdoug
Some new unexpected behavior, that I'd like confirmation as to what's happening, instead of just making an educated guess and acting on it. :) (And I'm throwing it in this thread rather than starting a new one because they are related topics...)

https://www.waze.com/editor/?env=usa&lo ... 960&zoom=5

For some reason Waze was routing me through an alley for a significant distance, crossing 5 streets in the process. The alley is properly marked a parking lot road.

The destination is UniMart in Chicago on Clark. (5845 N Clark) The start was near Clark and Argyle. Yes, I used the Google search engine, so I understand why the end-point was in the alley. But shouldn't it have switched to a regular street when the parking lot road crossed it?

To fix the problem, I suppose the location marker for UniMart could be adjusted on Google Maps, but is that actually the correct thing to do in this case, since the UniMart marker is correct for Google Maps' purposes?

Thanks in advance!
krikketdoug
Posts: 160
Has thanked: 56 times
Been thanked: 16 times
Send a message

Post by krikketdoug
Ok. Thanks for the explination. The follow-up question is that is it better to submit a google map change to fit our model, or just advise the end-user of the reason for the error?
krikketdoug
Posts: 160
Has thanked: 56 times
Been thanked: 16 times
Send a message

Post by PesachZ
qwaletee wrote:Google is very much still in the picture, entering a search that gets you a Waze result is still hit or miss. Last I heard the autosearch still relies entirely on Google, though a couple of earlier comments lead me to believe that at least some editors think otherwise.
This used to be true, but is no longer. Auto-complete searach now certainly includes Waze places in it, and possibly other waze data as well.
PesachZ
Wiki Master
Wiki Master
Posts: 4516
Has thanked: 1365 times
Been thanked: 1572 times
Send a message
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum

Post by PesachZ
deeploz wrote:Except if I've missed the forum thread dealing with this, I've detected potential unexpected changes on this wiki page.

This addition seems to be, however, relevant but required to be assessed.
At least, I suggest a review of this bullet point and, probably, the replacement of the last link (search in the forum) by a link to this thread.
according to the wiki this behaviour is true, the guidance may be true as well.
PesachZ
Wiki Master
Wiki Master
Posts: 4516
Has thanked: 1365 times
Been thanked: 1572 times
Send a message
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum

Post by PesachZ
PinPusher wrote:First, Waze knows the name of the street (alley) that the imported address points are attached to or it would not send us to "alley". It also knows the street type.
Second, Waze knows the address' real street and the slightest push causes the stop point to attach to the correct street. Yes, there are exceptions like when the entrance is on the side street.
Therefore Waze has all the information it needs to fix the problem. If street name="alley" then stop point goes to real street. This would be better more than 99% of the time.

Maybe Waze 4.0 will address this issue.
I am not waiting, I have corrected what I could on all of Chicago's East streets north of 54th Street, so far. PM me if you want to help.
what is actually happening is when you make the slightest push, you are confirming the waze pin. This then gives the waze pin priority, and waze pins are attached to the street with the name they are set for, so even if they are closer to the alley they still resolve at the street.

Before you made any adjustment the waze pin was not confirmed, it was a lower priority therefore than the google pin which was being used instead. When waze gets pins from google, they only come with a lat/lon location, not a street name to attach to, therefore waze uses the closest segment to the pin location which may be the alley.

Simply touching the waze pin confirms an editor has looked at it and gives it priority over 3rrd party sources like google.
PesachZ
Wiki Master
Wiki Master
Posts: 4516
Has thanked: 1365 times
Been thanked: 1572 times
Send a message
https://s.waze.tools/gc.pngNYhttps://j.mp/1xPiWC8https://j.mp/1C9mUY2
Formal Mentoring, Wiki
Useful Wiki pages
URs & etiquette | WME | Editing Manual | Quick-Start Guide | Best Map Editing Practices | Junctions
State specific Wiki | Forum

Post by pinpusher
Try moving the stop point away from Wolcott and closer to Blanchard. Wait two days & it should be OK.
pinpusher
Posts: 57
Been thanked: 1 time
Send a message

Post by pinpusher
Wait, I tried that and it does not work, best I could do is move it to the corner. :-(
pinpusher
Posts: 57
Been thanked: 1 time
Send a message

Post by pinpusher
First, Waze knows the name of the street (alley) that the imported address points are attached to or it would not send us to "alley". It also knows the street type.
Second, Waze knows the address' real street and the slightest push causes the stop point to attach to the correct street. Yes, there are exceptions like when the entrance is on the side street.
Therefore Waze has all the information it needs to fix the problem. If street name="alley" then stop point goes to real street. This would be better more than 99% of the time.

Maybe Waze 4.0 will address this issue.
I am not waiting, I have corrected what I could on all of Chicago's East streets north of 54th Street, so far. PM me if you want to help.
pinpusher
Posts: 57
Been thanked: 1 time
Send a message