On Wed, Mar 22, 2017 at 5:13 PM, Dale Puch wrote:
> The tag seems functionally correct, it is paid access. Fee might apply,
> but it seems more like it applies to the park itself, not the roads, or you
> end up creating a very similar but specific use tag just for parks.
>
The tag seems functionally correct, it is paid access. Fee might apply,
but it seems more like it applies to the park itself, not the roads, or you
end up creating a very similar but specific use tag just for parks.
As for routing, if the distance around is far enough, and the road
size/speed
Functionally, I would argue that payment-required (or pass-required) park
entries are effectively the same as a toll, anyhow. I'll give the example
of driving to Cooke City, Montana, in the winter—the only way to get there
with a wheeled vehicle is via Yellowstone National Park's northwest
On Tue Mar 21 21:17:04 UTC 2017 Shawn K. Quinn wrote:
>On one hand, I can agree withe the principle behind re-purposing of this
>tag. On the other hand, I can see it being quite possible this is going
>to throw some routing programs for a loop when "avoid tolls" is selected.
I never thought of
On 03/21/2017 11:56 AM, OSM Volunteer stevea wrote:
> I tagged barrier=toll_booth on numerous "exit lanes" at the parking
> facility at San Diego International Airport. I also used this tag
> at a state park near me which has exactly the same sort of entrance
> attendant you mention collecting
Thanks for the feedback, Steve! That's kinda what I was thinking, but
wanted another opinion.
--jack
On Tue, Mar 21, 2017 at 12:56 PM, OSM Volunteer stevea <
stevea...@softworkers.com> wrote:
> I tagged barrier=toll_booth on numerous "exit lanes" at the parking
> facility at San Diego
Are the various "toll" related tags appropriate for park entrances where
you have to stop and pay a fee? For example, most state parks in Georgia
have a "parking fee" that you have to pay to an attendant when you enter
the park, so it seems appropriate to tag the collection point as
7 matches
Mail list logo