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

Lars-Daniel Weber Lars-Daniel.Weber at gmx.de
Mon Oct 7 18:16:02 UTC 2019

From: "Kathleen Lu via legal-talk" <legal-talk at openstreetmap.org>
> 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

Okay, thanks for clarification. Then the specific column is under ODbL and the other columns can be proprietary.
But I need to tell others, not to compare both ZIPs datasets and get "the best of both worlds", right?

> (However, I am doubtful that the ZIPs would be considered
> nonsubstantial, since that definition is not based on how many columns
> of OSM is used.)

Ah okay, there's the 100 features directive in OSM, which I didn't know about.

More information about the legal-talk mailing list