MapSwipe Data Imports
Source
The much-anticipated MapSwipe 2.0 was officially launched on October 1st, 2019. Incorporating new features on top of the old, it continues to be used around the world as a 'first-filter' humanitarian digitization tool for Missing Maps Project, producing many thousands of screen-sized areas of unknown landmass, which is rapidly categorised and compiled into packages of data under three categories. These categorised and downloadable data packages pass under the labels of 'Yes', 'No', and 'Maybe' - referring to the acknowledged likelihood of human activity, as judged by individual 'Mapswiper' contributors, spotting houses, roads and landuse in rural areas.
Humanitarian Impacts of this for remote 'digital humanitarian' interventionists is massive, allowing allocation of remote-mappers to areas of risk, and saving precious time in emergency mapping ('Mapathon') initiatives.
License
MapSwipe is released under a "liberal" non-reciprocal license (Creative Commons Attribution). This only requires that users acknowledge the source. You can do whatever you want with the data, just make sure to credit the MapSwipe contributors.
Project is managed by Heidelberg Institute for Geoinformation Technology at Heidelberg University (HeiGIT gGmbH)
MapSwipe 2.0 deploys certain new features
- changes in imagery across time intervals
- automatically detect shelter features in imagery, and assign suggested digital vector data, to be validated by hand, before OSM inputting.
The latter of these significant new features requires some post-processing work, to exploit the potential of quickly uploading new buildings vector layer data to OSM. The following outlines the processes, many of which are procedural, rather than technological, for the accomplishment of this task.
Data Quality
Automatically detected shelter are validated by more than one human.
Pre-processing
Vectors of automatically recognized object are stored in database and waiting for validation. Validated data can be in GeoJson format prepared for downloading and next processing.
Work Plan
Import process
After final validation by JOSM data in smaller changesets will be uploaded, under unique user account, to OSM.