I was going through some older notes and found Note: 3632211 | OpenStreetMap, Note: 3632214 | OpenStreetMap and Note: 3632212 | OpenStreetMap
Which all say:
Unable to answer “Does this stop have tactile paving?”
Platform edge Doors instead
I can’t find a way to tag this though, looking at the wiki nor taginfo combinations.
Does anyone know of a way?
First of all, this response doesn’t answer the question yet. Stations with platform doors should have tactiles. The difference would be whether they are along the edge only, or fully provided along the walking route. In any case, it should still be =yes first. There have been proposals drafted for further distinguishing.
You should first look at Tag:railway=platform_edge - OpenStreetMap Wiki . It is the exact solution for showing the boarding side of a side platform; and proper method for island platforms, rather than an arbitrary pair of =platform areas splitting it into halves. This needs to be drawn first, before considering platform doors.
The problem is there are many types of platform barriers. Traditionally, it is full-height platform screen doors vs open-top to half-height platform gates. There are lifting variants of the latter. Nowadays most prominently in Japan, there are various designs that are not quite “doors” to suit non-standardized trains and platform structural strength on non-metro systems for mainline and private railways. They can be horizontally sliding bars; and lifting bars, or even ropes only. Platform screen doors and platform gates can even be fully moving, for all the door positions of different trains. All these needs to be considered when devising. In theory, I’m of the opinion they should use barrier= .
One may wonder whether door= can already be used. However, it is used on points, and together with entrance= / exit= etc points. It can’t be directly applied to =platform_edge lines. Of course, you may take advantage of tagging freedom to intrepret it as whether “doors” as present on the =platform_edge . This isn’t all that bad. In detail, it is a combination of screens and doors, if someone wants to add door positions etc. The flaw is it can’t handle gates and other barriers, which you may choose to ignore here. Mapping train platforms subareas and markers
For a more proper solution with barrier= , currently there are 30 barrier=platform_gates | Tags | OpenStreetMap Taginfo , and 20 barrier=platform_doors | Tags | OpenStreetMap Taginfo mainly from Europe and Japan. You can use the latter on the =platform_edge .
There are some other solutions, 48 platform_protection | Keys | OpenStreetMap Taginfo (all =door ) , and 19 platform_screen_doors | Keys | OpenStreetMap Taginfo . The latter doesn’t seem to consider platform gates and other barriers. The former is too unspecific, as there are platforms with fence or walls but no doors, and what about active fall detection sensors with warning triggering emergency stops? Peculiarly, platform_protection= is in fact inflated by being used on the door positions. OpenStreetMap
Either case, barrier= is a standard feature that can always be added on on the =platform_edge . These two are more worth considering on the =platform , =station , and =stop , requiring more support.
A caveat is sometimes platform barriers aren’t aligned on the =platform_edge . On Touhouku Shinkansen local-stopping stations, the platform gates are set back with a significant spacing for extra safety from the very high-speed passing trains. Another note in addition to fully moving platform door or gates is Sanyo Shinkansen has extremely wide opening ones, nearly half the car length, again to fit different train set door positions.