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

by **AlanOfTheBerg** » Tue Dec 04, 2012 3:18 pm

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

by **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

by **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.

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.

by **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:

by **top_gun_de** » Mon Dec 10, 2012 8:35 pm

Maybe this is old, but I found no mention of the issue:

When I draw a new road and the road ends in an existing road, the beginning of the road does not have a node, resulting in a road with navigation issues.

I have just found a similar behaviour when I drag the end of a road from an existing junction. The resulting road will have no end-node.

In my opinion, this is bad. Due to the design of Waze's routing engine, every piece of road must end in nodes, there seems to be no case where the end of a road should not have a node. The standard behaviour of Waze should automatically generate a node when the end of a road is not connected to another road, thereby enforcing the wiki guidelines.

Best regards,

Detlev

by **jondrush** » Mon Dec 10, 2012 8:45 pm

It's a known issue. We've put in a request to have that automated. We'll see what Waze's response is.

by **mssusa** » Mon Dec 10, 2012 8:57 pm

I kinda like the current behavior. With the highlighting tool the lime color reminds me that work on this segment is not over yet. Very helpful with long roads and highways where there is a lot of panning.

Sent from my GT-I9100 using Tapatalk 2

by **top_gun_de** » Mon Dec 10, 2012 9:04 pm

The newly painted segment has no city and no name, so it is highlighted in grey. A newly painted road without an end-node is technically broken.

The highlighting extension is great, but it's new and not that wide-spread.

Best regards,

Detlev

Gesendet von meinem iPad mit Tapatalk HD

by **mssusa** » Mon Dec 10, 2012 10:02 pm

top_gun_de wrote:The newly painted segment has no city and no name, so it is highlighted in grey. A newly painted road without an end-node is technically broken.

The highlighting extension is great, but it's new and not that wide-spread.

Best regards,

Detlev

Gesendet von meinem iPad mit Tapatalk HD

Everything I'm not completely done with is technically broken. Named or not. Newly mapped or disconnected from years old system-connected client-paved roads. All I'm saying is that I'm hacking this 'bug' to mark the roads that I should not end my editing session without mapping properly.

Sent from my GT-I9100 using Tapatalk 2

by **davipt** » Wed Dec 12, 2012 4:36 pm

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