Map Editor major ver (Nov 5, 2012) Official Feedback

[bz2012]

Is anyone else having this problem???

"loading road images" appears to be failing.
When roads layer is on I see pink. Mouse-over shows roads data is there.
Problem started about 24 hours ago and was reported at https://www.waze.com/support/.
Chrome Browser in Win7.
Have disabled all extensions.
Have cleared cookies.
No joy.

Any suggestions?

[Bomber_Man]

Im having an issue where I load a recent drive, and wish to use the "create road" function that appears over 30% of the map screen. Problem is after the road is created I can't save it because I "don't have permission"... and its my drive... hmmm...

[bgodette]

Just a big thanks for having already implemented the feature of storing the state of the full screen so a refresh keeps the editor in full screen mode

Yeah, that'd be JNF or possibly WazeBar doing that.

[bgodette]

BTW, is the speed data retained when you split a segment? In one or both segments? How about when you join an old segment to a newly created one and remove the junction to make a longer segment?

Yes, both, averaged.

[bgodette]

BTW, is the speed data retained when you split a segment? In one or both segments? How about when you join an old segment to a newly created one and remove the junction to make a longer segment? This is important when mapping freeways out of scattered client paved roads.

If not, then the best option is to extend a little, save then extended a little more and so on.

That's point I'm interested in, too. I read in a post that if you shorten (in terms of compress not to cut) a segment the speed rises e.g. the average speed of the segment is 50kmh. After shortenig the segment to the half the average speed rises to 100kmh. Can this happen?

THX, Stefan

Only in Cartouche, which isn't available any more. Papyrus/WME has always handled speed data correctly in the backend.

[bgodette]

It'd be nice if we could add house numbers to more than one segment of a street.

How do you propose it distributes the numbers, especially if the segments are different lengths, or cover different lengths of ranges?

You can because you have each segment's length. However, it is too much of a bother.

No, you can't. Say you've got 5 segments selected that cover the ranges 100-400, but they're all different lengths. Do you distribute based on length, segments, or ???

[bgodette]

It'd be nice if we could add house numbers to more than one segment of a street.

How do you propose it distributes the numbers, especially if the segments are different lengths, or cover different lengths of ranges?

[bgodette]

I'm finding many segments with no level set. I'm not 100% sure but I believe all were old unedited client paved segments. When I edit a segment to fix its geometry points and give it a name then select it together with another completed segment to create junctions at intersections the cross sign "+" does not appear. When I check the newer segment I always find its level property empty. New editor? or the move to the new infrastructure?

Cause a wazeModel update and that clears. It's indeterminate data from modified segments that's cleared by refreshing the wazeModel (F5/Permalink/Panning far enough/zooming far enough).

[bgodette]

I think I found another bug... In the layers menu, you can move a few of the layers around, so they are on top of each other in a specific order... The layer at the top of the list is actually below the other layers and the layer at the bottom of the list is on the top of all the layers.

Design, and it is consistent with the rest of the layers menu. It isn't first glance logical however.

[bgodette]

viewtopic.php?p=287986#p287986

Been there since they released to public. 781 fixed the turn problems leak but not the general bug introduced into loading features on zoom/pan. Basically the url args aren't being built right (going to server with...).

It's all my phone's fault for using Tapatalk.