2010/5/20 Tyler Gunn :
> Lol, now just think if we micro-mapped each tree in the parking lot you
> could get your GPS to determine the spot that is likely to be in shade for
> a large part of the day, keeping your car nice and cool! :) Ok, too far
> perhaps.
height and diameter are still missing
On Thu, May 20, 2010 at 8:50 AM, John Smith wrote:
> On 20 May 2010 22:46, Tyler Gunn wrote:
> > Lol, now just think if we micro-mapped each tree in the parking lot you
> > could get your GPS to determine the spot that is likely to be in shade
> for
> > a large part of the day, keeping your car n
On 20 May 2010 22:46, Tyler Gunn wrote:
> Lol, now just think if we micro-mapped each tree in the parking lot you
> could get your GPS to determine the spot that is likely to be in shade for
> a large part of the day, keeping your car nice and cool! :) Ok, too far
> perhaps.
Some people do map i
> Rather than permitted=*, why not use parking_use=*? That would then be
> consistent with your proposed relation. Though "permitted" is more
> general and might be able to be generalised to other features...
Or perhaps something like "permitted_parkers"; I don't think there's
anything wrong with
> Agreed, although the situations in which it's not so clear are the ones
> where OSM could really get an advantage over the competition. So many
> times
> I'm directed by Google Maps to a location quite a distance away from the
> parking lot I'm trying to get to. It's especially annoying when t
On Thu, May 20, 2010 at 7:36 AM, Tyler Gunn wrote:
>
> > Access=private works fine, then (along with access=public
> > andaccess=permissive). Preferably with an additional tag (or relation)
> > withsome indication of who is allowed to park there.
> > Maybe access=customer isn't needed after all.
On Wed, May 19, 2010 at 5:36 PM, Tyler Gunn wrote:
> I think in most circumstances it is probably pretty clear which business a
> parking lot is intended for though.
>
Agreed, although the situations in which it's not so clear are the ones
where OSM could really get an advantage over the competi
> Access=private works fine, then (along with access=public
> andaccess=permissive). Preferably with an additional tag (or relation)
> withsome indication of who is allowed to park there.
> Maybe access=customer isn't needed after all.
How about something like:
access=private
permitted=patron/pe
Yes, exactly. I couldn't have put it better myself!!
From:
tagging-boun...@openstreetmap.org[mailto:tagging-boun...@openstreetmap.org] On
Behalf Of Anthony
Sent: 19 May 2010 21:36
To: Tag discussion, strategy and related tools
Subject: Re: [Tagging] FW: Parking for businesses..
On Wed, May
