We’ve heard your calls for more versatility in House Numbers, and we’re thrilled to deliver a feature that’s been highly requested by our community.
We’re expanding the types of HN you can now map in WME Production.
Starting today, you can use the following address formats:
Generic alphanumeric addresses: Any mix of letters and numbers, even with digits before letters, or two numbers split by a dash or slash (e.g., 10-20, 12A, a1, 1bis)
Alphanumeric addresses with slashes: Like 1/4A
Alphanumeric addresses with dashes: Like C15-20 or 15-20C
Leading 0s: Like 0 or 0235
North/South/East/West addresses: Like N73W13430 (not supported in full search but can be added to WME and will appear in autocomplete)
Thank you for adding this ability! As the GIS tech for my 911 District it is often necessary to use unit numbers or suite numbers as sub-address information for a particular residence or business and until now I could only navigate Waze users to the base address.
That’s the way it’s supposed to work, but I think Google usually provides their own interpolated address pin but doesn’t say it’s interpolated. As such, the Waze interpolated address is rarely provided.
Great. If only the entrance point bound to house number could be dragged away from the street. There are places where entrance isn’t on the same street compared to what is the official street address and number of the house.
It’s strange to solve only part of global problem and announce about win and close user suggestion as solved. Which sense from this improvement if users still can’t put correct HN in venues and RPP, especially for countries which don’t use HN?
After the rollout of these changes, we can no longer add house numbers with Cyrillic letters, e.g., house numbers 9А, 9Л:(unavailable attachment: Screenshot 2024-09-06 at 09.31.01.png)
Before any changes were made to the house number structure, such numbers were valid. Example: Segment with house numbers like 21Л, 21М.
