OpenStreetMap logo OpenStreetMap

Changeset When Comment
86680314 over 5 years ago

Smaller areas per changeset, please. The bounding box for this one encompasses all of Mexico in addition to parts of several US states and a big hunk of Central America.

87147461 over 5 years ago

Looks like this is mainly adding paths, why not "adding paths" for the changeset comment (which actually tells us this) instead of "misc edits" (which doesn't really tell us anything)?

87104927 over 5 years ago

Why does this edit stretch across multiple countries and the entire Atlantic Ocean?

87060217 over 5 years ago

Hi, and welcome to OpenStreetMap!

Overall this is okay for a first edit, however I did clean up some things, most notably the house outlines were not squared up. In iD you can use the "Q" keyboard shortcut to help with this. Also, highway=living_street has a specific meaning that is not normally found in the US; Liliana Glen Lane was correctly tagged as highway=residential which I have restored.

77350388 over 5 years ago

In the future, please do not map the same thing twice as both a node and a way. Also, ways tagged as building should conform to the building outline (and not the entire area of, say, a church).

86751483 over 5 years ago

What exactly is this change supposed to be? "1" doesn't tell me anything.

76357841 over 5 years ago

Thanks. I was about to change it, but thought maybe you had gotten it from an on-site survey so held off.

76357841 over 5 years ago

Hi,

What is your source for the address number on this building?

86463242 over 5 years ago

Should be "add data from notes 2223667 and 2223670"

85822902 over 5 years ago

I'm with Kovoschiz, this should have been made a relation which re-uses the existing coastlines. It could still (and should be) converted into one.

85051733 over 5 years ago

Looks good, congratulations on your first edit and welcome to OpenStreetMap!

84786973 over 5 years ago

My 15,000th changeset :-)

75015504 over 5 years ago

way/15290982 was self-intersecting and last modified by you before I fixed it. It's difficult to tell if it's always been like that, but I've seen quite a few of these kinds of mistakes from Amazon Logistics mappers.

As originally mapped before I fixed it, this way self-intersected twice at node/6831044056 and then again at node/151494057.

I don't object to having every service road in the entire US mapped, but I do take a bit of issue with problematic data that throws warnings and errors in validators (and may well cause other issues in programs that use the data).

75015504 over 5 years ago

Please do not loop roads back onto themselves. This triggers a warning for a self-intersecting way in JOSM's validator and other QA tools.

79639469 over 5 years ago

Please add service roads in different directions as separate ways. When the same highway=* tagged way loops back on itself, JOSM's validator and other QA tools flag this as bad data.

79966663 over 5 years ago

Please add service roads in different directions as separate ways. When the same highway=* way loops back over itself, JOSM's validator and other QA tools flag this as bad data.

74229393 over 5 years ago

There were a lot of misspelled cuisines I was cleaning up in this changeset, JOSM's apparently doesn't know what "creole" is, and I missed it when making the changes. I have reverted this unfortunate blunder just now.

83656741 over 5 years ago

Please do not abuse description=* by adding advertising copy.

83601534 over 5 years ago

Please save your work before switching areas. None of these changes are anywhere near Houston and yet this shows up in the history for Houston because the bounding box is so large.

83116587 over 5 years ago

What exactly is this edit? Bounding box stretches across 9 US states and part of Mexico, and comment says nothing useful.