On Tue, 8 Jan 2019 07:54:00 +1000
Graeme Fitzpatrick wrote:
> Possibly something like caravan:type=caravan / motorhome / Winnebago /
> camper trailer etc, but then you get to the problem of what is
> difference between a camper van, motorhome & Winnebago?
In the (US) industry, the terminology fo
While I was first thinking of brand like Warin, I think this is the
better solution. Just as, we do not map the share holders of companies
(even when they are other companies) on shops, man_made=works object
etc., we typically do not map properties of the operator (besides
brand).
m.
On Tue, Jan
sent from a phone
> On 7. Jan 2019, at 19:08, Volker Schmidt wrote:
>
> Are these "access" tags, in the sense that (in the example) the kindergarten
> only accepts Roman Catholic children, or is it only indicating the religious
> background of the institution, but they accept children with o
No magic, the preset has curated values for the subtags (which is
naturally possible in iD too) most of them have historically been
gleaned from the wiki or from actual use. The upside and the downside
of this is that they are curated, so there is always a certain lag
between a value being used in
Am 08.01.2019 um 23:55 schrieb Martin Koppenhoefer:
> ...
> With current tools there is no tag completion for the individual
> values in lists, while the alternative already works.
>
Value completion has for lists has woked since ages in Vespucci (you
normally would use the form interface where yo
sent from a phone
> On 8. Jan 2019, at 14:35, Simon Poole wrote:
>
> I'm not convinced that we really want to model such a level of detail in the
> first place, but using a small set of common keys for facilities with similar
> purpose has obvious advantages over a multitude of special purpo
On Tue, 8 Jan 2019 at 23:36, Simon Poole wrote:
> I'm not convinced that we really want to model such a level of detail in
> the first place,
>
Agree with you there!
If the place is a shop=tyres, isn't that really all that OSM needs to say?
After that, isn't it up to "you" to make a simple phon
Am 08.01.2019 um 16:25 schrieb Rory McCann:
> On 08/01/2019 08:30, Simon Poole wrote:
>> and yes you could even document that something is -not- sold in a
>> structured fashion.
>
> How do you do that? To me "sells:blah=no" is clear: that blahs are, by
> default, sold in this type of thing, but ar
On Tue, 8 Jan 2019 at 15:27, Rory McCann wrote:
>
> How do you do that? To me "sells:blah=no" is clear: that blahs are, by
> default, sold in this type of thing, but aren't here. Is there a
> standard way to do that with semicolon'ed values?
>
Yes. You list all the things that are sold there an
On 08/01/2019 08:30, Simon Poole wrote:
and yes you could even document that something is -not- sold in a
structured fashion.
How do you do that? To me "sells:blah=no" is clear: that blahs are, by
default, sold in this type of thing, but aren't here. Is there a
standard way to do that with se
> On Jan 8, 2019, at 2:30 AM, Simon Poole wrote:
>
> Am 07.01.2019 um 16:12 schrieb Bryan Housel:
>> ...
>> On “both is OK”. the `service:vehicle` issue was because we can’t use the
>> same key `service=*` to contain both things like `tyres` (a few thousands)
>> and `driveway` (a few millions).
Inconsistent tagging is inconsistent tagging, don't think that is really
relevant for this discussion, inconsistent tagging schemes however are
on topic.
I'm not convinced that we really want to model such a level of detail in
the first place, but using a small set of common keys for facilities
wi
Am Di., 8. Jan. 2019 um 08:31 Uhr schrieb Simon Poole :
> To hypothesize on some of the stuff floating around, obviously there is
> a desire to document exactly what kind of stuff a shop sells, so people
> have proposed stuff like
>
> motorcycle:tyres=yes
>
> service:tyres:car=yes
>
> service:bicy
On 07/01/2019 23:51, Bryan Housel wrote:
So I’m thinking of introducing changeset tags like
“closes:x=123;456;789” where x can be a tracking service like
“keepright”, “osmose”, “improveosm”, “maproulette” or any other issue
tracker we want to connect iD to.
This is a good idea! You co
I think we need to map peninsulas in three ways, as nodes, areas, and ways.
Areas when the land border is obvious. Nodes for little ones, when you
don't have time to draw an area and the shape of the peninsula is obvious.
Then there are ways, when the peninsula is huge, or when the land border
isn
Personnaly I don't think I would map umbrella organisations... I would put
operator and operator:wikidata and let Wikidata update partnerships between
associations. It is not a property of the kindergarten, it is a property of the
operator.
LeTopographeFou
Message original
De: t.pfei...@co
16 matches
Mail list logo
