"wild" platform - the opposite of a built, dedicated platform structure
 
An example for both:
 
wild - a road with a grass strip and a PT post stuck in the ground,
people have to use the grass strip; over time it may have an "upgrade"
using fine gravel to compensate for the dirt revealed by the grass stepped
down
 
dedicated - a platform made of paving_stones or other solid material, may
be equipped with additional street furniture (shelter, tactile paving, bins, etc.)
 
You may find wild platforms (i.e. non-dedicated ones)  in secluded areas
with very low passenger frequency.  Profit-wise such stops are usually
inattractive to a company, so unless they are tax sponsored they often
are a target of consolidation.  An analogy is a wild path, e.g. when people
"shortcut" park meadows - it's a path for usage frequency, not because
it was built for or dedicated to this purpose.
 
 
Tagging wild platforms is addressed by PTv2.  As pointed out previously
platform nodes may be used to indicate these. 
 
 
Greetings
cmuelle8
 
Gesendet: Freitag, 30. März 2018 um 08:56 Uhr
Von: Johnparis <[email protected]>
An: "Tag discussion, strategy and related tools" <[email protected]>
Betreff: Re: [Tagging] Still RFC — Drop stop positions and platforms
I don't think a tag is needed for "wild" platforms. As already noted, public_transport=platform applies to nodes already. And shelter=yes/no or bench=yes/no can be added if that's the infrastructure Christian means. (Not clear to me what exactly a "wild" platform is.)
_______________________________________________
Tagging mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/tagging

Reply via email to