I spent some trying yesterday trying to unravel the changes and there are just too many. If you are willing to fix things, that would be very much appreciated. I would strongly suggest avoiding the built-in editor for changes of this magnitude. The best program to use would be JOSM. It takes a little effort to learn, but it isn't as scary as some people make it out to be. You don't need to be a master at JOSM in order to start making changes, so start small and make "small" changes. If you have any questions about it that DuckDuckGo can't answer, feel free to reach out and I'll do what I can to help.

And back to the original problem with that straight line segment, it isn't the straightness that is the problem so much as the fact that the boundary gets crossed over by the straight line as points were deleted. There are Q/A tools out there that set of alarms when ways like this get created/modified and that is how I was made aware. Since it sounds like you will be editing this area, I'll make some slight changes to those two ways so that they don't cross over themselves and hopefully you will come around and clean them up.

Sorry if my original note scared you. I don't want to destroy anyone's work. But sometimes reverting complex changes is the best way to get the map back to some level of "correct" (and yes, I get that it wasn't perfect in the first place).

Good luck, and again, feel free to reach out.

I guess the blunt answer is, if you don't know how to make changes that don't affect other existing features (deleting shared nodes), you should probably not do it until you have the tools and understanding how to make the changes safely. I wouldn't be able to just delete the straight parts since that would delete the entire way (a line segment that is potentially part of a set of lines that define a feature/area). I think the best thing to do would be for me (or someone else) to delete all of your additions and restore the original wood back to its original state. This can be difficult and potentially even possible though, which would result in the entire features (yours and theirs) being wiped off of the map and starting from scratch.

> no technical solution has been found

https://www.youtube.com/watch?v=lOTyUfOHgas

Seems pretty easy to me. Editors could simply have a feature that pops up a warning when someone is about to submit a globe-spanning changeset. I submitted a changeset in my early days that spanned the globe. I didn't realize it was a problem. I submitted one in the recent past knowing full well that it shouldn't be done, but I didn't realize I was doing it. Just letting the user know they are about to make one would go a LONG way to solving the problem.

This has been deleted as it is not the proper use of OSM.

Something got very damaged with this way and I have no idea how to fix it. I'm not pointing fingers at The Moth, but maybe they know what is up. Take a look at the very long straight lines in the definition of way/387946454 and way/387946352
Is there a chance you could go back and see what got messed up and replace it back to the way it was? Thanks.

People need to stop blaming the users for edits like this. Yes, it is inconvenient, but get over it, it happens. Pressure the tools to put up roadblocks when someone tries to create a changeset that is this large. Especially when it is a new user doing it. Let's stop criticizing new users and start criticizing the maintainers of iD/JOSM/etc.

way/1058080189 and several others cross over themselves. When ways cross themselves, it is assumed that segments are all at the same elevation, but as this pipe probably doesn't have a 4 way intersection, it should be broken into two pipe segments with a `layer=0` and `layer=1` tag added as appropriate. layer=*

A couple of comments on this GPS upload in case you want to improve future uploads.
1. The number of points is too high. There is no hard and fast rule for the proper number of points, but this is definitely too many. You might want to resample the data before uploading.
2. You should clean up the data for spots where you take a rest because the GPS jitter will drop a bunch of points zigzagging around where you rest and that doesn't represent what is on the ground.
3. Some QA tools (JOSM in this instance) is saying that the elevation data for every single point is too precise. No need to have 3 digits of precision when GPS can't measure the thickness of a grain of sand.
4. "UNMAINTAINED" isn't in the *name* of the trail. It belongs in some other tag. The wiki might help you find a more appropriate place for that bit of information.

Have fun riding and thanks for the map contributions.

Should Menifee be promoted back to a city now? Wikipedia lists it in US cities over 100,000 population.

Fixed in changeset/122567682. I'd love to know how JOSM put a 13 year old node into a stream that was being worked on across the world. Maybe @pfg21 could elaborate.

Bon-Vue is how all of the county tax lots show the name. The city guy I spoke with is going to submit a request to have the signs replaced/modified to include the dash.

Hello NewSchool19,

I'm making some edits to some of your contributions in the area and thought you might want to know what I've changed so you can avoid the problem in the future. I see that several ways have been reusing nodes and portions of the way in an effort to make one long continuous path. There is a rule that says you shouldn't do that so I'm breaking up the ways where I see that. Hope this helps. If you have any questions, please feel free to reach out.

way/1065311883 makes some crazy turns and then crosses itself. Unless there is some magic four way intersection pipe fitting there, the way should be fixed in whatever way is appropriate.

Crap.

Hello eugsah,

I'm trying to solve some bike routing issues and I notice that you set Polk St to be bicycle=designated, but I don't think that is correct. There are no sharrows and there are no sensors in the road at stop lights and no pedestrian crossing triggers that are reachable from a bicycle in the road. How did you come to the conclusion that this was "designated" instead of simply "yes" or allowed?
Thx.

faceboob??

are you sure about that website url?

Oops

The irony being that I "created" that way 3 years ago, when all I actually did was split up the existing way to add speed limits. :)

Main St is divided through here and you can't drive straight across it like way/1058880490 implies.

Dzięki za notatkę. możesz chcieć ulepszyć swój program, aby wstrzymywać komentarze, jeśli ktoś wprowadzi edycję, która nie obejmuje pól adresu. Nie zmieniłem adresu, więc komentarz ginie.