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.

@utible: looks like you (or your data) had some search/replace problem and changed "Cloverdale" road to "CoveRoadale" road due to the "rd" in "cloverdale". I'm fixing this one, but letting you know in case you can discover others that have the same problem.

Great. Thanks Adam.

It looks like you combined some river segments for the Deschutes River and undid @emem's work in changeset/48638796. Would it be possible to possible to leave the river segment split so that there are fewer nodes. There are a couple of reasons: one being that the limit is 2000 nodes per way, which it is approaching, and the other is that OSM Inspector complains about anything over 1900 because it becomes problematic when someone wants to refine the segment but hits that 2000 nodes limit.
I can argue both sides that it seems a waste to split it before it hits 2000, but I don't see much of a harm in doing the split in advance so a newer mapper doesn't have to worry about it. Would love to get your input.

How does an "EU UPLOAD FILTER" have anything to do with this duplicate node? Or is that just the comment that gets reused by some tool to make deleting the node easier?
Thx.

Thanks for the contributions to OpenStreetMap. I'm not sure if you noticed, but the corner area of that building already is tagged as "India House" with essentially the same information as the node that you added. I'm guessing your new node is redundant and can be deleted.

Thanks for the contribution to OpenStreetMap. Is the "d" in "Layton Refridgeration" accidental?