On Sun, 19 May 2019 at 06:12, Mateusz Konieczny
wrote:
> It is the same as with say shop=supermarket.
>
> It is not enough to tag shop=supermarket to indicate that building exists,
> you still need to have building tag (maybe on the same object, maybe on a
> separate way).
>
Which seems to be
18 May 2019, 22:07 by si...@poole.ch:
>
>
>
> Am 18.05.2019 um 11:44 schrieb Jan S:
>
>> Interesting point... I'd suggest that it is a top-level tag itself.
>> Otherwise you'd have to tag buildings as building=* and police=*, which
>> I find an unnecessary duplication that might
Am 18.05.2019 um 11:44 schrieb Jan S:
> Interesting point... I'd suggest that it is a top-level tag itself.
> Otherwise you'd have to tag buildings as building=* and police=*,
> which I find an unnecessary duplication that might even result in
> contradictory tags.
I think you will find that
Am 18.05.2019 um 15:28 schrieb Paul Allen:
> ...
> Can we just ignore the problem? For Easter, maybe. Data consumers
> could build in
> country-specific rules defining if Easter is Orthodox or Catholic.
> Along with astronomical
> calculations, that would allow an app to say "This office in a
On Sat, 18 May 2019 at 12:01, Simon Poole wrote:
>
> As I've pointed out before the one thing that is unproblematic to add are
> more variable date public holidays, right now there is only easter
> defined, adding ramadan for example would be no problem.
>
Syntactically, probably not a
I also see it as a top-level tag. i find it similar to the recent
"healthcare=*" which can be used by itself too.
Le sam. 18 mai 2019 à 11:46, Jan S a écrit :
> Interesting point... I'd suggest that it is a top-level tag itself.
> Otherwise you'd have to tag buildings as building=* and
As I've pointed out before the one thing that is unproblematic to add
are more variable date public holidays, right now there is only easter
defined, adding ramadan for example would be no problem.
Further expressing a rule is one thing, evaluating it is a something
else, and adding some kind
That doesn't seems to solve the problem that would occur. For instance, how
to represent the first Sunday (a feature in Gregorian calendar) after
Chinese traditional ceremony X (a feature in Chinese traditional calendar)
in the opening time syntax, if they're split up for "simplicity"? What
about
Hi Valor,
Thanks for reducing your proposal. I could go with it. Still, it's up to the
programming guys to say whether the changing of the name of the key from diaper
to changing_table is somehow problematic.
Best, Jan
Am 18. Mai 2019 11:28:31 MESZ schrieb Valor Naram :
>Hey guys,
>
>my first
Interesting point... I'd suggest that it is a top-level tag itself. Otherwise
you'd have to tag buildings as building=* and police=*, which I find an
unnecessary duplication that might even result in contradictory tags.
Best, Jan
Am 18. Mai 2019 10:36:32 MESZ schrieb Simon Poole :
>Seems as if
Hey guys,
my first proposal regarding changing tables were rejected because of
being "too complex". I will give it a second chance and provide you
with the v2.0 of it: https://wiki.openstreetmap.org/wiki/Proposed_featu
res/changing_table
Author: Valor Naram
Definition: A tag to mark the
Seems as if the proposal and now the definite wiki page is missing one,
not quite unimportant, bit of information:
is police an attribute to be used on other "top-level" (say for example
building=xx OSM objects or does it define a stand alone "top-level"
object itself?
Simon
Am 17.05.2019 um
Hi Graeme,
I've just seen that. I've used the taglist template, but apparently it
doesen't work as intended. I'll make a manual list.
Best,
Jan
Am Sa., 18. Mai 2019 um 01:06 Uhr schrieb Graeme Fitzpatrick <
graemefi...@gmail.com>:
>
>
> On Sat, 18 May 2019 at 07:05, Jan S wrote:
>
>>
>> I've
13 matches
Mail list logo
