New WME v2.309

Map Editors Community WME Production Version Releases
1

Hi Everyone :waving_hand:

We hope you’re all doing great.

We’ve just released a new version of WME v2.309 :tada:

Below you can find a summary of the release.

Implemented Community Suggestions:

We’ve listened to the community’s requests for more versatile address options. We’re excited to announce that we’ve expanded the types of House Numbers you can now map in WME Production for both Residential Point Places (RPP) and venues.

You can now use the following address formats:

  • Generic alphanumeric addresses: Any mix of letters and numbers, even with letters before digits, 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 and will appear in autocomplete).

  • Uservoice suggestion - More complexity for Residential place point house numbers

  • Uservoice suggestion - Need options for Unit/Apt/Space/Suite/Building numbers on addresses and RPPs

  • Uservoice suggestion - Support house number format e.g. 123/45-67

  • Thanks @seppasami, @RichardPyne and @kid4rm90s for submitting these suggestions and everyone for voting!

New features/enhancements:

1. Closures: We’re introducing a change that, when a closure has the status “Finished” or “Finished earlier,” the closure card is now clickable in a read-only (disabled) mode. When opening the closure form:

  • All input fields will be disabled and not editable.
  • The “Created by” and “Provided by” sections will remain visible.
  • Editors will be able to view the full details of the closure, even after it has ended.
  • This change has been a part of the community feedback, raised during the NA mega meetup.

2. WME SDK Improves Performance of the FC Layer Script: The FC Layer Script now uses the WME SDK for a significant performance boost. The script loads map data much faster across all zoom levels, particularly with large datasets. This enhancement improves the editor experience and highlights the WME SDK’s value in enabling script writers to create quicker, more efficient tools.

3. SDK improvements: please refer to the change log to check the SDK additions.

Bug fixes:

We released 12 bug fixes:

1. House numbers (HN) revamp: Fixed the issue where the enabled House Numbers layer prevented roundabout creation.

2. RPPs: solved an issue where RPPs containing non-latin characters in the HN field could not be saved

3. Suggest an Edit on House numbers (HN):

  • Addressed an issue that there is no pending suggestion notification under the segment for suggestion creator.
  • Fixed the flow that the lamp icon is visible only for users who have the rights to Accept/Reject a suggestion and not for the suggestion creator.
  • Resolved the issue that there are no suggestion details on the card in case you open a suggestion from the map pin/issue tracker/permalink.
  • Handled the issue where an accepted issue card couldn’t be closed if opened from the segment’s history.

4. Map Events Filtering / Duplicating:

  • Resolved an issue that the Crosshair button to locate events is not added to the event details menu.
  • Addressed the issue with the ‘Locate’ button and polygons: when a user clicks the ‘Locate’ button for a Major Traffic Event (MTE), the MTE’s polygon is now visually highlighted on the map.
  • Fixed the issue where a suggested closure was not highlighted on the map when hovered over.
  • Corrected the behavior where selecting the ‘Specific category’ radio button ticked all category checkboxes by default. Now, only the first checkbox is selected, matching the behavior in the ‘Issue Tracker’.
  • Handled a problem where the ‘Locate’ feature didn’t work on turn closures.

5. Performance: fixed the problem that the crash happens in case you pan the map from the previous edit.

Known issues:

1. Map Events Filtering / Duplicating: Failed closure should be locked for editing and verifying.

You can read more here.

We look forward to hearing your feedback! :envelope_with_arrow:

Thank you!
Olesya

56 Likes
Nova Versão WME 2.309
New WME v2.318
2

I have a question on this point - digits before letters were allowed previously, is this supposed to be “letters before digits”? One of the examples listed after has “a1” so I’m thinking that this is the case but want to confirm.

Thanks!

4 Likes
3

Hi @jushag thank you for pointing this out, I have edited the post accordingly. :slight_smile:

5 Likes
4

One other question - when using special characters (non-numeric) on house numbers, does this impact interpolation? Forced house numbers on a segment disables interpolation, e.g. - does anything similar apply to HNs using this expanded character set?

