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

The place to get information and ask questions about everything to do with properly and successfully editing the Waze Map.

Use this forum for all general editing questions, and the sub-forums for specific types of Waze Map Editor features.

Moderators: Unholy, bextein

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

Postby Dave2084 » Tue Dec 04, 2012 8:53 pm

Further to that I've now found examples of cities duplicated which DO NOT HAVE alt names so it looks like a general error check fail :shock:
Dave2084
Global Champs Localizers
Global Champs Localizers
 
Posts: 2420
Joined: Tue Feb 09, 2010 12:58 am
Location: Lincoln, UK
Has thanked: 392 times
Been thanked: 383 times

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

Postby Dave2084 » Tue Dec 04, 2012 8:14 pm

The city layer has now been (or is in the process of being) updated for the World Server. :D

This seems to have uncovered a bug in WME.

Where some cities have been renamed in the UK to remove (county) if one of them had alt names it has let the editor save the second city with the same name too far away from the first, so city blur is back!

Example:
Greetwell in North Lincolnshire which has alt street names on Messingham Ln and Greetwell in Lincolnshire

These are now linked on the cities layer despite being 25 miles apart.
Dave2084
Global Champs Localizers
Global Champs Localizers
 
Posts: 2420
Joined: Tue Feb 09, 2010 12:58 am
Location: Lincoln, UK
Has thanked: 392 times
Been thanked: 383 times

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

Postby davipt » Tue Dec 04, 2012 4:42 pm

AlanOfTheBerg wrote:The a/b "reversal" was documented before, I forget where, and whether we figured out the reason.


it would be nice to find that conversation ;)
davipt
Waze Global Champs
Waze Global Champs
 
Posts: 2766
Joined: Tue Nov 02, 2010 8:51 am
Location: Oeiras, Portugal
Has thanked: 284 times
Been thanked: 593 times

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

Postby davipt » Tue Dec 04, 2012 12:34 pm

Kuhlkatz wrote: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.
davipt
Waze Global Champs
Waze Global Champs
 
Posts: 2766
Joined: Tue Nov 02, 2010 8:51 am
Location: Oeiras, Portugal
Has thanked: 284 times
Been thanked: 593 times

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

Postby Kuhlkatz » Tue Dec 04, 2012 12:28 pm

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.
Kuhlkatz
Waze Local Champs
Waze Local Champs
 
Posts: 917
Joined: Fri Jul 20, 2012 6:11 pm
Location: Centurion, Pretoria, South Africa
Has thanked: 39 times
Been thanked: 160 times

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

Postby davipt » Tue Dec 04, 2012 10:26 am

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!
davipt
Waze Global Champs
Waze Global Champs
 
Posts: 2766
Joined: Tue Nov 02, 2010 8:51 am
Location: Oeiras, Portugal
Has thanked: 284 times
Been thanked: 593 times

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

Postby bgodette » Tue Dec 04, 2012 8:06 am

beffl wrote:
mssusa wrote: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
Waze Global Champs
Waze Global Champs
 
Posts: 3420
Joined: Wed Jul 06, 2011 8:19 pm
Location: Denver, CO
Has thanked: 109 times
Been thanked: 510 times

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

Postby beffl » Tue Dec 04, 2012 7:20 am

mssusa wrote: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
beffl
Global Champs Localizers
Global Champs Localizers
 
Posts: 2571
Joined: Tue Jun 19, 2012 3:00 pm
Location: Perchtoldsdorf (bei Wien), Austria
Has thanked: 372 times
Been thanked: 613 times

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

Postby AlanOfTheBerg » Mon Dec 03, 2012 5:10 pm

bz2012 wrote: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.
AlanOfTheBerg
Waze Global Champs
Waze Global Champs
 
Posts: 23611
Joined: Sat Aug 28, 2010 8:48 pm
Location: US Country Manager - Oregon, USA
Has thanked: 1126 times
Been thanked: 4788 times

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

Postby Olestas » Mon Dec 03, 2012 9:22 am

As I understand, end roads without junction point on the end have problems with routing. Isnt it possible to automatically add junction points to all open ends? So we do not have to do it for ALL existing open roads?
Or at least start automatically add junction point to newly drawn open end segments.
Olestas
Coordinators
Coordinators
 
Posts: 5628
Joined: Wed Mar 09, 2011 7:08 pm
Location: Latvia
Has thanked: 2672 times
Been thanked: 1992 times

PreviousNext

Return to Waze Map Editor

Who is online

Users browsing this forum: Bing [Bot]