sent from a phone
> On 15. Jul 2020, at 00:49, Justin Tracey wrote:
>
> If the festival is held at some date expressible using the opening hours
> syntax, you could use the "open hours" tag[0] or add conditions to the
> "access" tags
I would not use opening_hours tag to represent the tempo
Am Mi., 15. Juli 2020 um 01:40 Uhr schrieb Paul Allen :
> On Tue, 14 Jul 2020 at 23:44, Matthew Woehlke
> wrote:
>
> The multipolygon is just ammenity=parking, but the sub-objects are
>> tagged with more information (capacity, in particular). Again, is that
>> sane, or do I need to do this differ
I found interesting the Corine definition for "3.3.3 Sparsely vegetated
areas" [1] : it refers to various scenarios, and specify a percentage
(10%-50%, or "less than 50%") for vegetation landcover.
In the similar American paper [2] mentioned in a previous post, we find for
barren land (page 18): "
Am Di., 14. Juli 2020 um 18:24 Uhr schrieb Volker Schmidt :
> I suggested this as a helpful guide when defining tag values. I don't
> think it can be used one-to-one for OSM.
> Bare ground, BTW, can be found also the area covered by CORINE, as it
> includes the Sahara for example)
>
right, but i
In the parking example that i talk about, the multipolygon is not usable if
i want to indicate the specificity of each part of the parking lot like
capacity or capacity:disabled (as the tagging is global for every outer
part). I like the site relation as it allows to also group the vending
machine
Am Mi., 15. Juli 2020 um 09:45 Uhr schrieb Martin Koppenhoefer <
dieterdre...@gmail.com>:
> If you are interested in reading some interesting thoughts about landcover
> classification, there is the FAO landcover classification system, thought
> to be useful globally:
> http://www.fao.org/3/X0596E/
Am Mi., 15. Juli 2020 um 10:03 Uhr schrieb Lionel Giard <
lionel.gi...@gmail.com>:
> In the parking example that i talk about, the multipolygon is not usable
> if i want to indicate the specificity of each part of the parking lot like
> capacity or capacity:disabled (as the tagging is global for e
On Wed, 15 Jul 2020 at 08:35, Martin Koppenhoefer
wrote:
> Am Mi., 15. Juli 2020 um 01:40 Uhr schrieb Paul Allen >:
>
> If you're talking about one (or both) of those parking areas by the
>> restaurant, then it is (or they are) not really a parking area. I'd
>> probably make it a closed way wit
On 14/07/2020 19.39, Paul Allen wrote:
On Tue, 14 Jul 2020 at 23:44, Matthew Woehlke wrote:
The multipolygon is just ammenity=parking, but the sub-objects are
tagged with more information (capacity, in particular). Again, is
that sane, or do I need to do this differently?
Doesn't look sane at
On 15/07/2020 03.33, Martin Koppenhoefer wrote:
Also you should not have 2 objects amenity=parking which cover the same
area (regardless of additional tags).
Do you mean having that on both the relation and the areas?
Am Mi., 15. Juli 2020 um 01:40 Uhr schrieb Paul Allen :
Even so, is a mult
On 15/07/2020 05.43, Paul Allen wrote:
On Wed, 15 Jul 2020 at 08:35, Martin Koppenhoefer wrote:
there is the "maxstay" tag which can be used with a value like 5 or 15
minutes.
https://taginfo.openstreetmap.org/keys/maxstay#values
That works semantically, but the rendering is (on many cartos) m
sent from a phone
> On 15. Jul 2020, at 16:17, Matthew Woehlke wrote:
>
> On 15/07/2020 03.33, Martin Koppenhoefer wrote:
>> Also you should not have 2 objects amenity=parking which cover the same
>> area (regardless of additional tags).
>
> Do you mean having that on both the relation and t
On 15/7/20 5:07 pm, Martin Koppenhoefer wrote:
sent from a phone
On 15. Jul 2020, at 00:49, Justin Tracey wrote:
If the festival is held at some date expressible using the opening
hours syntax, you could use the "open hours" tag[0] or add conditions
to the "access" tags
I would not use
Le 15 juillet 2020 23:10:52 GMT+02:00, Martin Koppenhoefer
a écrit :
>Generally I would agree with Paul, maxstay of a few minutes isn’t actually a
>„parking“
I doesn't agree.
Yves
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.
14 matches
Mail list logo