[Tagging] public_transport=platform rendering on osm-carto
winfixit at gmail.com
Fri Jun 22 15:07:53 UTC 2018
For access restrictions we had started by using psv=yes, but I guess few
people will read that as public services vehicle and another problem with
that is that is apparently includes taxis as well.
Personallly, I see a big difference between a way tagged as *=platform and
a node with that tag.
On a way it means the area where passengers are supposed to stand and which
usually is a bit higher, or explicitely created for those passengers. You
know it, when you see it.
On a node it means waiting area, where you can expect to be picked up by a
public transport vehicle. There could be pole, there could be a platform
(which can be drawn next to it), there could be a shelter, a vending
machine, a screen announcing when the vehicle will come, garbage cans,
benches. Or there could be nothing there at all, but the convention that
buses will alight and pick up passengers at that spot.
The platform node groups most of the properties of the bus stop, so it
makes sense to add it to the route relations. I'd like to see that it can
remain a node over the lifetime of such a bus stop. And for all the other
amenities near it, we can have separate objects.
This works just as well for bus stops as for tram stops and indeed, some
tram stops are served by buses as well.
it's that 'platform' node that gets bus=yes/tram=yes etc.
For the platform way/area mode of transport is far less important.
Maybe the platform node should have been called something else. Especially
since stop_position contains the word stop and some new mappers consider
that to be the correct tag for tagging the bus stop.
So yes, words are confusing and the way they have become defined in
OpenStreetMap even more so.
Op vr 22 jun. 2018 om 16:53 schreef Johnparis <okosm at johnfreed.com>:
> Heh. Another example of the imperfectibility of language.
> Neither the GTFS specification nor the NetEx standard envisions any
> distinction between boarding-only and alighting-only points (or mixed ones,
> for that matter), and I have never encountered any bus route where such a
> distinction was made. Since the wiki is supposed to be descriptive, I
> have amended it accordingly, but of course there will still be other
> precisions to be made.
> I think Thorsten's description of the magic transfer is very accurate.
> One of the advantages of PTv2 over PTv1 is the ability to tag mutlimodal
> platforms. Tram platforms are frequently multimodal, but others can be as
> well. The tags used (not controversial) are public_transport = platform +
> <mode> = yes, for one or more mode tags. The controversy referred to in
> another thread is that this duplicates (some of) the access=* mode tags, so
> there is a potential confusion between bus=yes when it is intended to be an
> access tag and bus=yes when it is a modal tag for public transport.
> I have previously gone on record as supporting "access:bus=yes" when
> access is meant, but I don't think that's very practical, and in the real
> world the conflict doesn't exist. (I suppose an alternative would be
> "public_transport:bus=yes" for such cases, which might make things simpler
> for parsing software, and maybe for editor software, but makes no
> difference otherwise that I can see.)
> On Fri, Jun 22, 2018 at 2:35 PM, Martin Koppenhoefer <
> dieterdreist at gmail.com> wrote:
>> sent from a phone
>> > On 22. Jun 2018, at 13:53, Johnparis <okosm at johnfreed.com> wrote:
>> > It's not always a waiting area, btw, sometimes it's reserved for
>> leaving the transportation device.
>> the definition for public_transport=platform is “The place where
>> passengers are waiting for the public transport vehicles.”
>> if the area is not used for waiting, you cannot tag it as platform, you
>> could use something like boarding_area
>> Tagging mailing list
>> Tagging at openstreetmap.org
> Tagging mailing list
> Tagging at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Tagging