<html><head></head><body><div style="color:#000; background-color:#fff; font-family:verdana, helvetica, sans-serif;font-size:13px"><div class="" id="yui_3_16_0_1_1446477076198_34517" dir="ltr">#DigiRevCMI New Information Technology Tools in 21st Century Politics</div><div id="yui_3_16_0_1_1446477076198_34477" dir="ltr"><a id="yui_3_16_0_1_1446477076198_33954" href="http://www.cmi.no/news/?1585-digital-revolutions">http://www.cmi.no/news/?1585-digital-revolutions</a></div><div id="yui_3_16_0_1_1446477076198_34008" dir="ltr"><br></div><div id="yui_3_16_0_1_1446477076198_34563" dir="ltr">My presention yesterday was the opportunity to review that last major OpenSteetMap / HOT Responses in the context of disaster and to show the various management aspects of such interventions plus quality problems / management in the context of such responses.</div><div id="yui_3_16_0_1_1446477076198_34657" dir="ltr"><a id="yui_3_16_0_1_1446477076198_34658" href="https://twitter.com/pierzen/status/661120335845138432">https://twitter.com/pierzen/status/661120335845138432</a><br></div><div id="yui_3_16_0_1_1446477076198_34657"><br></div><div dir="ltr" id="yui_3_16_0_1_1446477076198_34982">I presented briefly the Semantic analysis I started of the 2015 Nepal response. Looking at the OSM Planet File for 2015-04-24 (before the Response) and 2015-06-07 (After the response), I measured how the objects are related to OSM features. This important measure of quality, completes other quality measures of OSM data. It also gives us a global measure of quality, and can help us monitor the progression of the crowdsource effort and detect rapidly some tagging problems. The first step is to relate parents / childs (ie. relation, way, node) and find the tags that describe each OSM Feature.<br></div><div id="yui_3_16_0_1_1446477076198_34962"><br></div><div dir="ltr" id="yui_3_16_0_1_1446477076198_34981">Either before or after the Nepal Response, only 1% of the objects cannot be related to a feature such as highway, building, amenity, etc. No key / value combination listed on the OSM Map Features wiki page (plus specific HOT disaster keys). A 1% error shows a high ontologic precision of the data produced. Data with no feature, is Invisible data. Either, there was syntax error in the key / value, no tag, or a contributor simply added a name or note. We need to look more closely at such patterns and find ways to correct them rapidly.</div><div id="yui_3_16_0_1_1446477076198_35533" dir="ltr"><br></div><div id="yui_3_16_0_1_1446477076198_35404" dir="ltr">To show how we can focus on this "Invisible Data" and cure it, I created the JOSM NoFeature Mappaint style. It can be selected from the JOSM Mappaint Preferences. <a id="yui_3_16_0_1_1446477076198_35633" href="https://josm.openstreetmap.de/wiki/Styles/NoFeature">https://josm.openstreetmap.de/wiki/Styles/NoFeature</a>. This Style shows the key-value combinations I selected for my OSM data analysis. I invite HOT Validators to use this style and test it while validating data.<br></div><div id="yui_3_16_0_1_1446477076198_35692" dir="ltr"><br></div><div id="yui_3_16_0_1_1446477076198_35405">We also have access to dynamic data (ie data created, modified, deleted). I will analyze more in detail and try to identify patterns. Monitoring semantic quality of data produced can help to correct rapidly, revise instructions, etc.<br></div><div id="yui_3_16_0_1_1446477076198_35406"><br></div><div id="yui_3_16_0_1_1446477076198_35519" dir="ltr">This two day workshop is a great opportunity to discuss with other Digital Humanitarian Network contributors and thanks to Per Aarvik from SBTF and Bergen Universiy who organized this workshop.<br></div> <br><div id="yui_3_16_0_1_1446477076198_33942" class="signature"><span id="yui_3_16_0_1_1446477076198_33941" style="font-style:italic;color:rgb(0, 0, 191);font-weight:bold;"><font id="yui_3_16_0_1_1446477076198_34479" face="garamond, new york, times, serif">Pierre </font><br></span></div></div></body></html>