I was trying to get to 1736 1st Street NW Washington, DC 20001 and WAZE kept directing me to the 1700 block of 1st Street NE Washington, DC 20002. In all fairness to WAZE, both Google Maps and Verizon Navigator did the same thing. The two addresses are only about a mile and a half apart, but that’s not much help when you have no idea where you are. I think it may be a problem on whether you list the street as 1st or First.
It probably is bad data being imported from Google Maps; thus, that’s why both programs go to the same wrong location.
Permalink, please?
On further review, there is something odd going on with Waze search.
If you type “1736 1st St NW” in the search bar, the first two suggested results that pop up are as follows:
- 1736 First St NW, Washington, DC
- 1736 1st St NW, Washington, DC
(Note: the order in which results are presented may vary depending on where you are when you do the search.)
If you click on the first link, the correct destination address and location come up. But if you click on the second link, the destination address appears as “1736 First St NE, Washington”, and Waze will then direct you to that incorrect destination.
I’m unsure whether this has any relationship to the search error I reported in another thread.
Russ
The good news is that the fix will be coming around the end of the month so the problem will completely go away if it is the same bug.
I heard back from Noam, and apparently it is not the same bug. The auto-complete search results are obtained from Google, so the error is on their end.