New Waze Map Editor - Official Feedback Thread

[AlanOfTheBerg]

I've yet to hear from Dror on this: are we getting points for "Solving" or "Not a Problem"ing update requests in WME? We already know we don't get points for solving problems in WME as we did with Cartouche.............

[AlanOfTheBerg]

Click on the "bridge" icon --> segments are bridged, but both original IDs remain in the Properties window as though the bridged segments are still selected separately

Not for me. The properties toolbox goes blank and no segments are selected . Bridging works normally.

[AlanOfTheBerg]

Am I the only one who thinks it was much easier to draw smooth roads in old Cartouche? The squares in the new map editor are terrible. The circles and the dragging method were much smoother in the old version.

It was smoother for some reason. The fact that the browser is doing more of the lifting for the server to load balance doesn't really explain why the movement of geometry nodes isn't as fluid in WME. The only explanation that makes sense is that the browser code is constantly checking for snap-to objects. We've asked them to disable this for geometry nodes, with the exception of the end of a segment. There's no reason to be looking for snap-to for middle-of-segment nodes.

[AlanOfTheBerg]

Add this to the list of oddities that /map-editor/ doesn't appear to have the highlighting correct, but /cartouche/, which I can log in to again, highlights correctly with the new gray highlight.

[AlanOfTheBerg]

Is it just me, or is anybody else not seeing Speedcams, Problems and Update Requests in the Papyrus for the last 2 - 3 days? Ctrl +F5 and re-login does not help.

You are not the only one.

[AlanOfTheBerg]

Can anyone please tell me I should use 'world/waze.com/editor' or world/waze.com/map-editor'? Are they the same?

It looks like they are the same thing.

/editor/ is the URL last posted by krankyd, so that is the one we should be using going forward, regardless of whether we find another one which appears to work. The others could disappear at any time. /editor/ is what is documented in the wiki for new mappers as well.

[AlanOfTheBerg]

FWIW, FF10 on Win7 seems to have fixed the problem I reported earlier with the Properties display upon deleting a junction or bridging segments.

Thank goodness! I was getting soooo tired hearing about all the firefox problems.

[AlanOfTheBerg]

Confirmed bug: Can't delete an unlocked segment last edited by a higher-ranking editor.

Location: Outside AM area, inside Editable Area
Object: Unlocked segment
Previous edit by: Higher-ranking editor
Action not allowed: Deletion
Actions allowed: all others

Workaround: Modify geometry or other attribute. The segment can then be deleted.

[AlanOfTheBerg]

having a issue :

I have been able to delete a node connected to Streets & Primary Streets.

At zoom level 200m / 1000ft, you are able to select node from higher or equal to primary, but having no data from streets. So I could deleted it, but there was an error when I save it.

This is a known issue as captured here: viewtopic.php?f=211&t=14441. This was shown to the Waze team in person by me at the Palo Alto meetup in January.

[AlanOfTheBerg]

Sorry then Alan. I must say that I'm not going to this forum very frequently...

No need to say 'sorry.' There's a lot of stuff to keep tabs on. I knew about this because I had reported it a LONG time ago.