Automatic geometry editing must DIE!

[Elgirts]

I was about to do my own complaining about Automatic geometry too, however, It now looks like there were some changes to cartouche as of this morning (Wednesday 1/20/10). I will hold out complaining until after I reset some of the issues I have, and observe the new algorithm mentioned above :

Well it has been changed extensively (and I advise that you please monitor this area to double check assuming you corrected it already) as we've altered the algorithm to bypass segments and areas which have been modified manually, giving the manual correction significant more weight than was previously given.
As such I assume that these changes have occurred before the algorithm change was made (about a month ago we upgraded the server for that).
Another update is going to be uploaded this week (or beginning of the next) to correct a bug where the automated process sometimes partially 'straightens' a curved segment.
These 2 changes should prevent such reoccurrences.

[friedlinguini]

Actually that only makes sense if we're sure that errors aren't correlated. If, for example, the presence of a mountain on one side of a road consistently causes GPS tracks to appear 30 feet to the west, then the tracks might agree, but still be wrong. I'd say let the Lock option extend to road geometry and intersection topology. If a road is locked, then only manual changes should affect it.

[gibby71]

I think that it should not automatic update unless at least 50 different people have driven over it and they all agree on the path.

[pottedmeat]

Well it has been changed extensively (and I advise that you please monitor this area to double check assuming you corrected it already) as we've altered the algorithm to bypass segments and areas which have been modified manually, giving the manual correction significant more weight than was previously given.
As such I assume that these changes have occurred before the algorithm change was made (about a month ago we upgraded the server for that).
Another update is going to be uploaded this week (or beginning of the next) to correct a bug where the automated process sometimes partially 'straightens' a curved segment.
These 2 changes should prevent such reoccurrences.

I call tomfoolery. There is horrific geometry editing that JUST took place in my area that DESTROYED intersections. I can't see how any of your algorithms should produce anything like what shows up. I showed you guys some of the mess when you did your screencasts, and you said the same thing back then about how it should be fixed now.

My favorite:

[Shorty-CM]

Changes in cartouche have nothing to do with server processes.

I've complained about this for a LONG time now. If everything worked perfectly with our phones then this feature would be awesome. But, our phones don't work perfectly, and often have drifting GPS data to report to the server. And this is how we get all our goofy geometry adjustments. The fact that our phones aren't high-dollar professional GPS receivers with huge antennas on the roof of the car pretty much means this feature should be REMOVED FOREVER. Nothing should ever be straightened. Nothing should ever be altered. Our phones are never going to be excellent GPS receivers. And not every user puts them in an optimal place in their car. GPS errors will always be plentiful. Tweaking the feature to "behave better" isn't the answer. Just get rid of it altogether. It isn't helping anything.

[Shorty-CM]

Take any area, particularly where there are curves and especially 90-degree intersections with other curves (ramps) around them. Turn on GPS tracks. Do you honestly think the feature will help, ever? It won't. Our devices aren't capable enough for the feature to do what it should. I agree that the theory is sound. The problem is our devices are not, and will never be, accurate enough to make the theory work in practice.

[Shorty-CM]

Something like that would definitely make more sense. It makes no sense whatsoever that a single person driving through any given area can cause the server to make spaghetti out of orderly streets.

[Shorty-CM]

At any rate, it doesn't do any good right now. And anything even remotely resembling what it does now is unacceptable.

[sketch]

Okay, it looks like I got a little too comfortable. When I checked some stuff near my house for fun — which I had assumed would be all squared away, like it was months ago when I fixed it the first time — I noticed it was all wrong.


, and


The automatic process is a nice idea, but it's flawed. Very flawed. I have not seen one occasion in which it has provided a good result. Turn it off.


This ramp, as it is shown in the photo, would have been correct five months ago. It's not anymore, which is why I changed it five months ago — it now connects to the service road for construction purposes, and will do so for a while longer. But again, the server messed everything up.

Turn it off. Please.

[The Fej]

Well it has been changed extensively (and I advise that you please monitor this area to double check assuming you corrected it already) as we've altered the algorithm to bypass segments and areas which have been modified manually, giving the manual correction significant more weight than was previously given.
As such I assume that these changes have occurred before the algorithm change was made (about a month ago we upgraded the server for that).
Another update is going to be uploaded this week (or beginning of the next) to correct a bug where the automated process sometimes partially 'straightens' a curved segment.
These 2 changes should prevent such reoccurrences.