3 Likes
5

Where in the RPP and HN functions can we enter the Unit/Apt/Space/Suite/Building numbers?

4 Likes
6

Just want to make it clear that the new alphanumeric functionality already existed for HNs and that it’s being expanded to support RPPs and venues with this release.

Previous release info: https://www.waze.com/discuss/t/more-complexity-for-house-numbers-hn-for-segments-now-available/280585

6 Likes
7

@jushag, just to be sure, are you asking about the impact of the expanded character set used in HNs within RPPs/venues or house numbers in general? If you have some specific instances in mind, I will appreciate you providing those so we can ask the team directly.

3 Likes
8

Thank you for mentioning this post @nimper2000 this is exactly what we are trying to achieve with this release.

Regards,
Olesya

2 Likes
9

Despite today’s new version, I am still unable to approve this RPP PUR that contains a slash in the address: https://waze.com/en-US/editor?env=usa&lat=39.36042&lon=-76.54967&zoomLevel=19&venues=185729418.1857621856.21061837&venueUpdateRequest=185729418.1857621856.21061837

2 Likes
New WME v2.318
Nova Versão WME v2.318
10

I’m referring specifically to house numbers added to segments. In certain cases where a house number doesn’t exist and a reasonable result can’t be obtained from Google, interpolation happens between 2 addresses that encompass the missing house number.

For example, a segment may contain house numbers 1, 3, 5, 9, 11. If no result is found for 7, a house number can be interpolated half the distance between 5 and 9. If we had 1, 3, 5, 5a, 9, 11 would 7 still be interpolated between 5 and 9?

1 Like
11

Same behavior with this RPP PUR.

2 Likes
12

Thank you for your feedback @russblau. There is a space in between which is why it cannot be added. The same will fail when adding a new RPP/venue; if there is a space it will not be saved regardless of the characters/digits used. This particular format has not been mentioned but I will check about it with the team.

Kind regards,
Olesya

2 Likes
13

Thank you for the clarification @jushag It does not seem like the interpolation logic would get broken by adding 5a in your scenario. I will, however, make sure to have it confirmed by the team to be on the safe side.

3 Likes
14

Thanks, so many exciting updates!

Can I please clarify, if I set the address to “10-20 Market St” and then attempt to navigate to “15 Market St”, will it navigate me to the “10-20 Market St” address?

2 Likes
15

Hi @Olesya-Staff !

Please do double check, as the HN alphanumeric update did allow spaces to be used in HN number fields.

2 Likes
16

Hi @nzahn1,

It does allow spaces in HNs (HN for segments) but not HNs within RPPs or venues. As mentioned, I’ll check about this limitation with the team and let you know as I have more details.

4 Likes
17

Awesome, thanks for checking. It would be awesome to have parity between the address feature.

5 Likes
18

Hello,
We have information in France that when Waze POIs are associated with a Maps POI, the information (such as phone number, opening hours, etc.) is synchronized in the client to the Waze POI (regardless of whether the information is entered in WME or not).

The problem is becoming increasingly common, and has been noticed with UR types such as “incorrect opening hours.” Indeed, with vacations and holidays, stores change their hours. Sometimes, the hours are correctly modified by the owner on Maps, but not necessarily on Waze.
We should consider:

Prioritizing Gmaps information on the Waze client EVEN IF the Waze POI has the details on WME.
prohibit writing POIs on WME when the details are already entered on Gmaps (see complicated with a condition: if Gmaps is kept up to date or contains a Business page).
I am available to explain the principle,
Misterlogik, L4 Fr

3 Likes
19

Thank you, so much! great release and features very much needed!

4 Likes
20

Hello @LostInMyMaps,

Thank you for your input!
Just to make it more precise, are you referring to House Numbers for segments or House Numbers within RPPs/venues? If you could also provide a specific example of where you would see it on the map, it would be much appreciated.
I’ll pass this question along to the relevant team.

All the best,
Olesya

3 Likes