At 2012-04-14 22:10, Nathan Edgars II wrote:
In the U.S., a gated residential community usually allows anyone in who
has a legitimate reason to be there (e.g. visiting a friend, delivering a
package, repairing a TV). It seems that this fits access=destination as
well as private. Would it be rea
On Sunday, April 15, 2012, Alan Mintz wrote:
> At 2012-04-14 22:10, Nathan Edgars II wrote:
>
>> In the U.S., a gated residential community usually allows anyone in who
>> has a legitimate reason to be there (e.g. visiting a friend, delivering a
>> package, repairing a TV). It seems that this fits
On 4/15/2012 3:55 AM, Alan Mintz wrote:
At 2012-04-14 22:10, Nathan Edgars II wrote:
In the U.S., a gated residential community usually allows anyone in
who has a legitimate reason to be there (e.g. visiting a friend,
delivering a package, repairing a TV). It seems that this fits
access=destinat
Am 13. April 2012 19:44 schrieb John Sturdy :
> On Fri, Apr 13, 2012 at 12:10 PM, Martin Koppenhoefer
> wrote:
>> Prices on the other hand
>> are also of interest if you look for a hotel, but there is currently
>> no hope to keep this information up to date (and usually there are
>> lots of price
Am 14. April 2012 03:10 schrieb Steve Bennett :
> Possible values:
> surface=historic_cobblestone
> surface=preserved_cobblestone
> surface=rounded_cobblestone
I'd prefer to focus on the shape and therefore "rounded_cobblestone",
because other aspects like historic can be expressed with additiona
On Sun, Apr 15, 2012 at 4:08 AM, Martin Koppenhoefer
wrote:
>
> That's always useful, but it doesn't solve the issue of getting the
> data for a query like: give me all the hotels cheaper than 66 EUR for
> a double room with bathroom in this bounding box.
I'm not sure why you would attempt such a
> I'm not sure why you would attempt such a query with nothing but OSM
> data. There are multiple websites that specialize in this type of
> thing and are far better at it than OSM will ever be because they have
> direct interaction with hotels to handle the volatility in prices,
> room availabilit
At 2012-04-15 01:10, Nathan Edgars II wrote:
How would you distinguish an entry for visitors from an entry for
residents only?
name= or ref= or whatever else Mapnik was designed to render on a gate.
--
Alan Mintz
___
Tagging mailing list
Tagging@o
Btw. I think current Mapnik rendering renders addr:housenumber=* over
barrier=gate .
Meaning: if u tag em both u won't see the gate icon at all but only the house
number. .. Which imho is not ideal.
I'd love to see both rendered (when space allows) as both are of high
importance.
This is based
Le 15/04/2012 10:10, Nathan Edgars II a écrit :
On 4/15/2012 3:55 AM, Alan Mintz wrote:
At 2012-04-14 22:10, Nathan Edgars II wrote:
In the U.S., a gated residential community usually allows anyone in
who has a legitimate reason to be there (e.g. visiting a friend,
delivering a package, repairi
At 2012-04-15 05:38, Jaakko Helleranta.com wrote:
Btw. I think current Mapnik rendering renders addr:housenumber=* over
barrier=gate .
Meaning: if u tag em both u won't see the gate icon at all but only the
house number. .. Which imho is not ideal.
I'd love to see both rendered (when space all
I prefer tagging the addr:housenumber on building outline, landuse, parcel,
etc, too. That's clearly the right place for it.
The challenge, though, is that if/when one is simply "driving by" it's very
difficult to know especially in densly built areas where the # should be placed
-- even when l
Martin Koppenhoefer wrote:
> Am 14. April 2012 03:10 schrieb Steve Bennett :
> > Possible values:
> > surface=historic_cobblestone
> > surface=preserved_cobblestone
> > surface=rounded_cobblestone
>
>
> I'd prefer to focus on the shape and therefore "rounded_cobblestone",
> because other aspect
On 15 April 2012 15:15, Jaakko Helleranta.com wrote:
> I prefer tagging the addr:housenumber on building outline, landuse, parcel,
> etc, too. That's clearly the right place for it.
My personal mapping philosophy is to avoid overloading of information
on nodes and ways, so addr:housenumber alway
Nathan Edgars II writes:
> On the other hand, private says "Only with permission of the owner on
> an individual basis". But the owner is the homeowners association, and
> the individual residents can allow people in.
That's creating nits where they don't even exist! Owner is a more
complicate
Hi,
Am Mittwoch, 11. April 2012, 15:42:29 schrieb fly:
> I still do not get one major point which was totally left out on the first
> scheme. What actually belongs to a "point" and how are they tagged.
Especially
> on big crossings and roundabouts I always was confused (e.g. it might be
> possibl
Am 15. April 2012 12:22 schrieb Volker Schmidt :
>
>> I'm not sure why you would attempt such a query with nothing but OSM
>> data. There are multiple websites that specialize in this type of
>> thing and are far better at it than OSM will ever be because they have
>> direct interaction with hotels
On 15 April 2012 11:33, Toby Murray wrote:
> On Sun, Apr 15, 2012 at 4:08 AM, Martin Koppenhoefer
> wrote:
>>
>> That's always useful, but it doesn't solve the issue of getting the
>> data for a query like: give me all the hotels cheaper than 66 EUR for
>> a double room with bathroom in this boun
Am 15. April 2012 10:10 schrieb Nathan Edgars II :
> How would you distinguish an entry for visitors from an entry for residents
> only?
There is already an extension to the barrier class which allows to
mark the presence of a guard.
page: http://wiki.openstreetmap.org/wiki/Key:barrier:personnel
Am 15. April 2012 15:15 schrieb Jaakko Helleranta.com :
> I prefer tagging the addr:housenumber on building outline, landuse, parcel,
> etc, too. That's clearly the right place for it.
what is "right" and what is "wrong" depends on the circumstances. I
also prefer tagging addr:housenumbers to wh
On Sun, Apr 15, 2012 at 1:10 AM, Nathan Edgars II wrote:
> On the other hand, private says "Only with permission of the owner on an
> individual basis". But the owner is the homeowners association, and the
> individual residents can allow people in.
And so could the security company. But the HO
On 4/15/2012 6:30 AM, Alan Mintz wrote:
At 2012-04-15 01:10, Nathan Edgars II wrote:
How would you distinguish an entry for visitors from an entry for
residents only?
name= or ref= or whatever else Mapnik was designed to render on a gate.
That's only a solution if the gates actually have nam
Nathan Edgars II wrote:
> On 4/15/2012 6:30 AM, Alan Mintz wrote:
> > At 2012-04-15 01:10, Nathan Edgars II wrote:
> >> How would you distinguish an entry for visitors from an entry for
> >> residents only?
> >
> > name= or ref= or whatever else Mapnik was designed to render on a
> gate.
>
> Tha
Am 15.04.2012 23:51, schrieb John F. Eldredge:
I have seen gates that had number signs (1, 2, 3, etc., not a street
address). This number would logically go into the name tag.
If these numbers are, what I expect them to be, then it's not a name,
but a reference, and should go into the ref-Tag (
Peter Wendorff wrote:
>
> > Am 15.04.2012 23:51, schrieb John F. Eldredge:
> > > I have seen gates that had number signs (1, 2, 3, etc., not a
> street
> >
> > > address). This number would logically go into the name tag.
> > If these numbers are, what I expect them to be, then it's not a
> nam
At 2012-04-15 13:55, Nathan Edgars II wrote:
On 4/15/2012 6:30 AM, Alan Mintz wrote:
At 2012-04-15 01:10, Nathan Edgars II wrote:
How would you distinguish an entry for visitors from an entry for
residents only?
name= or ref= or whatever else Mapnik was designed to render on a gate.
That's
On 4/15/2012 10:39 PM, Alan Mintz wrote:
At 2012-04-15 13:55, Nathan Edgars II wrote:
On 4/15/2012 6:30 AM, Alan Mintz wrote:
At 2012-04-15 01:10, Nathan Edgars II wrote:
How would you distinguish an entry for visitors from an entry for
residents only?
name= or ref= or whatever else Mapnik w
27 matches
Mail list logo
