On Wed, Apr 18, 2012 at 2:38 PM, Nathan Edgars II nerou...@gmail.comwrote:
On 4/18/2012 3:31 PM, Charlotte Wolter wrote:
Yes, imported data can create issues like that. The same thing happens
with schools. Yes, it takes some effort to separate them and move them
to their correct locations,
On Wed, Apr 18, 2012 at 4:40 PM, David Fawcett david.fawc...@gmail.com wrote:
On Wed, Apr 18, 2012 at 2:31 PM, Charlotte Wolter techl...@techlady.com
wrote:
I just separate them out, and look them up on Google or Bing, and
try to move them to their correct locations.
So Google is a
Gregory Arenius wrote:
Hi,
Imported data turns down potential new mappers.
I really disagree with this statement. I think the mappers would be
turned off if we didn't import it when available. So you have all
250,000 address points for the city but instead of using them you'd
rather us go
On 4/17/2012 3:29 AM, Werner Poppele wrote:
I totally agree with Frederik. Yes - imported data turns down new
mappers. Have you ever seen those monster
multipolygons ? I am sure a new mapper says: Forget that
I personally tend to stop my contribution to OSM because of the very bad
stuff I see
Nathan Edgars II wrote:
On 4/17/2012 3:29 AM, Werner Poppele wrote:
I totally agree with Frederik. Yes - imported data turns down new
mappers. Have you ever seen those monster
multipolygons ? I am sure a new mapper says: Forget that
I personally tend to stop my contribution to OSM because of
Hi,
On 04/17/12 01:05, James Umbanhowar wrote:
Being a reformed importer, I generally agree with the don't import rule.
However, I have often heard this nugget and in my experience it is based on
either anecdote or one set of simulations that assumed that individuals stop
joining because they
On 4/17/2012 4:26 AM, Frederik Ramm wrote:
And now assume there's a third city
of equal size where *nothing* has been mapped at all... maybe I
shouldn't speak for everyone but for me (and virtually every mapper I
know) surely the city with data-but-no-mappers would be least appealing,
far below
Regarding Frederik's 4 points, plus the element duplication issue as
reasons imports are bad:
ALL are potentially true for any mapper especially new ones. It is just
that a bad import can generate a lot more good/bad data at once. So yes,
imports need more effort to insure good quality.
On Tue, Apr 17, 2012 at 7:51 PM, Dale Puch dale.p...@gmail.com wrote:
I think this point is controversial, so let's stick with some points
that aren't:
1. In our history of imports, a very small percentage have been good.
Compare a users early imports to their early mapping
They aren't
On 4/17/2012 8:18 PM, Serge Wroclawski wrote:
If a user manually surveys data, there is an assumption of timeliness
and accuracy of that survey. That's not the case with imported data,
despite oftentimes being stamped official.
When I joined OSM I went through photos and notes I had taken
On Tue, Apr 17, 2012 at 8:52 PM, Nathan Edgars II nerou...@gmail.com wrote:
When I joined OSM I went through photos and notes I had taken since the late
1990s. There's no guarantee of timeliness here either. Certainly not as much
as an import of city boundary data that has each annexation
On 4/17/2012 9:23 PM, Serge Wroclawski wrote:
On Tue, Apr 17, 2012 at 8:52 PM, Nathan Edgars IInerou...@gmail.com wrote:
When I joined OSM I went through photos and notes I had taken since the late
1990s. There's no guarantee of timeliness here either. Certainly not as much
as an import of
Hi,
Imported data turns down potential new mappers.
I really disagree with this statement. I think the mappers would be turned
off if we didn't import it when available. So you have all 250,000
address points for the city but instead of using them you'd rather us go
collect all of them a
On Mon, Apr 16, 2012 at 6:46 PM, Frederik Ramm frede...@remote.org wrote:
That is exactly the wrong message. Between the lines, it reads: Importing
is for professionals and you can earn laurels by doing it right.
The message we should be sending is:
Imports are nearly always bad; they are
So I missed the whole exchange - so I read what little I see below and
here are my thoughts.
I don't think it's too GIS geeky - it's too OSM geeky. There are too
many ways to get to a common goal - adding data. You can import, GPS,
walk around, etc etc.
There almost needs to be a list
Also, the original mail in this thread was on imports, which is by its
nature, a technical list.
Folks who don't have a *ton* of experience shouldn't do imports, and
folks with a ton of experience don't do imports.
- Serge
___
Talk-us mailing list
..and I'll end my part in this with this - I've contacted the two people
I am interested in helping. I will talk to them and work our way through
the problem. I am interested in getting more people editing - not
arguing over the technical.
As for imports - I guess I shouldn't have imported
Documentation! I think what you did is exactly what is needed. It may or
may not need improvements. If what is decided in the newsgroups is not
put down in the wiki then the discussion was not finished to a point
someone could sum it up for the masses to follow. Then post a link here
for
18 matches
Mail list logo
