Abstract

OpenStreetMap (OSM) is a well-known crowdsourcing project which aims to create a geospatial database of the whole world. Intrinsic approaches based on the analysis of the history of data, i.e. its evolution over time, have become an established way to assess OSM quality. After a comprehensive review of scientific as well as software applications focused on the visualization, analysis and processing of OSM history, the paper presents “Is OSM up-to-date?”, an open source web application addressing the need of OSM contributors, community leaders and researchers to quickly assess OSM intrinsic quality based on the object history for any specific region. The software, mainly written in Python, can be also run in the command line or inside a Docker container. The technical architecture, sample applications and future developments of the software are also presented in the paper.

Highlights

  • OpenStreetMap (OSM) is the most successful crowdsourced geographic information project to date [1]

  • The application was born from the need to provide OSM contributors, community leaders and researchers with an easy-to-use tool for quick and intuitive assessment of history-based OSM quality for specific regions

  • There is no doubt that some classes of OSM objects are often mapped once and rarely or never updated and still may be of high quality – since they usually do not change over time – while other classes of objects are more often updated but still may be of low quality – since their details tend to change frequently

Read more

Summary

Introduction

OpenStreetMap (OSM) is the most successful crowdsourced geographic information project to date [1]. The Louvre Museum was in the past represented by another relation with id 3262297 and might be represented by new relations in the future This fundamental difference between the permanent ids of real-world features and the OSM ids of nodes, ways and relations should be properly considered when analyzing OSM history data. Software applications are grouped into the following categories: Visualization, when they display the current version (or a specific version in time) of the database and/or information on specific objects or changesets, without aggregation, processing or computation of additional information; Statistics, when they make use of OSM history to produce numerical data and/or graphs; Analysis, when they provide an interface to filter, aggregate and perform computation on OSM historical information; and Conversion, when they transform historical OSM data into formats which are more suitable for analysis.

Aim
Conclusions and future development
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.