Find research datasets worth reusing

OSHDB - OpenStreetMap History Data Analysis

<p>A high-performance framework for spatio-temporal data analysis of OpenStreetMap full-history data. Developed by <a href="https://heigit.org">HeiGIT</a> as part of the <a href="https://ohsome.org/">ohsome project</a>.</p> <p><em>Code is hosted on github: <a href="https://github.com/giscience/oshdb">https://github.com/giscience/oshdb</a>.</em></p> <p>The OSHDB allows to investigate the evolution of the amount of data and the contributions to the OpenStreetMap project. It combines easy access to the historical OSM data with high querying performance. Use cases of the OSHDB include data quality analysis, computing of aggregated data statistics and OSM data extraction. The main functionality of the OSHDB is explained in the <a href="https://github.com/GIScience/oshdb/blob/master/documentation/first-steps/README.md">first steps tutorial</a>.</p> <p><strong>OpenStreetMap History Data</strong></p> <p><a href="https://www.openstreetmap.org/">OpenStreetMap</a> contains a large variety of geographic data, differing widely in scale and feature type. OSM contains everything from single points of interests to whole country borders, from concrete things like buildings up to more abstract concepts such as turn restrictions. OSM also offers metadata about the <a href="https://wiki.openstreetmap.org/wiki/Planet.osm/full">history</a> and the modifications that are made to the data, which can be analyzed in a multitude of ways.</p> <p>Because of it&#39;s size and variety, possibilities of working with OSM history data are limited and there exists a lack of an easy-to-use analysis software. A goal of the OSHDB is to make OSM data more accessible to researchers, data journalists, community members and other interested people.</p> <p><strong>Central Concepts</strong></p> <p>The OSHDB is designed to be appropriate for a large spectrum of potential use cases and is therefore built around the following central ideas and design goals:</p> <ul> <li><em>Lossless Information</em>: The full OSM history data set should be stored and be queryable by the OSHDB, including errorneous or partially incomplete data.</li> <li><em>Simple, Generic API</em>: Writing queries with the OSHDB should be simple and intuitive, while at the same time flexbile and generic to allow a wide variety of analysis queries.</li> <li><em>High Performance</em>: The OSM history data set is large and thus requires efficiency in the way the data is stored and in the way it can be accessed and processed.</li> <li><em>Local and Distributed Deployment</em>: Analysis queries should scale well from data explorations of small regions up to global studies of the complete OSM data set.</li> </ul> <p>The OSHDB splits data storage and computations. It is then possible to use the <a href="https://en.wikipedia.org/wiki/MapReduce">MapReduce</a> programming model to analyse the data in parallel and optionally also on distributed databases. A central idea behind this concept is to bring the code to the data.</p>