Hi,
there is a proposal for vending_machine at
http://wiki.openstreetmap.org/index.php/Proposed_features/vending_machine
but there has been no vote for it. Is someone already using it?
I have several cases where I have post boxes to map, with their stamp
selling machine. Currently I have not yet
On Tue, Sep 2, 2008 at 2:36 PM, Pierre-André Jacquod
<[EMAIL PROTECTED]> wrote:
> Currently, I have never seen a stamp vending machine without its post
> box. That is why I intended to mark these with something like:
>
> amenity=post_box
> vending_machine=yes
>
> Is there a (strange:-) country wher
On Tue, Sep 02, 2008 at 03:30:26PM -0400, Adam Schreiber wrote:
> On Tue, Sep 2, 2008 at 2:36 PM, Pierre-André Jacquod
> <[EMAIL PROTECTED]> wrote:
> > Currently, I have never seen a stamp vending machine without its post
> > box. That is why I intended to mark these with something like:
> >
> > am
Hi,
vegard a écrit :
>>> Currently, I have never seen a stamp vending machine without its post
>>> box. That is why I intended to mark these with something like:
>>>
>>> amenity=post_box
>>> vending_machine=yes
>>>
> There will be a lot of such cases of things with dual use. I did send
a ma
On 7 Sep 2008, at 19:08, Pierre-André Jacquod wrote:
> Hi,
> vegard a écrit :
Currently, I have never seen a stamp vending machine without its
post
box. That is why I intended to mark these with something like:
amenity=post_box
vending_machine=yes
>> There wil
Shaun McDonald wrote:
The problem with this is that none of the editors support having
duplicate key values, even so the 0.5 API supports it. The 0.6 API
will not support duplicate key values.
I think the support of duplicate keys is a very much needed feature and
I personally would drop it
> Currently, I have never seen a stamp vending machine without its
> post
> box. That is why I intended to mark these with something like:
>
> amenity=post_box
> vending_machine=yes
Hi,
if you have not seen a stamp vending machine without a post box nearby,
that m
On Sun, Sep 7, 2008 at 10:53 PM, Norbert Wenzel <[EMAIL PROTECTED]> wrote:
> Shaun McDonald wrote:
>
>> The problem with this is that none of the editors support having
>> duplicate key values, even so the 0.5 API supports it. The 0.6 API will
>> not support duplicate key values.
>>
>
> I think
On Mon, Sep 08, 2008 at 06:40:59AM -0700, Karl Newman wrote:
> >
> > So personally I think duplicate keys would be the easiest and best way to
> > tag such double-uses.
> >
> > Norbert
> >
>
> Just make two different nodes, each located closest to the amenity
> concerned. There's nothing that make
Karl Newman wrote:
Just make two different nodes, each located closest to the amenity
concerned. There's nothing that makes it non-routable. It's just a
point--the routers will get you as close to the point on the road as
possible. The addr: property definitely isn't going to help in making it
On Mon, Sep 8, 2008 at 10:33 AM, Norbert Wenzel <[EMAIL PROTECTED]> wrote:
> Karl Newman wrote:
>
>> Just make two different nodes, each located closest to the amenity
>> concerned. There's nothing that makes it non-routable. It's just a
>> point--the routers will get you as close to the point on
vegard a écrit :
> On Mon, Sep 08, 2008 at 06:40:59AM -0700, Karl Newman wrote:
>>> So personally I think duplicate keys would be the easiest and best way to
>>> tag such double-uses.
>>>
>>> Norbert
>>>
>> Just make two different nodes, each located closest to the amenity
>> concerned. There's not
12 matches
Mail list logo
