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
8842.5 km. away
I search for: 13th Street
13th Street, Sacramento, CA
16574.7 km. away
I search for: 13th St, Parkhurst
W 13TH St, Lakeland, FL
12528.6 km. away
I search for: 13th St, Johannesburg
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.