Search - Please improve

[Glipsie]

Hi there

Since Waze v3 Android I have been struggling to search for specific streets.
To give an example, last night I had to go here:
https://world.waze.com/editor/?zoom=5&l ... TTTFTTTTFT
From here:
https://world.waze.com/editor/?zoom=5&l ... TTTFTTTTFT
Total distance of ~ 16kms (23 via the freeway)

I search for: 13th St
Results:
Anschlusstelle Vienenburg-Ost/...
8842.5 km. away

I search for: 13th Street
Results:
13th Street, Sacramento, CA
16574.7 km. away

I search for: 13th St, Parkhurst
Results:
W 13TH St, Lakeland, FL
12528.6 km. away

I search for: 13th St, Johannesburg
Results:
13TH Ave, Johannesburg, MI
13724.5 km. away

At this point, I gave up and used google maps instead, incorrectly assuming that the road was not mapped.

My assumption as a user is that results closest to me are prioritised. There are MANY 13th streets in Johannesburg, let alone South Africa. Why only return 1 result that is over 8000kms away.
Waze also does not allow me to navigate to anything thats further than 200 miles (320 kms) away anyway, so why even show the results?


Today I was playing around with the client trying to navigate to 13th street. The "correct" way to search is thus: 13th St, Parkhurst, Johannesburg, South Africa.
13th St, Parkhurst, South Africa also does the trick.

So my suggestions are thus:
1. Please limit results to within 200 miles/320 kms of your current location.
2. If no results are returned within the range above, then tag on the user's current country and search again. This would result in my second search (13th st, parkhurst) being searched as "13th st, parkhurst, south africa" and thus returning the desired result. It feels silly that I need to type in "South Africa" to each and every search request.

Thanks
/Glipsie

[AlanOfTheBerg]

Waze used to have this problem a few versions ago, so it's disheartening to find it is again giving results across server infrastructures. I agree Waze needs to do a MUCH better job at returning useful search. For the world infrastructure where you are limited to 200mi for routing, returning only results under that limit makes perfect sense. The same could be said for the US/Canada servers where the search result limit should be capped at 1000mi.

[maantje76]

This problem also exists with cities and poi's. Dror could reproduce this problem with some examples I sended him. They working on à fix for the search engine...

[AlanOfTheBerg]

This problem also exists with cities and poi's. Dror could reproduce this problem with some examples I sended him. They working on à fix for the search engine...

That's good. Again.

[maantje76]

That's good. Again.

I know...

I had troubles in first place with finding cities. See this topic in the Dutch forum.

In those examples I only used WME, but it's the same in the client.

Entering the same cityname, on a different location on the map, gives a different result as you can see!

But this is a good reminder to ask what's the status...

[sampul]

Hi..

I also have this problem. I have just been on vacation in Denmark. I live in denmark, but decided to travel around in the country. however a lot of times it can't find the correct result i was searching for.
So many times i had to go to google maps to be able to navigate to a place.

I know the map isn't complete in denmark, but some streets i search for, can i find manually by viewing the map to find it.

So i really hope you will improve the search. I believe what glipsie said about adding country to the search will help a lot, because I tend to find a street more if I add denmark to the end and I do not get a lot of streets from different countries, sometimes I get results from the USA, and it gets really annoying. I also believe that most people will be searching for street names in his own country than in other countries all the time. So please improve the search, i know google is some of the best in search, but please look over the shoulder