Overture Maps Foundation
overturemaps.org
overturemaps.org
a) A geospatial data revision control system? [Collaborative Map Building]
b) A new way to do geospatial indexing, or some metamanagement layer on top of one or more existing forms of geospatial indexing? [Global Entity Reference System]
c) A quality control process, tool, system or review board/certification standard? [Quality Assurance Processes]
d) Specific SQL or NoSQL reifications for binding to specific datastores? [Structured Data Schema]
You can read into these tea leaves all you want, but at the end of the day, it's all just marketecture with no actual "stuff" behind it. At least as far as you and I as rubes on the Internet are concerned. The page is very, very light on details.
Moreover, I am 100% positive that the $3,000 price tag for individuals to just poke your nose in the tent, or $300,000 to actually to have voting rights is about as anti-open source-y as you can get.
Is it just me? Is this how people expect good open source results and progress to actually occur?
What is the relationship between Overture and OpenStreetMap?
Overture is a data-centric map project, not a community of individual map editors. Therefore, Overture is intended to be complementary to OSM. We combine OSM with other sources to produce new open map data sets. Overture data will be available for use by the OpenStreetMap community under compatible open data licenses. Overture members are encouraged to contribute to OSM directly.
How will Overture data be licensed?
Data contributed to ODbL licensed datasets will be contributed under both the ODbL and CDLA permissive v2. Contributions to CDLA permissive v2 datasets will be contributed under the CDLA permissive v2. How will Overture code be licensed?
Overture’s open source code will be subject to the MIT license.
This is a problem if you have proprietary data that you want to use to augment OSM. Some interpretation here: https://wiki.osmfoundation.org/wiki/Licence/Licence_and_Lega...?
tl;dr from that document:
> "...if you improve our data and then distribute it, you need to share your improvements with the general public at no charge. A painless way to do that is to contribute your improvements directly back to OpenStreetMap."
Data sources that people commonly want to blend with mapping data have legal and regulatory restrictions with respect to privacy, data jurisdiction, acceptable use, statutory time limits, contract terms, etc. The OSM license terms are in conflict with legal and regulatory compliance requirements.
The loophole that most companies seem to have landed on is using OSM data to do parallel construction of private data, which technically avoids the Derivative Database problem.
Anything combined with OSM will be a derivative dataset. So the whole project will have to be released under the ODbL license. Or something compatible with it. I don't think this will really help anyone get away from those issues.
This reminds me of the Micro Four Thirds model, where smaller camera manufacturers teamed up to fight Canon and Nikon. This looks like a bunch of smaller map companies trying to stay relevant.
(edit: the below is incorrect, please see boise's reply below) FWIW, I believe none of the founding members generate their own mapping data the way that Google, the Census, or Here.com do. They mostly republish Census/USPS data along with relicensing ESRI or Here spatial data. So it's not even a consortium of data creators, but more like an interop group that's trying to create a competing standard to what's already out there.
Maybe if the extinguish google or esri that would be a good thing. Way too many money changers in the spatial domain. It makes me want to found a startup to democratize the democratization of democratized foo.
And it is not just about maps but as an input to other systems and models. Knowing the location of a customer, machine or business tells you a lot about it and this kind of data unlocks that.
Also, ESRI are quietly putting a lot of effort into data curation and aggregating it in one place. But whatever they build will be slow, buggy, and focused on ESRI and its customers. In fact a lot of government open data providers have been moving their portals to ESRI and access to raw flat files is being lost.