More Complexity for House Numbers (HN for segments) now available! 🗺️

Hi Editors,

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 segment’s HN 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)

UserVoice Victories!

We’ll be marking the top 1 UserVoice suggestion, "House numbers with slash," as “now available.” Yay!

Thank you and happy mapping!

Maia on behalf of the team

17 Likes

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.

3 Likes

Will the interpolation brake by adding these different types of house numbers as it does when we force numbers?

2 Likes

I believe the interpolation is done by Google Maps, not by Waze. Waze uses results from Google Maps when the exact address is not known by Waze.

Thank you for the question! I am checking this with the team.

2 Likes

It can use Waze HN interpolation, but only when Google has no address data

2 Likes

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.

1 Like

Is complex HN functionality going to make its way into the RPPs?

I tried multiple different ways to label the structure with a RPP with no success (8855/3, 8855-3, 8855 3)

Still unable to mark these addresses accurately due to being off the named road.

HN.jpg

1 Like

The new HN complexity is only for HNs, not for RPP or places. They have given no indication that this will extend beyond HNs.

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.

Thanks Russ! Indeed there are no plans currently to extend the functionality to RPP, but we’ve passed on the request to the team.

1 Like

Back with a reply from the team: interpolation should continue working as previously.

2 Likes

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?

1 Like

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М.

This bug in the beta local issues forum may be related.

There is the same problem with Hebrew characters.

Hi WolfMeister-TL,

Thank you for the report! I’ve filed an internal issue for this for further investigation.

Regards,
Darya

1 Like

The editor refuses to save house numbers that include Hebrew letters. Only Latin letters are saved as part of house numbers.

As a GIS professional, do you have a suggested format to use in Waze for Unit/Suite/Building sub-addresses?

Brilliant ! Good job. Without a doubt, very useful.
However, WME is sometimes reluctant to accept the address in the proper format.
Insist or wait?