[Talk-us] Beaver dam? Wrecked bridge? Hallucinatory roads in TIGER?

[Harald Kliems]

Access tags seem inappropriate to me in this case. I would only tag the
last node as noexit=yes (http://wiki.openstreetmap.org/wiki/Key:noexit) as
a way of making clear that the trail does indeed end and hasn't just not
been mapped. Leave the rest to the users of the map -- maybe there is
actually a great spot for hunting/geocaching/sunbathing/beaver watching/
mushroom foraging at the end of the trail that you just don't know about.

 Harald.

On Mon Dec 22 2014 at 11:54:58 AM Jack Burke <burkejf3 at gmail.com> wrote:

> access=use_at_your_own_risk
>
> access=two_paths_diverged_in_a_yellow_wood
>
> access=choose_wisely
>
> access=plugh
>
> access=xyzzy
>
> ?
>
> -jack
>
>
> On December 22, 2014 10:06:15 AM EST, Richard Welty <
> rwelty at averillpark.net> wrote:
>
>> On 12/22/14 3:27 AM, Bryce Nesbitt wrote:
>>
>>   I've frequently wanted to map "the trails that peter out" for exactly
>> the reason you state.
>>
>>  The choices as a mapper seem wrong:
>> 1) Map the trail : thus encouraging use of a flawed route.
>>  2) Don't map the trail.  The casual map reader thinks OSM is missing
>> something.
>>
>>
>>  Possible solutions include a node type of "becomes indistinct", or
>> "dead end".
>>  How to mark the way is trickier.
>>
>> perhaps a new access tag..
>>
>> access=deprecated
>> access=not_recommended
>>
>> something else?
>>
>> richard
>>
>> -- rwelty at averillpark.net
>>  Averill Park Networking - GIS & IT Consulting
>>  OpenStreetMap - PostgreSQL - Linux
>>  Java - Web Applications - Search
>>
>> Talk-us mailing list
>> Talk-us at openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-us
>>
>>
> --
> Typos courtesy of fancy auto-spell technology.
> _______________________________________________
> Talk-us mailing list
> Talk-us at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20141222/5e62159e/attachment.html>