sent from a phone
> On 10. May 2020, at 01:31, Paul Allen wrote:
>
> If you use amenity=taxi + vehicle=* you
> guarantee that any carto which renders amenity=taxi will render ojek ranks
> incorrectly at first, and perhaps incorrectly for all time (if they decide
> they're
> going to ignore
Hello there,
the social_facility:for=* tag is used to describe the group of people that
is primarily served by the social facility. In my opinion there is the value
"family" missing on the Wiki (
https://wiki.openstreetmap.org/wiki/Key:social_facility:for)
Let me explain why: There are many
Hello,
I would not get in too detailed definitions, other values here like senior
or mental_health do not go into much details on the wiki. Family are the
groups of people these social facilities are aiming their services at.
Usually this are groups the consists of defferent age groups, juvenile /
On Sun, 10 May 2020 at 13:34, Martin Koppenhoefer
wrote:
>
> > On 10. May 2020, at 14:24, Paul Allen wrote:
> >
> > Technically, either approach to
> > tagging would work
>
>
> I would question this. It would work if all data consumers would evaluate
> the subtag, i.e. add support for it and it
sent from a phone
> On 10. May 2020, at 14:43, Paul Allen wrote:
>
> Either way, it's going to give the wrong results if renderers don't support
> it, the question is which wrong way is preferable: ojeks aren't rendered or
> ojeks
> are rendered as taxis.
ojeks getting rendered as cab
sent from a phone
> On 10. May 2020, at 11:09, klischka wrote:
>
> In my opinion there is the value
> "family" missing on the Wiki (
> https://wiki.openstreetmap.org/wiki/Key:social_facility:for)
I agree in principle. Can you give a definition of “family”?
Cheers Martin
sent from a phone
> On 10. May 2020, at 14:24, Paul Allen wrote:
>
> Technically, either approach to
> tagging would work
I would question this. It would work if all data consumers would evaluate the
subtag, i.e. add support for it and it would mean we would require two tags for
taxis:
On Sun, 10 May 2020 at 09:24, Martin Koppenhoefer
wrote:
>
> > On 10. May 2020, at 01:31, Paul Allen wrote:
> >
> > If you use amenity=taxi + vehicle=* you
> > guarantee that any carto which renders amenity=taxi will render ojek
> ranks
> > incorrectly at first, and perhaps incorrectly for all
在 2020年5月10日週日 16:24，Martin Koppenhoefer 寫道：
>
>
> sent from a phone
>
> > On 10. May 2020, at 01:31, Paul Allen wrote:
> >
> > If you use amenity=taxi + vehicle=* you
> > guarantee that any carto which renders amenity=taxi will render ojek
> ranks
> > incorrectly at first, and perhaps
And a tag refinement with a sub tag would work if the decision to tag as such
is advertised : renderers will follow, editor softwares too.
A successful vote may help, opening issues at major editors and renderers once
settled will certainly.
Also, it's not like taxis are a must have for
On Sun, 10 May 2020 at 22:00, Cj Malone wrote:
> > But not all of them are necessarily contacts. I've added URLs for
> > historic buildings that give more information about the
> > building. There is nobody to talk to about it. I've added websites
> > for companies; there is a contact page on
sent from a phone
> On 10. May 2020, at 17:24, Yves wrote:
>
> Also, it's not like taxis are a must have for renderers, there will be no
> drama if a map shows a taxi station inaccurately for a few months
all maps actually ;-)
Cheers Martin
___
Le dim. 10 mai 2020 à 01:25, Martin Koppenhoefer a
écrit :
> On 9. May 2020, at 22:50, Florimond Berthoux
> wrote:
>
> Yeah, that's the point...
>
> Keep it simple.
> You know taxi key ? You know motorcycle key ? Yeah, you can contribute
> without checking yet another wiki tag page.
>
> By the
On Sun, 2020-05-10 at 22:28 +0100, Paul Allen wrote:
> We can't replace phone with contact:phone in all cases, as some wish
> to do, because of phone boxes. We can't replace website with
> contact:website in all cases, as some wish to do, because there are a
> lot of POIs with websites or URLs
sent from a phone
> On 10. May 2020, at 23:55, Cj Malone wrote:
>
> I think we should actively encourage more precise tags like
> contact:phone when it's a contact number.
why is this “more precise”?
What about even “more precise” tags, like
contact:phone:business_hours=
On Sun, 10 May 2020 at 22:55, Cj Malone wrote:
>
> I agree, not all phone tags convert to contact:phone, same with the
> others. I don't think anybody is talking about a mass edit of the
> database.
>
But that's what they often imply. Perhaps with carelessly-worded
statements,
like the one
On Sun, 2020-05-10 at 23:07 +0100, Paul Allen wrote:
> But that's what they often imply.
I don't know if this is worth saying or not, but this isn't a war,
there aren't sides. We all just want OSM to be the best it can be.
I am fairly new to OSM, especially the mailing lists but I guess you
are
At the end of the day we are not taking motorcycle taxi and taxi
themselves. What's being tagged are waiting area for taxi or motorcycle
taxis. What matters is that, if one is created as an optional subtag of
another, would not using such subtag result in incorrect analysis of data
when someone
> But not all of them are necessarily contacts. I've added URLs for
> historic buildings that give more information about the
> building. There is nobody to talk to about it. I've added websites
> for companies; there is a contact page on that website but the URL
> I've given is for the company
On Mon, 11 May 2020 at 01:38, Cj Malone wrote:
> On Sun, 2020-05-10 at 23:07 +0100, Paul Allen wrote:
> > > and gradually deprecating the generic tags.
> >
> > And there you go, wanting to get rid of phone=* and website=*.
>
> I think I stand by that quote, but I'm happy to discus it. I'm not
>
* Also, as have already been mentioned in other replies, there are various
other differences between the two services other than number of wheels and
whether they're enclosed.
在 2020年5月11日週一 09:04，Phake Nick 寫道：
> I am more thinking about analysis of geographical data of cities or
> districts
I am more thinking about analysis of geographical data of cities or
districts where taxi and motorcycle taxi would be two very different things
to be managed.
Even if you view it from the viewpoint of people trying to get a ride, I
would not expect cross-display of the two types of mobility items
On Mon, 2020-05-11 at 02:10 +0100, Paul Allen wrote:
> And yet you, and others, keep saying it. "Deprecate" means "express
> disapproval of." In the context of OSM, it means "phase out." That
> is,
> eradicate with the passage of time. It may not be what you mean, but
> it's what you keep
On Sun, 10 May 2020 at 21:04, Phake Nick wrote:
> I am more thinking about analysis of geographical data of cities or districts
> where taxi and motorcycle taxi would be two very different things to be
> managed.
If you are managing taxis and motorcycle taxis then surely you know
you have to
On Sun, 10 May 2020 at 18:35, Phake Nick wrote:
> At the end of the day we are not taking motorcycle taxi and taxi themselves.
> What's being tagged are waiting area for taxi or motorcycle taxis. What
> matters is that, if one is created as an optional subtag of another, would
> not using such
May 11, 2020, 02:36 by cjmal...@mail.com:
> On Sun, 2020-05-10 at 23:07 +0100, Paul Allen wrote:
>
>> > and gradually deprecating the generic tags.
>>
>> And there you go, wanting to get rid of phone=* and website=*.
>>
>
> I think I stand by that quote, but I'm happy to discus it. I'm not
>
On Mon, 2020-05-11 at 03:27 +0200, Mateusz Konieczny via Tagging wrote:
> May 11, 2020, 02:36 by cjmal...@mail.com:
> > On Sun, 2020-05-10 at 23:07 +0100, Paul Allen wrote:
> > > > and gradually deprecating the generic tags.
> > >
> > > And there you go, wanting to get rid of phone=* and
27 matches
Mail list logo
