A-ha. I see it now. I'm not used to Bing having the most up-to-date satellite imagery, so I didn't even bother to check. My bad. I went ahead and applied my changes again (with the correct path this time). The loop was drawn such that it reused nodes on the way back to the main path. This is considered a no-no and should have started with a new path. Thanks for the quick reply.

Hey Joe, can you tell me why you reverted my changes? Was there a specific problem with them, or did my changes get caught up in some larger issues? I'd like to understand before I reapply them because there are certain problems with 825077740 that need to be addressed and don't want my changes reverted again without good cause. Thanks.

Hi MojaveNC, a small portion of West State Street was deleted in this change. Was that intentional?

Hi AduptUniform, thanks for the additions to OSM. Are you using satellite imagery (or local knowledge) that is relatively new? The area I'm looking at has this going through a parking lot and I'm wondering why a living street exists in a parking lot. Has there been some construction there I'm not aware of? Thanks.

Thanks!

Is there any chance I can convince you to delete the way until you are ready to finish? I'm trying to keep the country free of the "self-intersection" errors and this one keeps showing up on the list. Thanks.

Hello KneeKnocker. Can you fix up the relation for this golf course? The course shouldn't use things like sandtraps and cartpaths as "inner" relations. It's like you are saying everything there is the golf course EXCEPT sand traps, those aren't part of the golf course. If you need some help with understanding inner relations better, let me know.

Hey Alan, can you take another look at way/29795501? Several nodes got deleted and now the polygon is a figure eight, which I'm guessing isn't what what intended.

There are some problems with this way. The first is that is intersects and overlaps itself in many places. The second is that it is untagged, so I have no idea what it is. Can you fix it up please? Thx.

Hi there. Can you take another look at way/780861268. It claims to be a room, but since it crosses over itself, it is impossible to tell if the inner box is a room, or if the outer box (minus the inner donut hole) is the room. It would be good if you could break that way up so that it doesn't do this (technically, ways aren't supposed to intersect with themselves). Thanks.

Hi Daniel. I'm not sure how or why this change was done, but I have reverted it to move the water way back to its original place. If you need some help with a change, let me know what you were trying to do and I'll see if I can help you get it done.

Hi there, can you clarify the tagging and geometry of way/815603054 ? It is listed as a gate, but I'm guessing it should be a fence or wall or something. Also, the geometry is drawn in such a way that it doubles back on itself, which isn't allowed. Can you fix that as well? Thanks.

Hi pwhite. You might want to take a look at node/1787821171#map=14/39.6212/-79.8103
It looks like a large set of points were accidentally shifted a large distance. And since the changeset involves hundreds of changes, I'm not sure if reverting it would even work.
Can you take a look into fixing things up?

Are you familiar with the sidewalks in this area? One in particular is drawn in such a way that it doubles back on itself (nodes A-B-C-B-A) and also includes an "incline" tag. I tried to fix the fact that it shouldn't double back on itself, but then the question arose of which way the incline actually points (A-B-C or is it C-B-A) if that makes sense. Is this something you can fix because you might have local knowledge? Thanks (and thanks for the contributions).

Thanks for the additions, but you might want to know that you shouldn't but anything under the name tag that isn't the actual name of the feature. For instance, way/773920089 shouldn't have a name at all.

Looks like way/562085214 got messed up during your change. Can you take a look at correct it? I'm not sure what the intent was here. Thanks.

Hi Richard,
Something is wrong with way/312771439, but I'm not sure what it should look like. Any chance you can take another look at it and replace things where they should be?
Thanks.

I suspect that you're right, and that way should be corrected.

There were two problems with the way. The first was that it overlapped itself and made reuse of nodes incorrectly. The second is that it is using the same nodes as another path incorrectly.

I fixed the first problem, but didn't work on the second problem.

Can you take a look at the area around way/342802541? Something got messed up during your editing and you might be better suited to clean it up. Thanks.

Thanks for taking care of this. Much appreciated.