@GITNE, can you provide a link to your original interaction with @tguen where you had a civil conversation? Apparently I’m entering in the middle of the conversation and it has taken a very wrong turn and isn’t what the community wants to see in how we interact with each other. Thanks.

Hey there rivermont,
Can you take a look at my diff (changeset/89883891#map=16/33.9102/-78.3776) which untangles some crazy waterways. I'm not sure what it is supposed to look like, but your recent fix did something weird. I'm not sure what you're trying to accomplish, so I took a wild stab at it. Maybe you could provide additional insight. Thanks.

I'm not sure where the taxiway is supposed to end on the following way: way/326479982, but as it is, it is looking a little odd at the NE corner.

Hello Scrapper81, can you take another look at way/454773823? It seems to have been accidentally shifted while other elements were shifted and it doesn't look correct. Thanks.

Hello Wolf, do you know what the purpose of way/837453838 is? It has no tags, is the length of the state of R.I. and appears very close to the border. I don't think it should exist. I'm not sure if there are others similar to it, but I noticed this will looking at some other things.

Hello Oregon. I'm trying to understand the reason that the long ways were split up into small road segments when you were adding stop signs. (way/522775123 for example)

There shouldn't be any need to break them up as far as I'm aware, but maybe you know some reason that I haven't considered yet. I'd like to get them all combined back into a single way (when appropriate) but don't want to break anything you've worked on.

Is there some need for a single road to be made up of dozens of small segments?

Thanks.

I've removed what I can only assume is vandalism on the "VALOR" building. If I've done this in error, please let me know how.

Hi grant977, first off, thanks for all of your great contributions to OSM with all of the golf course mapping you've done recently. However, I've noticed a lot of QA errors are being raised for some of your ways, specifically nodes that have the same exact lon/lat values. I see from this changeset that it looks like the iD editor might be flagging those as well (warnings:close_nodes:vertices). Are you seeing these errors when you edit? It would be great if you could take a minute to clean them up before you submit so that others won't have to later. If you're not seeing these, we should probably file a bug against iD to make sure they are more visible. Thanks!

Thanks! Those building shapes look a lot more sane now. :)

Hello Ohio,

You might want to go back and look at your import in this changeset (and possibly others using the same methodology). There are a ton of unconnect nodes being dropped all over the place. And for a possibly related reason, some of the house geometry is making some strange non-rectangle zig zags around. Check out the following node in a sea of other unconnected nodes: node/7791950986

Hi there jwneptune,

Roads are already mapped for that stretch and they have appropriate speed limits defined. If those speeds are incorrect, you should modify the existing ways instead of adding additional ones along with the old ones. Also, make sure you include the units along with the speed (e.g. "35 mph") instead of just "35". I've gone ahead and deleted the two roads you added in this change. If there are multiple speed limits for the road, just split the way in two at the speed limit change and set the resulting sub-segments to the new limits.

Hi Knikitha, Do you know what happened here? I've seen a couple of these parking aisles today that are splayed out across buildings and existing aisles in ways that are highly unlikely. Is there some systemic error that can be fixed here? Thanks.

Sorry for not being specific in my original comment. I usually remember to mention an exact way url. This is the way that no exists and I'm not sure the incline tag is correct: way/820207768 If you could take a look and correct/verify it, that would be great. Thanks.

1) It was a discussion on the OSM US Slack channel. I have a vague recollection that I only mentioned it because JOSM complained about them overlapping, but I'm not 100% sure about that.
2) If it were me, I'd just mark up to an existing building, but not intersect it.

Anyway, it's not worth arguing over. I just thought I'd mention it and see if you're amenable to adjusting your mapping slightly.

Say Hi to Benny for me.

I conferred with others in the community and they agreed that when outlining woods like these that the way should include just the base of the trees and not their canopy so that we avoid having woods and buildings overlap each other.

Hello Doctor,
This change did something funky with a park and I'm not sure what it should look like and what you're trying to map. Can you take a look at way/565581544 and adjust as appropriate? Thanks.

Hi Dillon, a separate issue from what user_5359 mentioned is that you tried to define a residential area, but you only drew a single line instead of a polygon. I would fix it, but I'm not sure where you wanted to indicate the residential area is.

FYI, the woods that you added overlap with a house/building that added a year ago. I'm assuming that the house is still there, but I didn't dig too deep. Here is the house in question: way/652523803

Hi Stephen, did you actually change anything in this changeset? Is there an error in your workflow, or a problem with JOSM or OSM? Just curious.

Hi Juergen. Thanks for all of your contributions to OSM in the past day or two. I've noticed a slight problem with how you stop drawing a way (path) and I thought I'd mention it so that you can correct how you do it in the future. Say you want to draw four nodes: A, B, C, and D. I notice that you click A, then B, then C, then D, and then back to C to stop drawing a line. The correct way to stop drawing is to just click D a second time. I'm cleaning up the cases I've found of this, so there is nothing you need to do to fix previous contributions. Thanks.