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.

I reverted this change since it had too many problems to try and fix manually. A road was created using one long way that was overlapping the existing way. It also zigzagged over itself, which isn't allowed. And names were abbreviated and apartment name was listed for the street name. Let me know if you need help creating a route, but I think everything is already there if you just want to tag existing roads.

Hi Peter, are you aware that there are a bunch of duplicate address nodes in this changeset? See node/3386481617 for example. Several in that area. Maybe more as well.

Why is this tagged as a nuclear explosion site? Are you saying that when I get my car washed at Bubbles Hand Wash nearby, they are using radioactive water?

Oops, changeset comment is wrong. Picked the wrong one for a pick list. It should read "fixing up ways that intersect themselves".

Does this powerline really loop back onto itself?? way/283435914

Hi @Vangaurd. I did some work to clean up this area and thought I'd share some tips with you to prevent this type of mapping error in the future. When mapping out a big network of roads like this, it is critical that you don't double back on the road and reuse points in an effort to make it all with a single path. What you need to do is create a new highway/road/path for every junction and every spur road. That way, validation checks won't set of alerts and need to be remedied. Happy mapping. -- b-jazz

Thanks for contributing to the map @Skreiss. I've made a few modifications to your changes that you might be interested in. Somehow the boundary path was broken into several segments. I went ahead and joined them all into one "way". I also adjusted the boundary according to some better satellite imagery and tagged the new version with the garden type and gave it a name (there is no need to add the two points, you can tag the entire boundary with that information). Once again, thanks for improving the map.

Hi birdsiieye. Thanks for contributing to the map.

I'm confused though. Is it Super Burrito or Super Taco? I wouldn't really say that one is the English translation of the other.

This is vandalism and will be removed.

There are a few problems here:
1) address information shouldn't be used as the "name" of a feature
2) addresses shouldn't be abbreviated "NE" -> "Northeast", "Ave" -> "Avenue"
3) you didn't get the address information from Bing aerial imagery. If you got it from a survey of the area, great. If you got it from a copyrighted source, you put OSM at risk of copyright infringement.

Please correct these mistakes.

(Assuming that DuhMapMaster5000 and RomanoLuingine are the same person.) You're edits and contributions to the map are very appreciated, WHEN they follow guidelines and aren't meant to advantage you when playing PokemonGo (which your original comments clearly indicate). You make it sound like you're doing a great service to the community, but you are doing a lot of bad things at the same time. When you enclose your house with a way and call your house and yard a "park" and then create dozens of paths on your "park", that is not helping the community. You spent weeks of your life making the map your plaything. You can't blame those in the community from wanting a map that is high quality.

Thanks. I needed a good laugh today.

Please don't make up names like "Crop Circle" for features that are unnamed.

From name=*: "name=* tag is supposed to contain solely name, not to describe the type or location of the object"

Also, please include changeset comments more descriptive than just "stoof".

Thanks.

Thanks for the submission to OpenStreetMap. I've tweaked a few of the values to be more inline with OSM standards and naming. You might want to move the node closer to a building that a customer might approach when visiting though instead of the middle of the yard.