Road Shields on Unnamed Segments in Texas

Map Editors Community WME Local Issues Bugs
1

I was adding some new shields that were released and now I am seeing a shield on segments with “None” for segment and “None” for city.

This is the same thing as this previously reported issue (https://www.waze.com/forum/viewtopic.php?t=376072)

I am able to see this because of a script that shows road shields that are applied to segments (this includes railroads). Since the segments are unnamed, I can’t remove the shield. Note: as of time of this posting, the tiles have not updated to include them in the app but I anticipate it will reach the app tomorrow

Here are a couple screenshots (with script to show the shields)

Waze Map EditorRoad Shields on unnamed segments.png|557x743

Waze Map EditorRoad Shields on unnamed segments 1.png|698x520

You will not be able to see them in WME without scripts. The only way to see them without scripts is in the console.

Here is what I am seeing in my console on a couple of these segments. I am pulling the console details from an incognito WME with no scripts to show it is there without scripts.

W.selectionManager.getSelectedFeatures()[0].attributes.wazeFeature.id
W.selectionManager.getSelectedFeatures()[0].attributes.wazeFeature._wmeObject.getPrimaryStreetID()
W.model.streets.getObjectById(5604460).attributes
W.model.streets.getObjectById(5604460).attributes.dityID
W.model.streets.getObjectById(5604460).attributes.signText
W.model.streets.getObjectById(5604460).attributes.signType

Here is a base example to show that the shield info does not show up on a segment that has a city name

Note that the sign text and type are both Null

Console good.png
Console good.png911×338 14.7 KB

Here are examples of some issue segments. Note that the primary ID for the issue segments are all the same (5604460) and the sign text and type are not null
Waze Map Editor
Console bad 1.png
Console bad 1.png942×391 18.6 KB

Waze Map EditorConsole bad 2.png|907x392

2

You can disregard this issue. I somehow lucked into resolving the issue myself

I think I know what I did and can now reproduce it. Let me know if I should move this to an actual bug report

Here are the steps to “accidentally” add a shield to an unnamed segment

  1. Select a segment that has a road name
  2. Add an alternate address
  3. Select “None” for city (or select a city name - which will only cause the bug to be located with the city)
  4. Leave street name blank (this was done by accident when I caused my original issue)
  5. Apply alternate address
  6. You will now see the “add shield” icon
  7. Add a shield
  8. Shield will now show on all segments with None address and None city (or selected city)
  9. Delete the alternate address without removing the shield and now you have no way to remove the shield.

To be able to remove the shield, you need to follow the above steps and delete the shield in step 7

Let me know if you want me to create GIFs to show it as well.

3

Hi John /jm6087!

Thank you for the report and your own investigation :nerd_face:

I would appreciate to see GIFs to show steps as well. I want to show it to developers to decide if it was really the root cause for the initial report from France.

Regards,
Nataliia

4

Let me know if this helps.
Here is my test segment https://waze.com/en-US/editor?env=usa&lat=29.63717&lon=-104.28132&zoomLevel=20&segments=534725822

Here is a video of the creation using incognito to show it is not caused by scripts.
https://youtu.be/830iW3BH2QI

Since it is not visible in native WME, this is a screenshot of WME with scripts to show that the shield shows up on unnamed segmentShields 1.png

Here is a video that shows me deleting the alternate name (without deleting the shield) in incognito. I then switch over to WME with scripts to show that the shield is still showing on unnamed segments.
https://youtu.be/cY-zBhiiwjQ

Since this is created using my test area with a test city and does not cause issues with the rest of the state, I have left it with the shield.

I am leaving the alternate name deleted. If you want to bring it back so you can remove the shield, here is a video of what to do

https://youtu.be/xdDDqFHSI6Q

5

Just checking on this. The issue still exists in both Beta and Production. I just realized that it was reported as local issues since it appeared to be an localized problem. I believe that this is actually a bug that is reproducible. Should I report a beta bug or move this thread to beta bugs or is it fine here?

6

Hi John,

We have an internal issue for this case. I will update when we have some news.

Updated: John, I apologize. Could you please share a link to locations where road shields are still visible? I revisited an old problem, and it’s fixed now. There was some misalignment in the database, and it’s resolved. I simulated testing segments, but I can’t see road shields with my device.

Sorry for inconveniences.

Regards,
Nataliia

7

No worries, just going through some of my old reports

Thanks