Hence the "when it's fixed". I know it's by design, but I agree with you: they should provide the option, if only to increase the value of their own product instead of purposely crippling it.AlanOfTheBerg wrote:Google and Bing searches work, but only reliably for business and subject searches. Specific house addresses appear to not work.mfelaco wrote:If the Waze 3 client can use google maps results to guide places (when it's fixed), awesome. I'll just wait for the Android client.
Hahaha...AlanOfTheBerg wrote:It's hard to say what may happen. Some of this is my opinion: The issue at hand is that the Waze business model is to gather and sell traffic data and geotagged advertising. A road map and navigation to points is important to that, for sure. However, the next level of data being POIs, business addresses, home addresses, etc. is not nearly as important to Waze to have internally because other providers already have extensive databases of this information. If you can look something up in the other provider's database, but Waze can get you there, and provide some ads for local businesses as you drive by, then that's their drive. (Pun intended.)mfelaco wrote:Still, will Waze's own map be forever incomplete? Is this a known issue and there's no plan to add neighborhood info? Will address searches within Waze never work then? I guess I can live with the google maps workaround but it still feels kinda odd that I have to resort to that, not to mention I can't do it on the site... The ideal would be that both the Waze search works and the google maps search is allowed, IMHO.
And yeah I get their point of view, although I disagree with the specific choice of disallowing some google results. It's their prerogative, but if they want me to get the address results from Waze, address searches in Waze should work! I truly believe the neighborhood info to be essential in any map app.
Re: (Essential) Feature Request: Zones/Neighborhoods