[Talk-us] Appalachian Trail data

Richard Weait richard at weait.com
Sat May 22 19:47:49 BST 2010


On Sat, May 22, 2010 at 5:02 AM, Jean-Guilhem Cailton <jgc at arkemie.com> wrote:
> Le 21/05/2010 05:10, Eric Christensen a écrit :
[ ... ]
>> Has anyone contacted them about possible inclusion of their data into
>> OSM?  If not, I could try to work with them so we could include their
>> data.  It would be a great asset to have.
[ ... ]
> Quote from their "Data download agreement"
> (http://www.appalachiantrail.org/GISagreement)
>
> "To access and use this data, we ask that you agree to the following
> liability disclaimer and that you use proper citation (see metadata for
> details) on any materials (digital or printed) in which this information
> appears, and that you use the data appropriately."
>
> If you want to contact them, it might be good to check whether
> source=... is a proper citation for them (along with attribution in the
> wiki, maybe).

[I don't intend to direct my comments following at the previous
posters in this thread.  I just want to get a few things off my chest,
and on to the list.  ;-) ]

Please no, not the source tag as attribution.  That approach was first
used with TIGER import, iirc.  I've even recommended it for other
imports, but I now consider that a mistake.  Requiring attribution in
the db adds unnecessary duplication to the db and risks removal by
future editors.  When in discussion with data publishers, I recommend,
in order of preference:

- asking them to relicense under PDDL to make their data available to
the broadest range of projects, not just OSM.
- asking them to contribute their data explicitly to OSM under the
current ccbysa and future ODbL with no additional strings.
- asking them to contribute their data explicitly to OSM under the
current ccbysa and future ODbL and explicitly accept mention on the
wiki as suitable attribution, for example:
http://wiki.openstreetmap.org/wiki/Attribution or
http://wiki.openstreetmap.org/wiki/Import/Catalogue Please note that
this single page does not scale and will have to eventually be split
into sub-pages.

When considering imports, please consider the background and
experience or previous OSM imports and importers.

There are OSM contributors who believe that imports are bad for OSM.
http://wiki.openstreetmap.org/wiki/Talk:Import/Guidelines#Are_imports_bad.3F

Do read, understand and follow the import guidelines.  Consider
joining the imports mailing list and finding somebody with previous
successful import experience to help if you are new to OSM imports.
http://wiki.openstreetmap.org/wiki/Import/Guidelines




More information about the Talk-us mailing list