Page 4 of 4

Re: Waze app address lookup details (from Ohad)

Posted: Tue Jan 28, 2014 10:27 pm
by sketch
Hm. I assumed 1208 S Clearview was the Waze result because it was on the street. Didn't realize Google had so many address pins on the street.

Anyway, 4820 Richland Ave is giving the Waze result. The Google pin is right on the intersection with Rivage, but choosing the Instant result does give the Waze pin location in the middle of the dead-end block.


Sent from my iPhone using Tapatalk 2

Re: Waze app address lookup details (from Ohad)

Posted: Tue Jan 28, 2014 11:17 pm
by sketch
AlanOfTheBerg wrote:
sketch wrote:...but choosing the Instant result does give the Waze pin location in the middle of the dead-end block.
Ohad wrote that the auto-fill (I assume what you mean by 'instant result') is only populated by google. But even if you tap on that, Waze still may be the source behind the "navigation target."
Yep, that's what I've been testing.

The Google Instant results seem to be somewhat flexible—depending on what you type, it'll give results with or without abbreviations (e.g., "3978 West Esplanade Avenue" or "3978 W Esplanade Ave"). I don't think that has an effect on the Waze matching process.

Re: Waze app address lookup details (from Ohad)

Posted: Thu Feb 06, 2014 2:45 pm
by sketch
CBenson wrote:That's a lot of house numbers.
Yeah, but there's a buuuunch of really-wrong ones, at least in my area. Rather have to nudge a bunch of automatically-added numbers than add them all in myself.

Re: Waze app address lookup details (from Ohad)

Posted: Tue Jan 28, 2014 6:09 pm
by SlowlySlowly
AlanOfTheBerg wrote: When you search house numbers in the beta editor, the results are from Waze nearly 100% of the time, and the search pin lands at the stop point (on the road). Perhaps the stop point in the app would show the same?
Am I missing something, doesn't this break door-to-door routing to stores in large parking lots? Perhaps that is irrelevant because you rarely search for stores directly by address, but for apartment complexes with numbered buildings you do.

Also, does this get applied for contact searches?

Re: Waze app address lookup details (from Ohad)

Posted: Sun Feb 02, 2014 3:24 am
by SlowlySlowly
In San Marcos, CA Google uses McMahr Drive and Waze uses McMahr Road. (San Diego's GIS, SanGIS, matches Waze). Google returns different locations for the same address based on the use of Road or Drive. Both options appear in the client as suggestions.

Reported to Google. Any other fixes required in Waze?

Re: Waze app address lookup details (from Ohad)

Posted: Fri Jan 31, 2014 6:50 pm
by syborg_sasquatch
Maybe I am missing something with my testing and/or maybe this has been discussed elsewhere, but Waze appears to be attempting to interpolate addresses based off of the HNs in its system.

If you go to this section of Brightseat Rd in Landover, MD and search for any even address below 2200 as in "500 Brightseat Rd, Landover, MD" it will always drop a pin at the highlighted node in the link. This is the stop point for the only HN ("2000") on this section. "2200" is on the other side of Landover Rd.
500_Brightseat.jpeg
(27.13 KiB) Downloaded 1853 times
2000_Brightseat.jpeg
(41.64 KiB) Downloaded 1851 times
One problem with this is that the building with "1000 Brightseat Rd, Landover, MD" as its premises address is not in the Landover CDP. It is down here in the "Summerfield" CDP (I realize that the segments in this area still need to be modified from "No City"). If you search for this exact address in the app, using Waze as the provider, you will be taken to the node up by Landover Rd and not the correct location. To get to the correct location, "1000 Brightseat Rd, MD" needs to be used as the search parameter (and "1000 Brightseat Rd, Summerfield, MD" if the segment's city attribute was updated to reflect the CDP).
1000_Brightseat.jpeg
(40.1 KiB) Downloaded 1847 times
Edit: Added Screenshots

Re: Waze app address lookup details (from Ohad)

Posted: Thu Feb 06, 2014 3:29 am
by tonestertm
Ohad on Waze HN source wrote:...we only take into account house numbers that a Waze community member explicitly entered or updated, and not house numbers that we obtained from possibly non-accurate external sources which have not been modified by an editor in WME. We trust you guys way more than we trust our external search providers which, in turn, we trust more than imported 3rd party data to our database.
Does this mean that we should be giving all "un-updated" House Numbers a nudge, after verifying they're correct, in order to increase confidence?