[Tagging] Ferry routes as relations?
joseph.eisenberg at gmail.com
Sun Mar 24 23:34:13 UTC 2019
This issue was recently brought up on the Openstreetmap-Carto Github page:
it was noted that piers that were tagged as part of a relation were
being rendered incorrectly.
Some of the maintainers suggested that the actual path of the ferry
across the water should always be tagged as a linear way, so that this
alone is needed for most rendering and most routing functions, while
the relation can include other features without problems. This is also
what is done for tram tracks or railways; the path the train follows
is a linear way, but the route is a relation.
Are there people who think it is necessary to map the actual
over-water path of the ferry with relations, or should the wiki page
be clarified to recommend that this be tagged as a linear way?
On 3/24/19, Martin Koppenhoefer <dieterdreist at gmail.com> wrote:
> sent from a phone
>> Am 24.03.2019 um 04:19 schrieb marc marc <marc_marc_irc at hotmail.com>:
>> if the building is the plateform (where passager wait until the ferry is
>> there), it's usefull for routing : route the pedestrian to the platform
>> with a pedestrian profil, switch to the associated stop_position, route
>> to the desired stop_position with the vehicule profil, switch to the
>> associated platform and continue pedestrian routing
> I would expect a ferry route to go from the departing port to the
> destination port (or small station, ferry routes cover quite different
> features, from short pedestrian connections over a river or lake, to big car
> ferries over the sea), eventually by passing through via ports, but I would
> not expect or suggest to add buildings and other landbased infrastructure
> (e.g. waiting areas, ticket offices, customs, ...) to the route. The latter
> are part of the port, not the route.
> Cheers, Martin
> Tagging mailing list
> Tagging at openstreetmap.org
More information about the Tagging