Hi Richard,
Something is wrong with osm.org/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 osm.org/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.

Hello Importer. Is there any chance you can pause your import and fix some data problems? I see many (most?) of the street addresses aren't properly expanded (i.e "N Main Street" instead of "North Main Street"). I also see a lot of the ways have a node that is duplicated (something like 1-2-3-3-4-5) with the 3 duplicated. It would be great if you could fix those before importing any more, and it would be even better if you could go back and clean up the data already imported. Let me know if you need help.

Hello Importer. Is there any chance you can pause your import and fix some data problems? I see many (most?) of the street addresses aren't properly expanded (i.e "N Main Street" instead of "North Main Street"). I also see a lot of the ways have a node that is duplicated (something like 1-2-3-3-4-5) with the 3 duplicated. It would be great if you could fix those before importing any more, and it would be even better if you could go back and clean up the data already imported. Let me know if you need help.

Hi Stephenbell93, thanks for the contributions. I'm certainly no expert on creating bus lines, so take this with a huge chunk of salt, but I think that bus lines are supposed to be built by using existing paths (roads) and assigning them to a relation. Also, when creating any path, you should know that they aren't supposed to cross over themselves or double back on themselves. If you need to, you should use a new path anytime this is needed.

Hi bruceem. Something went wrong with your building in this change. There are only two points for the building, instead of a minimum of four to define a rectangle. Would you like to go back and fix it up?

Hey Greg! Thanks for all of the additions to OSM. I wish my town had someone as dedicated as you filling in all of the buildings. I just thought I'd let you know that the editor that you use (iD) has a feature to "square" the buildings. Since most houses/buildings are built with right angles, after you are done drawing the outline, you can hit the letter 'Q' on the keyboard and the corners will all get squared. It makes houses/buildings look really nice.

Reverted in osm.org/changeset/80107574

Hi @ohiomapper. Indeed I did make this change and it is problematic and I will revert it. However, there is something wrong with putting two nodes at the same location with different data. For example, passing through that entrance doesn't simultaneously put you in two different units. So those nodes should be moved to different locations or different levels, or at the very least, use the same node with `name=822;824` or something along those lines.

Hi fcphantom,

Can you reduce the number of points in these circles? There is no need to have 2000 nodes to represent a round building. Even 100 is probably too much.

See osm.wiki/Generalization for some info on it.

Thanks.

FYI,
osm.org/way/703521442 is broken. Would you like a chance at cleaning it up? It doesn't make sense as is.

I believe your comment said that I added or modified an address, but that is incorrect. The bot edited another tag in the object and your changeset comment (that I agree with in general) shouldn't have been made since my (bot's) change didn't actually touch the address.

Oh, the houses shouldn't be part of the boundary relation either. Otherwise walking into someone's home would take you out of the neighborhood, which would be odd.

You've named every house in the neighborhood as "Summerlake". AFAIK, that is not the right use for the "name" tag on a house. Also, some of the paths in the area I've noticed double back on themselves, which isn't allowed. Any chance you could clean things up there? Thanks.

Thanks @Wulf4096! I have created a bug (https://gitlab.com/b-jazz/https_all_the_things/issues/11) and will look into it.

This way really ought to be deleted. It doesn't match what is on the ground (no separate physical path exists) and it is causing lots of validation errors. It violates one of the first tenets of mapping: map what is on the ground.

If there is truly a cycleway that needs to be represented, it would be better to do this with a route relation of by adding bike lane tags to the appropriate routes. But a separate way is just wrong as far as I can tell.

Do any of you object to me deleting this?

I think between what @DFH808 did and what I did, the way is pretty accurate now.

I didn't place it there. I just changed a tag after the fact. You might want to ask the original mapper (osm.org/changeset/71534748) the question instead. It looks like you corrected the location in the latest update. Thanks.