pmaten
My feedback
1 result found
-
31 votes
Thank you for this suggestion.
We are aware of this need since address fields are ordered differently from one country to the other.
Providing this flexibility in address fields is planned but it’s out of current scope so we can’t share a timeline at the moment.
We will keep the community posted, so stay tuned!
pmaten
supported this idea
·
An error occurred while saving the comment
I agree. The whole country can benefit from this as we don't need to manually put numbers on houses because they can be automatically be infered from the intersection and distance in meters from the second component.
Currently, in Colombia you can find intersection by searching as follows:
'Calle 46 Carrera 57', waze finds intersection between the streets named 'Calle 46' and 'Carrera 57'
'Calle 46 57', Waze usually gets this right, and finds intersection between the streets named 'Calle 46' and 'Carrera 57'. I guess it finds the substring '57' in 'Carrera 57'.
What needs to be implemented, is that Waze understand a third element in the address (second component in a house number), which is the distance in meters. This is really important because the driving direction is incomplete in the intersection, you still need to get into the street and depending on how Waze got the direction to the intersection, you may get to the intersection but be unable to turn toward the destination street.
Google Maps understands this, so you can try searching the following addresses to get an idea of how it works:
Calle 41 # 74-20 Medellín - Antioquia, Colombia
Calle 41 # 74-50 Medellín - Antioquia, Colombia
Calle 41 # 74-80 Medellín - Antioquia, Colombia
They seem to work fine with or without the '#' symbol.