To avoid problems when querying, in case of explicitly add units, I would
prefer to use a separate tag like maxspeed:units=mph, for example.
Javier
El sáb., 28 jul. 2018 10:30, Mark Wagner escribió:
> On Fri, 27 Jul 2018 22:33:10 +0200
> François Lacombe wrote:
>
> > Well okay
> > Given proble
On Sun, Jul 29, 2018 at 12:57 AM, Graeme Fitzpatrick
wrote:
>
>
> The problem with that of course, as Warin mentioned, is what would it
> hypothetically render as - grass / sand / rock / scrub etc etc?
>
If you simply define an area that is absent of woodland with no tags
defining what it is, th
What I've tended to do with clearings is:
o natural=wood for "here be trees", with leaf_type added.
o If there's a large "landuse=forest" area already and that encompasses
wood, clearings, ponds etc. (and there often is), leave that as
"landuse=forest" or add as "landuse=forestry" (note - that
On 29/07/18 20:37, Paul Allen wrote:
On Sun, Jul 29, 2018 at 12:57 AM, Graeme Fitzpatrick
mailto:graemefi...@gmail.com>> wrote:
The problem with that of course, as Warin mentioned, is what would
it hypothetically render as - grass / sand / rock / scrub etc etc?
If you simply define a
On Sun, Jul 29, 2018 at 1:57 PM, Warin <61sundow...@gmail.com> wrote:
I too have created relations for tree areas and made 'holes' in them for
> various things. Some of those 'holes' may
>
well be 'bare map'.
>
[...]
> The problem with the present data in this area is that;
>
> a) it does not ren
2018.07.27. 23:47 keltezéssel, Kevin Kenny írta:
On Fri, Jul 27, 2018 at 11:54 AM marc marc wrote:
a good idea would be to explain with a (as easy as possible) example
why access=customers or private does not fit for your need.
If it was what you did in your previous email, sorry but I didn't
u
sent from a phone
> On 27. Jul 2018, at 17:53, marc marc wrote:
>
> what _I_ was saying is that despite your detailed explanations,
> i still have not understood how the case you describe is different from
> access=customers. some paths in the park of a castle are limited to the
> customer o
sent from a phone
> On 27. Jul 2018, at 17:53, marc marc wrote:
>
> I didn't understand how getting a license in your example is different
> from getting a license from a sports club.
I would understand that the permit will be obtained by everybody following the
application rules, while th
Le 29. 07. 18 à 22:35, Martin Koppenhoefer a écrit :
>> On 27. Jul 2018, at 17:53, marc marc wrote:
>> I didn't understand how getting a license in your example is different
>> from getting a license from a sports club.
> I would understand that the permit will be obtained by everybody following
sent from a phone
> On 27. Jul 2018, at 19:48, Kevin Kenny wrote:
>
> I'm all for SI units for things like voltages and elevations. I'm
> perfectly fine with tagging the elevation of Slide Mountain as 1274
> metres and letting a US data consumer convert that to 4180 feet.
>
> Regulatory thing
sent from a phone
> On 29. Jul 2018, at 09:57, Javier Sánchez Portero
> wrote:
>
> To avoid problems when querying, in case of explicitly add units, I would
> prefer to use a separate tag like maxspeed:units=mph, for example.
spreading the information over 2 tags creates another point of p
sent from a phone
> On 29. Jul 2018, at 14:57, Warin <61sundow...@gmail.com> wrote:
>
> It is quicker to map these 'holes' as they are much less in length compared
> to the outer way.
> The 'landuse=clearing' says nothing about what is inside the area , other
> than the lack of trees, it cou
That sounds right but would not be clearer to use spacename instead of
underscore? Like maxspeed:mph=25
That way you have to deal with main keys instead of split them into one key
per unit.
El lun., 30 jul. 2018 0:22, Martin Koppenhoefer
escribió:
>
>
> sent from a phone
>
> > On 29. Jul 2018, a
13 matches
Mail list logo
