Since you are using a tiny node on a physical object that has non-trivial width and length, maybe it would be okay to separate them a few inches. The nodes would still represent the location of the objects correctly and would keep the Q/A tools from alarming. I don't think putting them on different layers or levels would quiet the tool, but I haven't explored that in depth.

What are these spokes within the "arc reactor"? osm.org/way/1083262397

There are some OSM Q/A tools that don't like it when two nodes share the same exact lat/long coordinates. One case of that was pointed out recently with osm.org/node/9926139654 being one of the nodes. Is it possible to separate these two nodes by some minute distance? Thanks.

I have reverted the change and made the fix that I intended to make. Looking at it anew, there are problems that you might want to look to rectify. The farmland extends oddly to a point in the northwest corner (osm.org/node/9916211431). This doesn't match satellite imagery (not to mention that nobody would want to manipulate a tractor into a tight area like that. Conversely, the wooded area looks to extend farther east and should probably be reflected as such. I don't know much about forest=wood usage, but to use it for a thin line of trees probably isn't the best use. But like I said, I'm no expert in the use of that tag.

The thing that was wrong with it that brought it to my attention was that the two eastern nodes of the way were reused by the way, such that the way had a piece that was zero width. Looks like the way was inadvertently deleted when I went to correct that error.

You are able to continue with the way however after you fix up your nodes. And JOSM should be warning you of the validation errors before you submit the changeset, so you are able to fix the issue at that point. If you need help, feel free to reach out.

Please make sure that houses with 90 degree angles are drawn with 90 degree angles. iD has tools that will square up your area if you right click on the area.

I use OSM Inspector from Geofabrik: https://tools.geofabrik.de/osmi. I know that KeepRight has a similar feature, but doesn't update as frequently as Geofabrik's QA tools. KeepRight is at https://www.keepright.at.

The list of all affected ways:
osm.org/way/1066238220
osm.org/way/779579382
osm.org/way/1063014746
osm.org/way/1038312894
osm.org/way/1058936463
osm.org/way/1071383335
osm.org/way/779579392
osm.org/way/1071379773

What's up Doc?

Can you take another look at the changes you made recently. Several ways around osm.org/way/779579382 were edited in such a way that it looks like some shared nodes were moved and that drastically changed the shape of some areas that are obviously unintended.

osm.org/way/1077274315 and several other forest areas that are drawn here are oddly shaped, don't match satellite imagery and overlap with other forest areas. Was there some accidental movement of nodes? Could you take another look and make sure it represents what is on the ground? Thanks.

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 osm.org/way/387946454 and osm.org/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.

osm.org/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. osm.wiki/Key: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.