OpenStreetMap logo OpenStreetMap

Changeset When Comment
138690970 over 2 years ago

Hi,

Do these tracks no longer exist? "Private and inaccessible" tracks should not be deleted unless they actually no longer exist.

135096633 over 2 years ago

You're right, I looked back and didn't realize how many other changes there were. I've gone through and undid all the changes not related to the classification

138676190 over 2 years ago

No, they always need to be there, otherwise how will routers know how to get in and out of the parking lot?

138676433 over 2 years ago

Hi,

building:part areas can overlap building areas, that is what they are designed for. I'll revert this changeset for you, but please make sure you understand what each tag means before you delete things.

138676190 over 2 years ago

Hi,

Why did you delete all of the service roads in the parking lots? Are they no longer there?

135096633 over 2 years ago

Sure, but that's assuming that it was incorrectly added in the first place, which is something i'm not able to verify. My thought process was that if it is incorrect, then someone with local knowledge would come along and fix it.

135096633 over 2 years ago

it was a straight revert, so it shouldn't have added anything new. Do you have a link to a way where it wasn't there before?

138596809 over 2 years ago

Hi,

waterway=spillway has been deprecated for a while now, could you please change these to the standard, shown here: usage=spillway

Thanks!

138633412 over 2 years ago

Hi,

What is node/11051547342 supposed to be?

138544186 over 2 years ago

There's not currently a standardized way in OSM to indicate objects with varying height, some people use "incline" to try and work around it (see osm.wiki/Talk:Key:height#Varying_height)

138526113 over 2 years ago

Hi,

This changeset created a lot of ways with no tags, were you planning to do something with them?

138446678 over 2 years ago

Hi,

So for neighborhood boundaries, you can either do place=neighborhood like you did earlier, or you can do type=boundary, but you can't do both, you have to pick one or the other. It doesn't really matter which, although according to place=neighbourhood?uselang=en#How_to_map the boundary relation is more common.

138304112 over 2 years ago

Hi,

"height" values need to follow the OSM unit specifications (height=*?uselang=en#Examples), so "3 ft" is not a valid unit, it needs to be 3'. Could you please fix these? Thanks!

138544186 over 2 years ago

Hi,

"0 - 1 - 0" is not a valid value for height. Can you please explain what you were trying to show here?

138561947 over 2 years ago

Also, you have a lot of name fields with multiple values, which is uncommon. Could you please give your source for these changes?

138561947 over 2 years ago

Hi,

On way/1165957224, you put "voltage:primary" and "voltage:secondary" on this area, these tags can only be used on transformers. Could you please fix this? Thanks!

138507319 over 2 years ago

oops, that was supposed to be "remove duplicate power line

138343930 over 2 years ago

Hi,

Are you sure these should be in the name tag? Generally apartment numbers are either addr:housenumber or ref

138312433 over 2 years ago

Hi,

Thanks for your contributions! Please note that conditional restrictions are not valid inside the main access tags, they need to be in a separate tag, so for example "bicycle:conditional", motor_vehicle:conditional", etc. See osm.wiki/Conditional_restrictions#Traffic_modes for more examples.

Would you mind fixing these? Thanks!

138235463 over 2 years ago

Hi,

Thanks for your contributions, however, i've had to revert your changes because they were causing routing errors. The correct way to show that a road is dirt is to click on the road, and then go to the "Surface" field and choose Dirt (although you may want to look at the values listed here: surface=*#Unpaved, i think you probably mean to do "Compacted"), you shouldn't ever make a new road overtop of an existing one.