[OSM-legal-talk] ZIP codes from OSM in non-compatible licensed dataset

Martin Koppenhoefer dieterdreist at gmail.com
Mon Oct 7 22:04:06 UTC 2019

sent from a phone

> On 7. Oct 2019, at 19:48, Kathleen Lu via legal-talk <legal-talk at openstreetmap.org> wrote:
> In my view, if you are keeping the two zip codes in different columns and not removing duplicates, then essentially what you have is one property that is "OSM ZIP" and one property that is "proprietary ZIP", and they are two different properties that are not used to improve each other, so it is a collective database per https://wiki.osmfoundation.org/wiki/Licence/Community_Guidelines/Collective_Database_Guideline_Guideline

As I read the collective db guideline, you cannot have both, the ZIP codes from your proprietary database and those from OpenStreetMap, in the same database matched to the same objects. It says “add or replace” a property (we do agree the ZIP codes are a property and not a primary feature?). If you keep both ZIP codes in your db, it implies you need both columns, which implies you are somehow mixing them at some point (or you could drop the proprietary ZIP codes, as you won’t need them)

Cheers Martin 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/legal-talk/attachments/20191008/244981c9/attachment.html>

More information about the legal-talk mailing list