Question About OpenStreetMap and Legal Requirements
<p>We are planning to start working on a new Application (web based application) that requires us to use Geo Data. </p>

<p>OpenStreetMap is a free and open source data source that we could use as a starting point.</p>

<p>However it doesn't have everything that we need so what we are planning to do is to use their data to render the basic graphics (such as roads, parks, etc) and have a separate database to store more meta data for each geo data point.</p>

<p>My questions is whether if we have to make our metadata public or not ?</p>

<p>This is the few Urls that I found related to licensing:</p>

<p><a href="http://www.openstreetmap.org/copyright" rel="nofollow">http://www.openstreetmap.org/copyright</a></p>

<p><a href="http://wiki.openstreetmap.org/wiki/Legal_FAQ" rel="nofollow">http://wiki.openstreetmap.org/wiki/Legal_FAQ</a></p>

<p>Thanks in advance</p>

<p>This is addressed in OpenStreetMap's Legal FAQ, and, as usual, it depends.</p>

<blockquote>
  <p>3d. If I use your data together with someone else's data, do I have to
  apply your license to their data too?</p>
  
  <p>If the two datasets are independent, no, you don't; this is a
  Collective Database.</p>
  
  <p>If you adapt them to work together (for example, by taking footpaths
  from the OSM data, roads from the third-party data, and connecting
  them for routing), this is a Derivative Database and so you must (as
  per 3b). However, if the two datasets are matched "trivially" by, for
  example, automated matching using a simple criterion such as
  name/locality, this is not "substantial" and remains a Collective
  Database. There is a <a href="http://wiki.openstreetmap.org/wiki/Open_Data_License/Trivial_Transformations_-_Guideline" rel="nofollow">Community Guideline</a> on what constitutes a trivial
  transformation.</p>
</blockquote>

<p><a href="http://wiki.openstreetmap.org/wiki/Legal_FAQ#3d._If_I_use_your_data_together_with_someone_else.27s_data.2C_do_I_have_to_apply_your_license_to_their_data_too.3F" rel="nofollow">OpenStreetMap Legal FAQ, question 3.4 3d</a></p>

<p>So it depends on whether your data and the OSM data are "independent", and whether your changes to the OSM data itself qualify as a "trivial transformation". This distinction is a bit vague, and is based a similar notion in the EU <a href="https://en.wikipedia.org/wiki/Database_Directive" rel="nofollow">Database Directive</a>. I don't think you'll find much more specific general guidance - if you need more assurance, you'll have to work with a lawyer.</p>

<p>In your case, if your metadata is stored separately from the OSM data (ideally, technically separated, as in a different DB table or different file), I would think it would be considered "independent". The only link between OSM data and your data would be the reference to the OSM object in the metadata (probably by coordinate or OSM ID) - that should fall under _"trivial matching" as explained above.</p>

<p><strong>Thus you create a "Collective Database" and not a "Derivative Database", and the OSM license probably does not apply to your data.</strong></p>

<p>As with most "open source" projects, if you use their code then if you "distribute" with your own modifications, you have to do so under the same open source license as to your modifications as well. Your meta data arguably falls under that under this license as modified code.  </p>

<p>So yes, you would have to make your meta data publicly available once your system goes live, as well as attribute to OpenStreetMap. </p>

<p>There are some exceptions to that under this license, but to make sure you don't commit your resources, only to find out that you are threatened with suit, find an attorney who also programs, ask for a written opinion on the subject code\license, and if you get a positive written opinion, even then seek out the owner of the license and get an in writing assent if possible. </p>

<p>As per @mkennedy's above comment and link to <a href="https://gis.stackexchange.com/questions/156816/legal-standpoint-of-using-open-source-map-data-in-proprietary-software/156818#156818">Legal standpoint of using open source map data in proprietary software?</a> there is a real concern that the added data will be considered to be a derivative database.</p>

united-states licensing open-source-software