Reverted. Please use more meaningful comments than "buses" so other mappers know what you've done and why.

osm.org/changeset/103218671

Reverted. Please use more meaningful comments than "dc area" so other mappers know what you've done and why.

osm.org/changeset/103218509

Reverted. Please do not merge stop_area relations that are already contained within a stop_area_group relation.

osm.org/changeset/103218306

Reverted. Please do not merge stop_area relations that are already contained within a stop_area_group relation.

osm.org/changeset/103218270

Reverted. Please do not merge stop_area relations that are already contained within a stop_area_group relation.

osm.org/changeset/103218120

Hi goldenking05,

What is your source for the translations of these street names? It seems unlikely that these streets in small-town Indiana would have signage posted in Arabic and Chinese.

Did you do these translations yourself?

No big deal. Each state has its own conventions for how it signs roads. ODOT is pretty consistent in signing them as "State Road" and mappers in Ohio have come to the consensus that refs should match signage. Likewise in Indiana.

I have already reverted the fictional railway features. See osm.org/changeset/102436763

Track numbers are not names. I don't think they belong in the name tag. That said, it's a pretty small issue and I don't care if you re-add them.

If you're looking for a renderer that surfaces track numbers, check out OpenRailwayMap.

So here's what it looks like happened. I had been using JOSM to review MBTA rail and I must have thought I had finished, so I moved on to reviewing Pittsburgh's light rail. Turns out I had some unsaved changes in Boston and accidentally rolled those into the same changeset.

The changes in Boston seem to be only tweaking layer=* and level=* tags. The changes in Pennsylvania are aerial review of the T line between Library and Washington Junction, for example, changing service tags, or moving switches to more accurate locations.

At any rate, I no longer have the same workflow and now avoid having two different areas loaded into one JOSM layer, so this kind of mistake won't happen again.

Well that's weird. Thanks for calling this to my attention; I'm taking a look

Hi Darrell,

This isn't quite how light rail tagging is done. A node should not have both `public_transport=stop_position` and `railway=station`. What needs to be done here is the existing `railway=tram_stop` nodes should be retagged with `railway=stop`, and a new node with `railway=station` (and the other implied tags) should be placed at the visual center of the station.

Do you want to take care of this or should I go ahead and do it?

-Clay

changeset comment should actually say Seattle Streetcar

Well, `service=spur` remains in wide use and there is no indication on the wiki that it has been deprecated. It strikes me as odd that such a heavily used tag with a generally clear definition would be deprecated all of a sudden.

Could you find the discussion and link it here?

Where was the discussion on this deprecation? As a rail mapper that is news to me.

IMO, the segment of railway in question should certainly be `service=spur` or `usage=industrial` at best. It is not a main track of a branch line.

Reverted in changeset 100662307.

Why did you undo my revert? This is not the agreed-upon way to tag temporally restricted railroads. The Escondido Subdivision is already mapped thoroughly and correctly. The source for this is derived from the California Rail Schematics document [1].

Please do not change any more tags along the Escondido Subdivision without first consulting the talk-us@ mailing list [2], the tagging@ mailing list [3], or the #rail channel in the OSMUS Slack [4].

Best regards,

Clay

[1] PDF download: https://dot.ca.gov/-/media/dot-media/programs/rail-mass-transportation/documents/f0009927-ca-rail-schematics-a11y.pdf

[2] https://lists.openstreetmap.org/listinfo/talk-us

[3] https://lists.openstreetmap.org/listinfo/tagging

[4] https://slack.openstreetmap.us/

I upgraded most streets that pass through stoplights to at least tertiary. In retrospect, that particular street probably shouldn't have been upgraded and I probably wouldn't have done the same today. Goof on my part.

It doesn't matter whether you authorize it or not. That has no bearing on whether other people may add a driveway and buildings to OpenStreetMap.

If you don't want these structures mapped, you are free to demolish them.

No, it's in the correct place.

Reverted in changeset 99695147. Tagging the track segments that support freight trains as railway=light_rail is incorrect because those particular tracks are built to a higher standard and support heavier trains. Light rail trains (route=light_rail) may travel on railway=rail in certain cases such as this one.