Ok, what do you think about the following options then:
* route:scope with local (urban?), regional, national
(long_distance?), international
* public_transport:stops with non_stop, limited and many (applies
mostly to buses and trains)
* public_transport:service with train_replacement, p
If a barrier is used as a plant_box instead of a bollard . ->
https://forum.openstreetmap.org/viewtopic.php?id=60006
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
Le 6 octobre 2017 18:34:30 GMT+02:00, marc marc a
écrit :
>Le 04. 10. 17 à 17:44, Yves a écrit :
>> Now if it's bad, you can trust the contributors not to use it.
>> Also, you can take time to explain your argument against in the
>> discussion page, it's a wiki ;-)
>
>if an individualist contr
Le 04. 10. 17 à 17:44, Yves a écrit :
> Now if it's bad, you can trust the contributors not to use it.
> Also, you can take time to explain your argument against in the
> discussion page, it's a wiki ;-)
if an individualist contributor makes both mass changes on the wiki to
mark tags that bother
2017-10-06 13:00 GMT+02:00 Michael Reichert :
> Some people (including myself) started using service=* for train routes
> about two to three years ago. The service=* tag was part of the Oxomoa
> Schema. Why not using this tag with different values for bus routes?
by looking at the tags in use o
Hi Martin,
Am 2017-10-06 um 09:51 schrieb Martin Koppenhoefer:
> what I forgot to conclude: as the values are mostly new, and it’s not an
> access restriction, I’d use a different key for this, rather than bus you
> could use something like route:scope or route:type etc.
Some people (including
On 06.10.2017 03:22, Dave Swarthout wrote:
IMO, this sort of information does not belong in the OSM database. If a shop owner is expert in the
field, fine; let them say so in a website specific to the business and we can add the "expertise"
information in that way. OSM cannot be a database of al
what I forgot to conclude: as the values are mostly new, and it’s not an access
restriction, I’d use a different key for this, rather than bus you could use
something like route:scope or route:type etc.
Cheers,
Martin
sent from a phone
> On 6. Oct 2017, at 02:12, Mikolai-Alexander Gütschow
>