Possible drivers of quality:
1. Peer reviewing, as a social gateway to community engagement with new
mappers.
2. Hiring a physiologist on retainer to understand obsessed trolls like
NE2, and respond appropriately.
3. Supporting single feature mappers. There's a vibrant community
On Fri, May 31, 2013 at 12:23 PM, Mike Thompson miketh...@gmail.com wrote:
Frederic,
How about more mappers?
Mike
I think the key is more users of the maps.
Not one in ten people I mention OSM to have ever heard of it: and I tend to
run with geeks, outdoor enthusiasts, graduate students,
On Fri, Jun 7, 2013 at 11:24 AM, Bryce Nesbitt bry...@obviously.com wrote:
On Fri, May 31, 2013 at 12:23 PM, Mike Thompson miketh...@gmail.comwrote:
Frederic,
How about more mappers?
Mike
I think the key is more users of the maps.
By that I mean more eyeballs on the output: more passive
On Fri, May 31, 2013 at 12:15 PM, Frederic Julien fjulie...@yahoo.comwrote:
Dear all,
I'm working on a presentation and interested to hear your thoughts. What
are the top 2-3 changes that could improve OSM data quality? That could be
processes, tools, methods, training, peer review,
, 2013 2:26 PM
To: Mike Thompson
Cc: Frederic Julien; talk-us@openstreetmap.org
Subject: Re: [Talk-us] OSM Data Quality
On Fri, Jun 7, 2013 at 11:24 AM, Bryce Nesbitt bry...@obviously.com wrote:
On Fri, May 31, 2013 at 12:23 PM, Mike Thompson miketh...@gmail.com wrote:
Frederic,
How about more
Dear all,
I'm working on a presentation and interested to hear your thoughts. What are
the top 2-3 changes that could improve OSM data quality? That could be
processes, tools, methods, training, peer review, attributes, etc.
If this sort of info is available elsewhere let me know.
Looking
Frederic,
How about more mappers?
Mike
On Fri, May 31, 2013 at 1:15 PM, Frederic Julien fjulie...@yahoo.comwrote:
Dear all,
I'm working on a presentation and interested to hear your thoughts. What
are the top 2-3 changes that could improve OSM data quality? That could be
processes,
One thing that would help in the editor software would be, once you select a
tag, and list the preset values available, to have the option to list the wiki
descriptions of what those values mean. This should be optional, and should
come up in a separate window so you don't lose track of what
On Fri, May 31, 2013 at 12:15 PM, Frederic Julien fjulie...@yahoo.comwrote:
I'm working on a presentation and interested to hear your thoughts. What
are the top 2-3 changes that could improve OSM data quality? That could be
processes, tools, methods, training, peer review, attributes, etc.
As already noted, quality is in the eye of the beholder. That said, there
are some objective quality indicators such as positional accuracy,
completeness, resolution. I summarized this in a paper a few years ago from
another source, where I also introduced the notion of 'crowd quality' in an
On Fri, May 31, 2013 at 2:21 PM, Martijn van Exel m...@rtijn.org wrote:
and finally how do we make local communities work? Latter is super
important because great local data (transit, businesses, addresses) is key
to the usefulness (hey, another way of thinking about quality!) of OSM.
Great
US Talk talk-us@openstreetmap.org
Sent: Friday, May 31, 2013 2:21 PM
Subject: Re: [Talk-us] OSM Data Quality
As already noted, quality is in the eye of the beholder. That said, there are
some objective quality indicators such as positional accuracy, completeness,
resolution. I summarized
Frederic:
Validator is an excellent tool, but currently only works with JOSM.
I'd love to see Potlatch and/or iD do something similar. True, many
(most) ignore what Validator may report, and while Errors are always
Errors, Warnings are a bit more subtle and really must be taken one
at a
Martijn van Exel-3 wrote
As already noted, quality is in the eye of the beholder.
Yes, quality lies in the eye of the beholder. Or perhaps better said in the
eye of the data consumer. Therefore the assessment of quality will depend on
the application and use case you have in mind.
I think OSM
Richard,
We need:
1. More people. A big part of the map is untouched. We could
reach out more to the educational community to get middle-school and
high-school students involved.
2. Better training for people who are new to OSM. I think
learnosm.org is very good. I'm a
Richard Welty writes:
3) in the US (and you did ask on talk-us), identifying and dealing
with the shaky Tiger data from the 2007 tiger import. some of this
has been done, but it's an ongoing effort and is one of those
things that is easier to say than it is to do
I've been adding lakes
On 5/31/13 9:39 PM, Russ Nelson wrote:
I've been working on finding and fixing them in New York State. I've
probably got more than half -- maybe 60% fixed. Hopefully even
70%. And I'm just one mapper (well, and you're another mapper who's
done a ton, plus there's a few more I'm sure). My main
On Fri, May 31, 2013 at 3:02 PM, stevea stevea...@softworkers.com wrote:
Clifford Snow writes:
First you need to define what good data quality is and second, you need to
collect data to measure data quality. Once good data is collect then start
determining root cause of the problem.
Most
Martijn van Exel wrote:
I think I just wrote half of one of my SOTM US talk.
I think you just wrote half of mine too. ;)
cheers
Richard
--
View this message in context:
http://gis.19327.n5.nabble.com/OSM-Data-Quality-tp5763578p5763648.html
Sent from the USA mailing list archive at
ramble++;
Clifford, yes I could sense what you were trying to say: I have a
thirty+ year Quality background at Apple, Adobe, IBM, the University
of California (and others) as an employee, contractor, subcontractor
and consultant. You are doing fine, you just did fine.
OSM does sample
20 matches
Mail list logo
