[Talk-us] Brainstorming an Import Tool

80n 80n80n at gmail.com
Tue Aug 17 17:54:17 BST 2010

The lowest common denominator here is simple tracing.  Any useful map data
will be renderable in some form or other and the community has tracing
skills in spades.

I'd press for this as a starting point.  Render the data and make it
available to trace.  The community can do the rest.

The technical obstacles for importing any data set are quite high and the
issues diverse enough that automated methods are way beyond the skill set of
most OSMers.  But given a rendered map then crowdsourcing can do the rest
and a community can grow around it at the same time.

Automated imports just short circuit the community forming process and lead
to areas that are sterile.  (Does anyone have an activity heat map that can
highlight sterile areas btw?).


On Tue, Aug 17, 2010 at 1:24 PM, Ian Dees <ian.dees at gmail.com> wrote:

> On Tue, Aug 17, 2010 at 7:20 AM, Nick Black <nickblack1 at gmail.com> wrote:
>> A toolset like this would let a community grow around the import
>> process - letting OSM get the good data that's out there whilst making
>> sure there's a community there to maintain it.
> Good ideas. Also, If one of the features is to render the incoming data in
> a manner suitable for JOSM or Potlatch (think simple road centerline tiles),
> then the data doesn't even need to be downloaded into OSM: it could be used
> by the community to trace or correct existing data.
> _______________________________________________
> Talk-us mailing list
> Talk-us at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/talk-us
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20100817/d1350a28/attachment-0001.html>

More information about the Talk-us mailing list