On 1/29/2016 8:49 AM, Matthijs Melissen wrote:
On 29 January 2016 at 17:37, Mateusz Konieczny wrote:
"but that's not much to do with tagging diversity" - I would dispute
it, from my personal experience. Tagging diversity IS one of real
problems in using OSM data.
+1.
Mateusz Konieczny wrote:
> I am not claiming that there are quick & easy ways to reduce
> complexity - but complexity has some real negative consequences.
The cycleway tagging mess has come about because a bunch of wikifiddlers
keep inventing ever more spurious and unnecessary tags -
> "but that's not much to do with tagging diversity" - I would
> dispute it, from my personal experience. Tagging diversity IS one
> of real problems in using OSM data.
Could you please give an example?
My first ever attempt to display cycleways
[...]
Thank you very much. Now I
On 29 January 2016 at 17:37, Mateusz Konieczny wrote:
> "but that's not much to do with tagging diversity" - I would dispute
> it, from my personal experience. Tagging diversity IS one of real
> problems in using OSM data.
+1.
-- Matthijs
On Thu, 28 Jan 2016 19:50:11 +
Andy Townsend wrote:
> On 28/01/2016 19:16, David Marchal wrote:
> > Hello, there.
> >
> > On a GitHub issue
> > (https://github.com/gravitystorm/openstreetmap-carto/issues/2027#issuecomment-174443685),
> >
> > I've been told that Wiki
>> This diversity of tagging is often quoted as a problem for data
>> consumers. Oddly, this is often by people who don't actually use the
>> data but feel it must be awkward. Actually it's not. All OSM data has
>> to processed before use. This processing can be fairly
>> straightforward or
On Fri, 29 Jan 2016 19:38:46 +0100
Roland Olbricht wrote:
> >> This diversity of tagging is often quoted as a problem for data
> >> consumers. Oddly, this is often by people who don't actually use
> >> the data but feel it must be awkward. Actually it's not. All OSM
>
On Thu, 28 Jan 2016 20:31:04 +0100
Matthijs Melissen wrote:
> On 28 January 2016 at 20:16, David Marchal wrote:
> > On a GitHub issue
> > (https://github.com/gravitystorm/openstreetmap-carto/issues/2027#issuecomment-174443685),
> > I've been told that
Hello, there.On a GitHub issue
(https://github.com/gravitystorm/openstreetmap-carto/issues/2027#issuecomment-174443685),
I've been told that Wiki tagging votes are only advisory and that the
community is only invited, neither required nor recommended, to follow them. As
I understand this
On 28 January 2016 at 20:16, David Marchal wrote:
> On a GitHub issue
> (https://github.com/gravitystorm/openstreetmap-carto/issues/2027#issuecomment-174443685),
> I've been told that Wiki tagging votes are only advisory and that the
> community is only invited, neither required
On 28/01/16 19:16, David Marchal wrote:
Hello, there.
On a GitHub issue
(https://github.com/gravitystorm/openstreetmap-carto/issues/2027#issuecomment-174443685),
I've been told that Wiki tagging votes are only advisory and that the
community is only invited, neither required nor recommended,
On 28/01/2016 19:16, David Marchal wrote:
Hello, there.
On a GitHub issue
(https://github.com/gravitystorm/openstreetmap-carto/issues/2027#issuecomment-174443685),
I've been told that Wiki tagging votes are only advisory and that the
community is only invited, neither required nor
David Marchal wrote:
> What is the applicability of the Wiki content?
Three long-standing principles of OSM:
1. consensus is important
2. precedent is important
3. patches beat "should"
The first means that you can't order the community to do things based on ten
people voting on the
To: talk@openstreetmap.org
From: ajt1...@gmail.com
Date: Thu, 28 Jan 2016 19:50:11 +
Subject: Re: [OSM-talk] Applicability of wiki tagging and votes: may, should or
must
More seriously, any dataset that has no rules enforced at the API level must be
assumed to have data in it that doesn't
14 matches
Mail list logo