Feed on
Posts
Comments

Tag Archive 'ohsome example'

Welcome back to the second part of the blog series how to become ohsome. If you have not read the first part yet, better go and check it out now. It explains how you can create an ohsome visualization of the historical development of the OSM data from a city of your choice.
This second part shows how to use [...]

Read Full Post »

In a previous blog post we performed a conceptual compliance analysis between OSM data and several tagging-guidelines using the OSHDB API. The results were visualized in a line chart, comparing the different compliance ratio over several months. The following analysis focuses on a spatial representation of the conceptual compliance. It is [...]

Read Full Post »

This blog post is the start of a series of posts, which describe what you are able to do using the ohsome framework developed at the Heidelberg Institute of Geoinformation Technology (HeiGIT). OpenStreetMap (OSM), the biggest open map of our world, offers not only the current state of the data, but the whole historical evolution [...]

Read Full Post »

Conceptual compliance measures to what degree contributors of volunteered geographic information (VGI) are using proposed tagging-standards. Here, we look into OpenStreetMap (OSM) as the most well-known example for VGI. In OSM the most important tagging guideline is defined by its wiki. In addtion, OSM editors like iD or JOSM provide presets (default options to adhere to tagging standards).
This [...]

Read Full Post »

Our new ohsome dashboard is another preview on what is and will be possible with our ohsome OpenStreetMap history analytics platform. Behind the scenes, we added support for the Apache Ignite big data framework and deployed an instance using the full OSM history data of whole Germany on Heidelberg University’s cloud computing infrastructure heiCLOUD. Apache Ignite is an open-source [...]

Read Full Post »

In this blog post we report a small study on the size of the OpenStreetMap history data set, which we carried out in the context of developing the OSHDB. We estimated the size of OSM’s history in terms of raw data as it would be represented in a systems programming language [...]

Read Full Post »

Have a look at our new Jupyter notebook which provides a step-by-step introduction how to use the ohsome API. We show you how to analyse the OSM mapping efforts related to a HOT Tasking Manager project in Nepal. The analyzed project 1008 “Nepal Earthquake, 2015, IDP Camps in Kathmandu” was created by Kathmandu Living Labs [...]

Read Full Post »

Documentation of the Ohsome API

In a previous blog post we introduced the REST-based interface of our framework Ohsome (the OpenStreetmap History Analytics plattform) and gave an example link of a request. This blog post aims to give you some further information about the documentation of the ohsome API.
We use the Springfox Java library to create a Swagger documentation. The result can [...]

Read Full Post »

Disaster mapping activations that are supported by many volunteers with various levels of experience raise questions related to the quality of the provided Volunteered Geographic Information. Learning about the data quality that can be expected in a disaster activation helps to evaluate the quality and fitness for purpose of the OSM data.
At the ISCRAM 2018 [...]

Read Full Post »

The Ohsome Nepal Dashboard has new features to enhance its usability and functionality. The user can now easily select administrative areas of interest through a new map interface. Different administrative levels can be selected by zooming in and out and afterwards just clicking or tapping on that specific region. This convenience feature makes it much faster [...]

Read Full Post »

Older Posts »