Were you a bit overzealous here? Movements between K-96 and 127th Street East are not tolled.

The operator prefix is a convention we sometimes use where two different operators have nearby lines with the same name. I've left it unchanged in cases like the UP and BNSF Mojave Subdivisions, but only BNSF has a "Scenic Subdivision" in this area, so the operator prefix is not necessary.

Hi Bike 2 End,

Why was railway=owner_change removed from this node? This seems irrelevant to the MapRoulette task.

> If you're seriously questioning if my work on power lines is worse than orginal TIGER power lines, then that's extremely disrespectful.

Was it not disrespectful to do a mass deletion in the first place? It's obvious to anyone that that's against community guidelines. When you ignore community guidelines, you disrespect the whole community. We're all just reacting to being disrespected. I'm usually a very patient person, but I know when to set boundaries and I've stopped being nice with you long ago.

This is indicative of your reaction to criticism in general. You take all criticism personally, and you're not even willing to consider a situation in which your well-intentioned work may have done more harm than good. But what's alarming to me is your use of the phrase "both sides", despite not really addressing the concerns of the other "side". Is the entire OSM community the other side? Why are there sides?

You've been told before not to do massive changes without community input, but you did it again. It shouldn't be a huge surprise that people are upset. I'm tired of talking to a brick wall.

This is an insufficient response. You cannot unilaterally decide that your own edits are of high quality and that the elements you deleted were not. Furthermore, on OSM it is good practice to "keep the history" by improving the geometry of existing elements, rather than deleting them and tracing new ones.

Please do a full revert as requested.

Hi MetalCascade, hate to bother you again, but just a nitpick. Railroad signals and switches should stay separate - rarely is a signal in the exact same physical location as a switch.

As a railroad worker, you're probably aware that signals are typically located a little bit down the line on either side of a group of switches. I found signal assemblies beside the tracks at CP Summit in Trenton, so I added railway=signal next to them, along with the appropriate railway:signal:direction=*. Take a look: osm.org/edit#map=18/40.26554/-74.81068

Feel free to change it to usage=main or usage=branch if that matches how it's classified, but make sure you remove service=* when you do.

Hi again MetalCascade,

I noticed a couple of service tracks were tagged usage=main here. I know it's not totally clear in the tagging guidelines, but usage=main and usage=branch are meant to be mutually exclusive with service=*. Any crossover, siding, spur or yard track should not be tagged usage=main or usage=branch, or else it may disappear from renderers like OpenRailwayMap.

Thanks for adding such detailed information to Metro-North trackage otherwise. Keep up the good work!

usage=main removed here: osm.org/changeset/135164936

Hi MetalCascade,

It appears you merged the railway=junction at CP 424 with a railway=switch. This made a single node tagged railway=switch;junction which isn't recognized by OpenRailwayMap or any other renderers, causing it to disappear from the map.

Generally, we don't merge timetable points with individual features like signals and switches. I went ahead and undid this one for you: osm.org/changeset/135164650

Hi rayKiddy and thanks for contributing to this MapRoulette challenge! You weren't meant to edit any tracks beyond the one highlighted on MapRoulette. The track without service=* should have stayed that way, and this way should have been changed to service=siding: osm.org/way/215932551

I've gone ahead and fixed these two tracks. Let me know if there's anything that might be unclear in the instructions.

yannis323,

OpenStreetMap is not your personal sandbox. It's a collaborative project, with local and global guidelines created by consensus of a community of volunteers. I strongly recommend you read through the Wiki page on edit disputes, which are considered a form of vandalism: osm.wiki/Disputes

On OpenStreetMap, when we disagree with how mappers before us have defined tagging guidelines, we talk about it with each other before going through with major changes. I see that you've been replying on community.openstreetmap.org, and I encourage you to keep doing so. Please stick with one OSM account instead of creating more.

Because these are the outlines of underground excavated areas. All stations of the New York Subway are already mapped as nodes, and every time these outlines get retagged, it introduces duplicate stations.

My understanding is that highway=busway is for bus-only roads that are of high importance to bus passengers, and shouldn't be used for service roads that lead to a bus maintenance facility, for example. Roadways within bus stations are commonly tagged this way in the Netherlands, another major adopter of highway=busway tagging.

I picked the wrong time to do this—I'm leaving for vacation tomorrow. I'll respond to any more comments next week.

As for the Wikidata item, Q937694 represents the East Side Access construction project. Now that construction is over and it's in service, it needs a new Wikidata item for the Grand Central Branch anyway. So deleting it may have been a mistake, but it wasn't a big deal in this case.

Do you work for the LIRR? If so, it's important to make sure the information you're adding is copyright-compatible with OpenStreetMap. If the timetable has a copyright notice on it, please ask LIRR management or lawyers for written confirmation that it's okay to use it as a source for OpenStreetMap.

If you can get written confirmation, we'd love to see photos or scans of the relevant info. Copyright-compatible sources are hard to come by in railway mapping, so this would be immensely helpful for us all.

Also, could you please clarify what LIRR ETT SI GO 102 is, and where we can find it?

The Midday Yard Lead should just have that alone as the name.

How come the Midday Yard lead was changed from service=yard to usage=main?

The Morgantown PRT is not a guided busway. A regular bus with special guideway equipment should be able to traverse highway=bus_guideway. This fixed-guideway transit system doesn't support street vehicles.

While the Morgantown PRT isn't really a monorail, we use "monorail" on OSM as a de facto catch-all for any unusual urban or small-scale fixed-guideway transit systems. As Claudius mentioned above, this system was previously tagged as a monorail, and perhaps in the future we could devise a better tagging scheme for people movers, but right now "monorail" is the best we've got.

Could you please revert this to rubber-tired monorail tagging?

Hi Himké,

This changeset introduces a new value of network, CA:NS:H:toll. Currently, OpenStreetMap-Americana [1] renders shields for the network values CA:transcanada, CA:NS:H, CA:NS:T and CA:NS:R. Does this segment of Highway 104 have signage different from other Trans-Canada or 100-series highways in Nova Scotia? If so, I'd like to add it to our shield rendering inventory.

[1] https://zelonewolf.github.io/openstreetmap-americana/#map=9.11/45.4626/-63.6752

I see. Strange that the Alaska Railroad is included with the Anchorage Public Transportation Department. It should probably have its own page, though I guess that's something I can fix when I have time.