Some more discussion on the topic is taking place on the US Slack instance: https://osmus.slack.com/archives/C029HV951/p1540853913092600

From the OSM Inspector wiki page: "So while it might not be a "proper" solution its certainly pragmatic to make the segments shorter. Another problem is due to the current implementation of the OSM API: When requesting all objects inside a bounding box only nodes in this bounding box and ways having a node in this bounding box will be returned. (This is done because it is more efficient.) So the longer the segments are and the smaller the bounding box the bigger the chances that some object will not be returned from the API call and might not appear on the map."

Another reason for breaking these up is that any accidental moves of a way (to 0,0 for instance) would be masked by all of the other long segments that exist. If we segment the long ways, any mistakes that are made will be more likely to stick out rather than be obscured by many other valid long ways. So my argument is that you need to "clean" them all up in order for mistakes to stand out.

Also, thanks very much for the discussion. I appreciate the feedback.

IMHO, that makes complete sense for straight, smaller ways. But for massive ways it becomes a problem when the nodes that define the way are far outside of the bbox that you are querying for. You aren't aware that a way is traversing your work and that might cause an issue. It's one of the reasons OSM Inspector calls it out as a problem.

Thanks for contributing to OpenStreetMap. Just to let you know, there is a handy feature in iD that will "square" the buildings that you create. After you draw a circle, press 's' to make all of the corners be 90 degrees. Or you can right-click on the area and select the "Square" function that way.
Thanks again. We hope to see you continuing to add features to the map.

Blargh. Chose the wrong changeset comment again. Sorry. Should say, "Removing duplicate nodes".

Oops, got out of my rhythm. The changeset comment should be "Removing some duplicate nodes" and the source is "OSM Inspector"

For instance, see v1 of way/636085409 and nodes 5998800364 and 5998811585.

I noticed something interesting about the buildings that you are creating. They often have a node in the middle of a straight segment and that node is duplicated in place which triggers validation errors in OSM Inspector. You might want to see if you can prevent this from happening in your editor or double check after you create buildings and clean them up.

Removed way that has no basis in satellite imagery and no response from creator.

Thanks for submitting improvements to the map! I think you are the first person I've seen get the opening_hours format correctly on their first edit! :)
One feature you might want to know about is the tool that can "square" the corners of a building. Since most are built with 90 degree angles, pressing 's' after you draw a rectangle will make sure all the angles are 90 degrees.

Please find a less offensive way to test proper attribution of OSM next time.

Hey there Morgan. I love (some of) your movies. :)

Welcome to OpenStreetMap. Thanks for your contributions. I noticed that one of your "buildings" actually connected to a road, which triggers some validation warnings that you probably weren't aware of. As a rule of thumb, you want to make sure buildings surround just the physical structure of a building and not things like yards and driveways and such.

FYI, there are a couple of problems with this path that you uploaded. The first is that every single point was duplicated. I'm assuming there is a problem with your import. I went ahead and deleted every duplicate node. But you might want to be aware so that you don't repeat the mistake on your next import if you use that same workflow. The second problem is that the path doesn't seem to match reality. I don't see anything like it from satellite imagery. It doesn't mean it's wrong, just that it doesn't look quite right.

Hi @EuleKC. If this isn't really a building, and clearly it isn't, it shouldn't be labelled as one. Maybe you are looking for a place=suburb designation instead. That would be a more appropriate tag.

FYI, there were 3 footways on the Neches St. side of the church. They were all overlapping and causing validation errors. You might want to verify your kml files don't include duplicate data before importing.

FYI, I deleted way/382794751 since it seems way off from where it should be. Not sure if this indicates further problems or is just a one-off.

Thanks for contributing to OSM. I removed this "path" though since it is just along a street and there is no actual path there. (and it loops around a couple of times which makes it cross itself at certain points). Maybe you are trying to indicate sidewalks. If that is the case, you might want to do it by using satellite imagery instead of uploading gps tracks. Also, does the "preschool" in the area have a real name? You might want to use that instead of just "preschool" on the node. LMK if you have any questions. Happy to help.

Thanks for contributing to the map @natehome123. I noticed a tiny "mall" among your edits. I'm guessing that was a mistake. Here is the way: way/635838225

Oh, I see the "problem". Two nodes sit so close to each other than the house numbers were smashed together. Turns out it is a multi-unit building and the nodes are two different numbers. There is plenty of room in the area though to spread them apart so that you can see them. For example:

node/3386481618
node/3386481617

sit on top of each other and you can only see one of them at the max zoom level. So, not duplicates, just sitting on top of and obscuring each other.