Post Reply

Multiple address location pins from Google

Post by Kayos_On_The_Road
Hi,

As a warning, this is lengthy and covers an email conversation thread with a Google map editor, but the content is important and has a significant impact on waze map editing.

Per this FAQ wiki, waze predominately gets POI and street address information directly from Google.

https://wiki.waze.com/wiki/FAQ#What_do_ ... ocation.3F

Where this wiki is wrong is that the waze routing server *WILL* use the waze addresses if they exist in the waze map and will not query Google for the GPS location (even if Google does return a result, verified through personal experience). In many parts of the lower mainland, there are discontinuous streets of the same name. Apparently the Google search engine estimates address locations and all results for the estimation are returned to the waze search engine. It's up to the user to decide which one to pick as the correct location. This results in some users being routed to *VERY* wrong locations.

It was my understanding that this is corrected through the Google Map Maker interface by deleting the incorrect location pins, hence the following conversation with a senior map editor:

Flash:
Hello,

Address markers in Map Maker are a bit tricky. If the address marker does not exist when you search for it; the system will show you were it estimates it to be. To tell if it's an estimate or an actual maker, click on the History tab to see if it has a history. If it doesn't exist already and you ask to edit it in any way, the system then creates the marker for you to edit.

What has happened here is that the marker didn't exist; it was just an estimate, and you asking to edit it caused it to be created. But making your edit a deletion is not going to change where the estimated position is set.

Instead what we do with misplaced Address markers, which this is now one, is to move them to the correct position. You do this simply by grabbing it and dragging it. It should be placed at the front door/main entrance of the place to which it belongs.

Could you please undo this edit and move the marker instead?
This edit was marked for Auto denial

Kayos:
OK, thanks, I did not realize this was how these location pins worked. Just so I'm clear, searching for this address actually returned four location pins, only one of which was correct (Pin B). Should they all be moved to the correct location rather than deleted?
Now that I've looked at the incorrect location pins, clicking on history just says that history cannot be generated. Is this because they are estimates?

Flash:
You only need to move them if they have a history; if not they are just predicted spots.

The problem will be on common in Langley; namely that the road that are not continuous have not been named so that the system recognizes them as one road and/or that they address ranges for the roads have not been set or are set incorrectly.

I've been trying to fix them as I find them; I'll see if I can do 210 St next, though it might take me a bit.
This edit was marked for Auto denial

Kayos:
OK, I think I understand, but that doesn't really help me. I am a Waze map editor and the routing system returns all google hits for the address. If the user does not select the correct location, they will obviously be sent to the wrong location. The wiki for this issue is to delete the incorrect pins, hence my actions. Now you are saying don't delete them (because this will create them) and don't move them. How are these issues to be resolved as there a lots of discontinuous same name roads throughout the Metro Vancouver area?

Flash:
We do not map based on any instructions from the Waze wiki. That particular information is incorrect/incomplete.

The issue requires people that understand Map Maker at a deep level and have the edit and review trust to make the edits. You can do them, but you would need to learn the reasons why it is happening and until trust is built up you would need to wait for reviews.

The experienced editors and reviewers are free to work on whatever they wish, so I cannot promise you that anyone will fix this soon.

That begs the question of how these duplicate location pins should be dealt with going forward as I don't get the sense from this editor that there is much interest in correcting these errors. Should the drive be to enter house numbers into the waze map per this wiki:

https://wiki.waze.com/wiki/House_Numbers_in_WME

This would theoretically resolve the issue and break the reliance on Google information where there are errors in the returned search information.

What are everyone's thoughts on this?

Kayos
Kayos_On_The_Road
Posts: 5449
Has thanked: 386 times
Been thanked: 2069 times

POSTER_ID:16886216

1

Send a message
Samsung Galaxy S7 (7.0 stock), waze version always latest beta.
GC, CM - Vancouver, BC
Waze Beta Leader (Android)
Canada Wazeopedia
https://s.waze.tools/c6.pnghttps://wiki.waze.com/wiki/images/c/c1/ ... Tester.png

Post by codgerd
Kayos

I've been dealing with an angry UR over exactly this issue (Carnarvon St in van) and I think you're bang on here. I believe the solution is to use the house numbers layer. In my UR case I believe the issue was caused by new laneway house construction on a NS streets that has very few houses fronting onto it. Google doesn't know about the new houses and because there are very few existing houses on the street, its interpolations are horrendously off. Like, twenty blocks off on this case.

Sent from my D5503 using Tapatalk
codgerd
Area Manager
Area Manager
Posts: 553
Has thanked: 217 times
Been thanked: 29 times
Send a message
[img]https:///ESnp3j[/img]
AM Greater Vancouver, BC
AM Saguenay-Lac St-Jean, QC

Post by codgerd
(and I do realize I am replying to a year old post!)

Sent from my D5503 using Tapatalk
codgerd
Area Manager
Area Manager
Posts: 553
Has thanked: 217 times
Been thanked: 29 times
Send a message
[img]https:///ESnp3j[/img]
AM Greater Vancouver, BC
AM Saguenay-Lac St-Jean, QC

Post by codgerd
It might be that the location of the post in the BC forum limited readership - the BC forum is pretty quiet and I don't think gets many eyes. I've seen similar discussions in the Routing & Navigation forum, so I wonder whether you cross-posting your initial post there might bring it to the eyes of more editors.

I've added the HN of my UR to the map; we'll see whether it resolves the issue for them. It's an interesting problem - a lot of the laneway houses in Vancouver West are on corner lots, where the main house fronts onto an EW street, but the laneway house fronts onto the NS streets - and these latter don't typically have many houses fronting on them, so google's database of HN there is scant. Interpolating likely address locations in these cases is always going to give bad results.

I went looking for the civic addresses of the new laneway lots on the VanMap GIS, but lo & behold, their system is not updated either. So, it doesn't seem like there is a systematic way to address these missing houses other than entering them in manually if & when they pop up.
codgerd
Area Manager
Area Manager
Posts: 553
Has thanked: 217 times
Been thanked: 29 times
Send a message
[img]https:///ESnp3j[/img]
AM Greater Vancouver, BC
AM Saguenay-Lac St-Jean, QC

Post by Kayos_On_The_Road
Well, you can see that you're actually the only one that has responded to this post, so there is probably not much interest in resolving the issue in the waze community either. I still think the best method to deal with these issues is to add house number for the address that is causing the issue in waze.

This does however cause it's own complications because you still get multiple hits for the address so if the user doesn't know the intricacies of which search provider to select, they may still end up in the wrong place.

I guess the google map maker system is still down (I've not checked) but theoretically it could also be reported there as an issue and let them deal with it...

M@
Kayos_On_The_Road
Posts: 5449
Has thanked: 386 times
Been thanked: 2069 times
Send a message
Samsung Galaxy S7 (7.0 stock), waze version always latest beta.
GC, CM - Vancouver, BC
Waze Beta Leader (Android)
Canada Wazeopedia
https://s.waze.tools/c6.pnghttps://wiki.waze.com/wiki/images/c/c1/ ... Tester.png