I'd like to dispute your reverting of this changeset. I do not think it was the right decision despite the reasons you provided. I would still consider these to be "more a tram stop than a railway halt" because of their ≤300 meter proximity between each other, their alignment to the curb on separate streets, and their lack of a clear entrance and exit or exit.

The wiki page for `highway=motorway` does not list speed limits as a criterion.

This tunnel is apart of an interstate, and all interstates, turnpikes, and freeways are supposed to be tagged with `highway=motorway`.

👍

It is also worth noting that distances between stops is one of the more-important qualities for differentiating between light rail systems and streetcar systems in general.

Thank you for asking.

The tag `railway=tram_stop` can be correctly applied "where the halt resembles more a tram stop than a railway halt." I deemed this to be the case due to the following criteria:

- the lack of an enclosing structure
- the lack of a dedicated platform (aside from the sidewalk)
- the short distance between the stops

In any case, if you're going to vandalize maps, this link might interest you:

https://maps.google.com/localguides/

</joke>

Lmao

Perhaps, I just copied from the GTFS feed.I'm not sure if I'll continue to do that, however.

Do not apply `highway=busway` to these ways until *AFTER* support for it has been added to the Standard Tile Layer!

There are people who currently rely on the Standard Tile Layer to render busways, and applying `highway=busway` will cause them not to render.

Yes, I acknowledge that this would be considered tagging for the renderer, but I'm not about to tell the individual's whose workflow I broke by initially applying `highway=busway` that they need to wait for Carto to be updated before they can use their software again.

I apologize for the trouble I have caused you and your team.

Well, here's what's going on as of right now:

I am still pursuing trying to get `highway=busway` to, but the developers of the standard tile layer would rather not render it until it gains a level of large-scale adoption. Until then, busways tagged with `highway=busway` will remain invisible.

This puts me into a catch-22, where it is difficult to adopt a tag if the standard tile layer does not render it.

In other words, there is no set date for which `highway=busway` will render properly in Carto. Furthermore, there is no set date that `highway=busway` will work with the software that you are using.

Because of this and for the sake of practicality, I have decided to revert my own changesets.

I'm not sure what you are asking.

Note: initial comment is incorrect. *Low platform* stops were mapped as `railway=halt`.

Note: initial comment is incorrect. *Low platform* stops were mapped as `railway=halt`.

railway=halt

See here: railway=tram_stop

Here is the relevant issue:

https://github.com/gravitystorm/openstreetmap-carto/issues/4226

Please do note that it would be incorrect to replace `highway=busway` with `highway=service` or another value to force them to render.

Hello.

The standard tile layer has not yet been updated to support the new tagging scheme, and instances of `highway=busway` will not render until it does.

The reason why it might have "vanished overnight" is that the cached map tiles in your browser were probably cleared and replaced with the updated tiles.