[Imports] Designated Wilderness area import

[Erik G. Burrows]

(Replying to list with my response to Ian)

>
>> Lastly, the import of boundaries into OSM is pretty dubious. Once we
>> import
>> any sort of data it instantly starts to decay. Boundaries and borders
>> are
>> especially bad because OSM is not (and should not) be the official
>> record
>> for these boundaries. Boundaries don't meet the "map what's on the
>> ground"
>> test that most contributors use.
>
> The boundaries exist though, and affect travel on the ground. For
> instance, many roads on the map, imported from the TIGER data seem to pass
> right through a designated wilderness area. It is only when you get there
> that you find the "No Vehicles" stake in the ground, forcing you to find
> another route. I think it makes a lot of sense to have the boundaries in
> the OSM database, with the intersecting node a point where access
> permissions of the way change, based on the usage restrictions of the
> area.
>
>
> --
> If you are flammable and have legs, you're never blocking a fire exit.
> -Mitch Hedberg
>


-- 
If you are flammable and have legs, you're never blocking a fire exit.
-Mitch Hedberg