0
1

I have a question about attribution requirements. If I access OpenStreetMap data and save the OSM data into a database, do I need to save an attribution with the saved data? Do I then need to display that attribution every time the saved data is accessed?

Here's what I want to do: I'd like to create a "driving distance calculator" for a database application. My software will run within a database application. My software will take two addresses from the database, geocode both of them, then calculate the driving distance between them (using a routing service). Once the driving distance is possessed, my software will save it into the database.

This will run on the "view page" of a single record. The user will have a single record open, and on the view form they will see a "Calculate Driving Distance" button. Clicking the button will invoke my software as described above. I plan to add the required attributions on this page, for both the OpenStreetMap data and the MapQuest API.

But after that has occurred and the data is now saved in the database application, do I need to maintain an attribution with the saved copy of the data? I want to write my software so that it can use different mapping services, so it's possible that the driving distances saved on different records were acquired from different mapping services.

The saved driving distance will be used for private purposes only, and won't be republished. The database application is a password-protected application. My software may be used by both commercial and non-profit organizations.

Thanks! - Nathan

asked 09 Jun '12, 17:43

PlaysWithLife's gravatar image

PlaysWithLife
11112
accept rate: 0%


The question is a bit tricky, however my general approach would be to

  • be conservative and attribute OSM when you have used OSM data
  • be fair and attribute OSM when you have used OSM data even if you would not be legally strictly required to do so

When we switch to the ODbL you will have to determine if what you are doing falls in the "produced work" or derived database categories, the later will add further requirements and duties over attribution. This is naturally only relevant if you redistribute or publish the saved data. However even if you currently don't intend to do so, down the road you may change your plans and use the data for a public project and it would be very silly to not be able to do so because you didn't save the original source with your derived data.

The LWG (Licence Working Group) is currently discussing similar questions to yours with respect to geocoding, please see the minutes for the current state of the deliberations.

permanent link

answered 10 Jun '12, 00:38

SimonPoole's gravatar image

SimonPoole ♦
38.6k13287612
accept rate: 19%

edited 10 Jun '12, 00:48

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×195
×136
×25
×4
×1

question asked: 09 Jun '12, 17:43

question was seen: 2,670 times

last updated: 10 Jun '12, 00:49

powered by OSQA