OpenStreetMap logo OpenStreetMap

Changeset When Comment
175782475 3 days ago

Hi Truck-thin, I've reverted the demolished railway sections added in this changeset here: changeset/176072502

Former rail beds can be mapped in OSM where they are still visible features of the modern landscape, but where new construction other landscape modification has happened this data is out of scope for OSM. See: osm.wiki/Demolished_railways

174583169 about 1 month ago

Hi. Yes although in theory a data consumer could hopefully obtain the street name for a sidewalk from the nearest highway, so far they have not done so. As a result there is a movement to add `name`=* to sidewalks. `street:name`=* is an alternative to this emerging practice that is more semantically accurate. The name applies to the whole street, not just the sidewalk.

street:name=*

Several recent forum topics: https://community.openstreetmap.org/t/should-sidewalks-and-crossings-be-unnamed/136661
https://community.openstreetmap.org/t/what-problem-is-this-named-sidewalk-creating/136889

172264093 2 months ago

Hi, thanks for your contributions. It looks like you accidentally dragged a node off a river area here and it created a weird spike of water encroaching on the neighborhood 😀. Just a heads up to be careful of that. I've fixed it here:
changeset/173416967

171926973 2 months ago

Hi matthewfecica, I have to agree with ZLima12 here. A quick look at the Cranberry Lake Preserve web page makes it quite clear this is a leisure=nature_reserve and not a leisure=park. Please read and understand the wiki pages for these tags before making any more changes like this. This preserve should be reverted to leisure=nature_reserve and I'm guessing the others you've changed to leisure=park should be as well.

https://parks.westchestergov.com/cranberry-lake
leisure=nature_reserve
leisure=park

165978480 7 months ago

Hi Aleksandar, it looks like starting in this changeset, and then in a series of others following, you removed `natural=coastline` from a lot of ways and then added it to others going through open water. This moved the location of the coastline significantly and halted global coastline processing. It looks like these changes may need to all be reverted to resolve this. This is currently being discussed on the forum:

https://community.openstreetmap.org/t/130749

https://community.openstreetmap.org/t/130412

163367887 9 months ago

Revert changeset here: changeset/164055987

163367887 9 months ago

Hi Truck-thin,
I've reverted the classification changes to Routes 127 and 289 from this changeset because they did not align with the Vermont highway classification guidelines. Feel free to reach out if you'd like to discuss.

osm.wiki/Vermont#Highway_classification_in_the_general-purpose_road_network

osm.wiki/United_States/2021_Highway_Classification_Guidance

146013631 9 months ago

Aaand of course I was accidentally logged into my import account. The above message is from me.

158953471 about 1 year ago

Hi Udar,
Just popping in to say that crossing:signals= is a perfectly valid in-use tag. It's fine if you think it's redundant, but many other mappers don't so please don't delete it. Personally, I always tag both crossing:markings= and crossing:signals= while often omitting crossing= because the values of that tag are interpreted inconsistently.

149579123 over 1 year ago

Hi again edops, yes please slow down and engage in conversation with the rest of us. If you don't want to use slack you can also participate in this forum thread which you have already been invited to via changeset comment and private message from me.

https://community.openstreetmap.org/t/111201

I applaud your enthusiasm for place classification, but other mappers are not taking kindly to some of your edits.
You do need to discuss such major changes with other mappers in the local community. If we do not hear back from you we will be forced to get the Data Working Group involved.

osm.wiki/Data_Working_Group

149322259 over 1 year ago

Hi edops,

This and other changesets have broadly reclassified settlement place names across Vermont in a manner that is inconsistent with previous place classification discussions among Vermont mappers and generally does not align with the accepted meanings of these tags. As such, I've reverted these changes and invite you to discuss with other local mappers on the forum before making further place name classification changes.

Forum topic: https://community.openstreetmap.org/t/111201

Revert changeset: changeset/149395884

149321376 over 1 year ago

Hi edops,

This and other changesets have broadly reclassified settlement place names across Vermont in a manner that is inconsistent with previous place classification discussions among Vermont mappers and generally does not align with the accepted meanings of these tags. As such, I've reverted these changes and invite you to discuss with other local mappers on the forum before making further place name classification changes.

Forum topic: https://community.openstreetmap.org/t/111201

Revert changeset: changeset/149395884