Volker,
There was a rather inconspicuous sentence at the end of
http://wiki.openstreetmap.org/wiki/Key:bridge linking to the additional
"bridge:..." keys. I've reordered the introductory material in that page
somewhat to make it more clear that these additional options exist for
adding detail abou
concluded there are areas where behavior guidelines (see links below)
introduce paths not for general public but for climbers.
(Tom thanks for the links)
therefore we definitely should use:
access=destination
This single tag might be sufficient. And an other tag would just
simplify rendering...
A
Tobias Knerr wrote, on 2014-08-08 12:55:>
> access=destination makes sense. That second tag isn't established,
> though, nor is the concept of "explaining the details" through a
> destination=* subtag.
At least it helps the fellow mapper why the access was tagged so,
and is easier than a note=
A
agreed
That means producing a revised bridge wiki page that combines all info.
Who does the work?
:-(
On 8 August 2014 13:07, Tobias Knerr wrote:
> On 08.08.2014 11:35, Richard Z. wrote:
> > My idea was
> > * abandon bridge=swing in favor of bridge=movable which could provide
> > subtyping
On 08.08.2014 11:35, Richard Z. wrote:
> My idea was
> * abandon bridge=swing in favor of bridge=movable which could provide
> subtyping if someone really needed it.
We already have an approved proposal that provides this subtyping:
http://wiki.openstreetmap.org/wiki/Proposed_features/Bridge_t
> Am 08/ago/2014 um 12:47 schrieb k4r573n :
>
> In my opinion these paths shouldn't be used by default and we need a tag
> to ensure routers and renders have a possibility to do so.
>
> access=destination
> destination=climbing
>
> seams to be the best possibility
If there are legally bindin
On 08.08.2014 12:07, Tom Pfeifer wrote:
>>>access=destination
>>>destination=climbing
>
> Just to reinforce the opinion, "access=destination" forbids through
> traffic,
> in this case general hikers taking a short cut. This is what we want,
> and using
> an established tag for this purpose
On 08.08.2014 11:51, Martin Koppenhoefer wrote:
>> Am 08/ago/2014 um 11:31 schrieb Dan S :
>>
>> I'd vote for the first one (destination). I'm not keen on the third
>> one since climbing=* would need to become widely recognised as an
>> access tag, which doesn't feel very scaleable.
> I agree mostl
> Am 08/ago/2014 um 11:35 schrieb "Richard Z." :
>
> My idea was
> * abandon bridge=swing in favor of bridge=movable which could provide
> subtyping if someone really needed it.
> * introduce bridge=suspension bridge=simple_suspension
I suggest to also look at previous discussions on this t
> Am 08/ago/2014 um 11:31 schrieb Dan S :
>
> I'd vote for the first one (destination). I'm not keen on the third
> one since climbing=* would need to become widely recognised as an
> access tag, which doesn't feel very scaleable.
I agree mostly, from these suggestions it seems the best altern
Dan S wrote, on 2014-08-08 11:31:
2014-08-08 10:21 GMT+01:00 k4r573n :
Tom - yes you understood me right :)
Thanks
There is no one who check whether your a climber or not or want to have
a fee - but these path are not aimed to be used by the general public.
I admit that access=customers doe
On Thu, Aug 07, 2014 at 05:58:01PM +0200, Volker Schmidt wrote:
> Good old Wiipedia helps:
>
> http://en.wikipedia.org/wiki/Bridge#Types_of_bridges
>
> http://en.wikipedia.org/wiki/Swing_bridge
> http://en.wikipedia.org/wiki/Suspension_bridge
wikipedia is clear on that but if you look at "swing
2014-08-08 10:21 GMT+01:00 k4r573n :
> On 07.08.2014 12:05, Tom Pfeifer wrote:
>> If I understand Karsten correctly, the limitation is not about payment,
>> it is to limit the number of people using this path. This would be
>> typical for climbing crags in
>> http://wiki.openstreetmap.org/wiki/Cons
On 07.08.2014 12:05, Tom Pfeifer wrote:
> If I understand Karsten correctly, the limitation is not about payment,
> it is to limit the number of people using this path. This would be
> typical for climbing crags in
> http://wiki.openstreetmap.org/wiki/Conservation
> areas.
>
> A typical example is
14 matches
Mail list logo