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

[AlanOfTheBerg]

Possible fix for:
"Highlighted segment has been extended beyond the allowed distance"

The workarounds have been documented for quite some time: http://www.waze.com/wiki/index.php/Map_ ... _the_limit

Just splitting the segment is enough because then there are new segments with start/end points instead of an original segment with an end point moved too far.

[mssusa]

Possible fix for:
"Highlighted segment has been extended beyond the allowed distance"

The workarounds have been documented for quite some time: http://www.waze.com/wiki/index.php/Map_ ... _the_limit

Just splitting the segment is enough because then there are new segments with start/end points instead of an original segment with an end point moved too far.

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.

Sent from my GT-I9100 using Tapatalk 2

[beffl]

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

[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]

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.

[davipt]

I think I found out yet another issue, albeit I think this was also happening on the previous editor. This seems to be the reason for my reversed A-B -> B->A roundabout and other segments.

- Create a segment from left to right, A->B
- Create a second segment connected to B, also left to right
- You'll have two connected segments A->B A->B
- click on the node
- press delete
- alternatively click on both segments, whichever order, and click on the bridge

what would happen
- one segment with A->B

what happens
- randomly the segment becomes B->A. Funny thing is that 90% of the time, doing "undo" and repeating the exact same operation (delete node or bridge) will do the correct thing and keep the new segment A->B

Now I understand why I have so many segments with one-way and locked but with fwd and rev average speed. It was my adjustments of ramps or roundabout nodes that were reversing the A->B to B->A and screwing the up.

Now it's way easier to identify with the big A and B balls. Again, if fails, undo and repeat!

[fvwazing]

Cool find! Which reminds me... Is there any possibility to reset those speeds, apart from creating the segment new?

[Kuhlkatz]

A reset would mean nothing. The data on speeds is also kept in various increments in the back end for each unique segment id. You only see the overall averages in WME.

A 'combine' function would have more use for unsplitting without losing all data, effectively combining the data for both directions into a new single segment id.
On the other hand, it should be up to date in a few days anyway if it's a busy stretch of road.

[davipt]

A reset would mean nothing. The data on speeds is also kept in various increments in the back end for each unique segment id. You only see the overall averages in WME.

Taking in consideration the "bug" I reported above, it would indeed be nice to be able to reset the averages, fwd and rev in separate. Because of this A-B reversal, I have now a lot of one-way segments with averages in both ways, and it would be nice to see 0 on the reverse direction which should never be driven.

[Kuhlkatz]

Because of this A-B reversal, I have now a lot of one-way segments with averages in both ways, and it would be nice to see 0 on the reverse direction which should never be driven.

I think we might need 'official' confirmation from Waze that the maintained timed stats are also duplicated when a segment is split, and not just the averages. By themselves, the averages likely would not affect routing.