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

[davipt]

The thing with the geometry node sticking to the mouse pointer has been around for a while, but now, you can click multiple times and it still won't let go. It also seems to do it a lot more frequently under certain circumstances, and it does seem to have something to do with rapidly trying to select multiple segments. I found that hitting Escape will get rid of it sometimes, and sometimes it will do it on its own. This is an extremely frustrating bug.

Indeed, that's why I gave my example of the fupped road that I only noticed because there was a user report about that nice highway 90º based detour through the forest

[mssusa]

I get the pointer stuck when my machine is overloaded. Especially when there are many segments in the view or there is a very long segment (10s or 100s of km long). This was also the case with the old version

Sent from my GT-I9100 using Tapatalk 2

[olestas]

Shortly speaking - in current state and form House numbering is hard and unusable. Besides you have to check which way the road goes (A-B) all the time. Automatic numbering breaks everything too. Even and odd numbers are put on both sides all the time and mixed.

[dgtlrift]

http://www.waze.com/wiki/index.php/Loop_road#Loops
Video at the bottom is pretty clear.

<delete>Tnx - this clears up the issue and explains it very well.</delete>

Correction - the directions on the wiki don't match up to what the editor has. However, I was able to stumble around and get the editing of the divided loop, but now I can't save. It gives me an error on the street split, but doesn't actually tell me what the issue is.

Cannot save changes

Screen Shot 2012-11-20 at 1.09.25 PM.jpg (115.4 KiB) Viewed 291 times

[daknife]

Often the only solution for such a loop is to delete it as one piece, save your changes and then redraw. It's one reason such loops are such a big pain is that once created in the system, you can't edit them, you can only delete them.

[davipt]

Often the only solution for such a loop is to delete it as one piece, save your changes and then redraw. It's one reason such loops are such a big pain is that once created in the system, you can't edit them, you can only delete them.

There was already on this thread a second solution for that:
- create a new segment connected to that loop, with the exact same street and city
- click on both segments and bridge them
- now you can edit the loop

[Mike-1323]

Often the only solution for such a loop is to delete it as one piece, save your changes and then redraw. It's one reason such loops are such a big pain is that once created in the system, you can't edit them, you can only delete them.

There was already on this thread a second solution for that:
- create a new segment connected to that loop, with the exact same street and city
- click on both segments and bridge them
- now you can edit the loop

I find that if I don't drag either the end point or a geometry node away from the recently bridged section then the save error appears. It is also necessary for me to save after bridging and pulling the bridged nodes apart or the save error occurs. So it is possible to fix loop segments but requires dealing with WME quirks.

[skbun]

This has been being discussed in various ways in other threads, but I wanted to put this here, so there's one place for Waze/the developers to look. (As a suffix to this, I'm not just putting these down as 'Look at how I can break the editor! I've actually had to fix real world cases of these problems.)

* City names with less than three characters are not rejected (Real world cases of such short names are exceedingly rare, but we get city smears all the time when people believe they've autocompleted a longer city name and haven't. See viewtopic.php?p=293748#p293748 (the problem) and viewtopic.php?p=295180#p295180 (possible solutions) for more on this.
* When the number of a city's streets is zero, a cityID is not deleted from the database (Related to above. If these don't get cleaned out, fat-finger errors can be reintroduced 'because that city DOES exist'.
* Spaces are not chopped from the middle of a city string (In other words, 'Federal Way' is not equal to 'Federal Way', but I can create a city with that name, and saving the latter will create a new CityID if it does not exist)
* Special characters are allowed in city names (e.g. $%,; ...) I suspect a couple select ones would want to be allowed like apostrophe, dashes...but as it is it looks like anything goes right now.
* 'The highlighted road is too far from the city it was added to' does not check altStreets for their cityIDs. I can add an alt street from anywhere in a state or country, in an alt street.
* In the United States, the state that the editor believes you are in is offered as a possible city. If I am in Washington, and start a city name with 'S', 'Washington' is given as an autocomplete. If I accept that, the cityID assigned is 100000040. I have to assume this is not what's wanted. (I've seen this sometimes, probably where a user was quickly tabbing around and didn't realize what they'd filled.) If there's a similar problem with countries on World, I can't see it because the infrastructure is being moved at the moment.
* I don't know how they got there, but there exist 'cities' in the database city names whose name is NULL or empty. I discovered this with the highlighter tool, when I saw two identical 'No City, State' entries in an area. One example is the altStreet on https://www.waze.com/editor/?zoom=7&lat ... s=61284239 whose cityID is 47991, not 999953. My guess is there are others on NA or world. I don't know if that might cause weird pollution behind the scenes.
* Please add more than six colors to the 'Cities' layer pallette. See viewtopic.php?p=293719#p293719 for more information.
* The Javascript console tells me when a new city has to be created. Can the user be alerted to it too, so they can be sure that they wanted to do that?

As always, thank you so much for reading!

[Timbones]

Skbun, you might want to send these issues directly to Waze Support...

via mobile

[skbun]

Skbun, you might want to send these issues directly to Waze Support...

I took your suggestion and did so. Thank you!