On Sun, Sep 1, 2013 at 11:18 PM, François Lacombe
wrote:
> Example :
> power=pole
> pole:transformer=yes
> transformer=distribution
> voltage=2;400
> transformer:ref=XX
> pole:ref=
Move "pole:transformer=yes" to one of the possible values of
"transformer" and you fall back to the tag
Ok, but 'yes' has to be added to the transformer=* table of values in the
proposal.
It isn't for now, that's why I thought we can't use it in this particular
case.
And what about multi-utilities poles ?
IMHO they definetly can't only be identified by power=* tag.
*François Lacombe*
francois dot
> It's already used for the poles but don't you think it's transformers
> which deserve the most the usage of power=* ?
>In this case no.
>From an electrical viewpoint the transformer is of course important. However,
>is this the most important aspect for the average user? You see a pole in >a
And how would you map such things ?
Concrete mast with low voltage power line, wifi antenna and communication
cables.
http://www.satcontact.fr/sites/default/files/SIEA-pbbt1.jpg
Concrete poles with optical fiber and medium voltage power line.
http://mlebon.typepad.com/.a/6a00d83454563069e2016762e
2013/9/1 Greg Troxel
> As Frederik points out, admin_level=8 is typically used for "town",
> "city", or "municipality". To the extent that (some) administrative
> divisions in Nepal are functionally similar to administrative divisions
> in other countries, using the same admin_level numbers is h
Thanks for the pictures !
We are taking loops only to come back to the conclusion that a pole is a
pole.
It does not matter what is mounted but we need to be able to tag several
objects mounted.
man_made=pole
communication=receiver
power=transformer
On 02.09.2013 11:48, François Lacombe wrote:
2013/9/2 fly
> Thanks for the pictures !
>
> We are taking loops only to come back to the conclusion that a pole is a
> pole.
> It does not matter what is mounted but we need to be able to tag several
> objects mounted.
>
That's what I'm trying to explain... Even if the simpler way proposed in
s
Hey
water=intermiitent and water=tidal contradict with natural=water plus
water=* and do not totally fit with waterway=*
I suggest to deprecate these two tags in favour of intermittent=yes/no
and tidal=yes/no with defaults set to "no".
cu
fly
___
Tag
2013/9/2 fly
> Hey
>
> water=intermiitent and water=tidal contradict with natural=water plus
> water=* and do not totally fit with waterway=*
>
> I suggest to deprecate these two tags in favour of intermittent=yes/no
> and tidal=yes/no with defaults set to "no".
>
shouldn't that go to the impor
On 02.09.2013 17:09, Martin Koppenhoefer wrote:
> 2013/9/2 fly
> Hey
>
> water=intermiitent and water=tidal contradict with natural=water plus
> water=* and do not totally fit with waterway=*
>
> I suggest to deprecate these two tags in favour of intermittent=yes/no
> and ti
On Monday 02 September 2013, Martin Koppenhoefer wrote:
> but admittedly the alternative approach (intermettent=yes) is used ~3
> times more often...
Of which >90% are from imports as well.
The number of water features manually tagged as intermittent is sadly
negligible.
But yes, intermittent=y
On 02/09/2013 09:58, François Lacombe wrote:
Ok, but 'yes' has to be added to the transformer=* table of values in
the proposal.
Done, but with the recommendation to use a more specific value such as
"distribution" if possible.
It isn't for now, that's why I thought we can't use it in this
2013/9/2 Ole Nielsen
> On 02/09/2013 09:58, François Lacombe wrote:
>
>> Ok, but 'yes' has to be added to the transformer=* table of values in
>> the proposal.
>>
>
> Done, but with the recommendation to use a more specific value such as
> "distribution" if possible.
Nice. Thank you.
> You ca
On Aug 28, 2013 8:17 AM, "Pieren" wrote:
> But another point is traffic signals where a bicycle can ignore red
> light stop when he is turning to right (right-hand traffic). This is
> allowed in some coutries, sometimes only with a specific road sign. I
> don't know how it is tagged currently.
T
Here's an example pack station: http://www.kennedymeadows.com/
I'd say the horse operation is first a "*coral*".
Second it is the type of coral that has *offerings for the public.*
And third it offers *cargo transport via horse.*
http://wiki.openstreetmap.org/wiki/Riding as you noted use a more
Thank you for the suggestion. Turns out that the operation at Kennedy Meadows
is quite a bit bigger with restaurant, lodging, store, etc. That is up the
highway from the one I'm tagging but I'm following your suggestion minus the
animal_boarding, feeding, etc. as it appears from the operator's w
Bryce Nesbitt wrote:
> Here's an example pack station: http://www.kennedymeadows.com/
>
> I'd say the horse operation is first a "*coral*".
> Second it is the type of coral that has *offerings for the public.*
> And third it offers *cargo transport via horse.*
>
>
>
> http://wiki.openstreetmap
On Fri, Aug 30, 2013 at 11:01 AM, Volker Schmidt wrote:
>
> On 30 August 2013 12:44, Martin Koppenhoefer wrote:
>
>> IMHO use amenity=ranger_station - no need to hide it in a subtag. If this
>> is anglo centric other people where this feature doesn't exist simply won't
>> use the tag.
>>
>> +1
>
18 matches
Mail list logo
