<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px"><div id="yiv4125796376"><div id="yui_3_16_0_1_1421985085995_2643"><div id="yui_3_16_0_1_1421985085995_2642" style="color:#000;background-color:#fff;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px;"><div id="yiv4125796376yui_3_16_0_1_1421977166232_29717">Hi Rafael,</div><div id="yiv4125796376yui_3_16_0_1_1421977166232_31796"><br clear="none"></div><div dir="ltr" id="yiv4125796376yui_3_16_0_1_1421977166232_31797">There can be more then one step of evaluation and this both for evaluations based on imagery or field survey. <br clear="none"></div><div dir="ltr" id="yiv4125796376yui_3_16_0_1_1421977166232_31798"><br clear="none"></div><div dir="ltr" id="yiv4125796376yui_3_16_0_1_1421977166232_31799">For Haiyan we did</div><div dir="ltr" id="yiv4125796376yui_3_16_0_1_1421977166232_31800">1. Aerial imagery evaluation</div><div dir="ltr" id="yiv4125796376yui_3_16_0_1_1421977166232_31801">2. Aerial imagery revision (later revising objects already evaluated)</div><div dir="ltr" id="yiv4125796376yui_3_16_0_1_1421977166232_31802">3. Red Cross did some Field survey evaluations.<br clear="none"></div><div id="yiv4125796376yui_3_16_0_1_1421977166232_29716"><br clear="none"></div><div dir="ltr" id="yiv4125796376yui_3_16_0_1_1421977166232_29715"><span id="yiv4125796376yui_3_16_0_1_1421977166232_32685">About the order of elements, I thought that this order would faciliate queries. <br clear="none"></span></div><div class="yiv4125796376" dir="ltr" id="yiv4125796376yui_3_16_0_1_1421977166232_32686" style=""><span class="yiv4125796376" id="yiv4125796376yui_3_16_0_1_1421977166232_35206" style="">For example</span></div><div class="yiv4125796376" dir="ltr" id="yiv4125796376yui_3_16_0_1_1421977166232_32687" style=""><span class="yiv4125796376" id="yiv4125796376yui_3_16_0_1_1421977166232_35207" style="">select key=</span>damage:evaluation:</div><div class="yiv4125796376" dir="ltr" id="yiv4125796376yui_3_16_0_1_1421977166232_32688" style=""><span class="yiv4125796376" id="yiv4125796376yui_3_16_0_1_1421977166232_35208" style="">select key=</span>damage:evaluation:barrier:</div><div dir="ltr" id="yiv4125796376yui_3_16_0_1_1421977166232_35571"><span id="yiv4125796376yui_3_16_0_1_1421977166232_32685"><br clear="none"></span></div><div dir="ltr" id="yiv4125796376yui_3_16_0_1_1421977166232_35573"><div id="yui_3_16_0_1_1421985085995_2835"><span id="yiv4125796376yui_3_16_0_1_1421977166232_32685">Overpass Regex query can be used except I think adding a negation. <br></span></div><div dir="ltr" id="yui_3_16_0_1_1421985085995_2798"><span id="yiv4125796376yui_3_16_0_1_1421977166232_32685">see <a id="yui_3_16_0_1_1421985085995_2802" href="http://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL#Key.2Fvalue_matches_regular_expression_.28.7E.22key_regex.22.7E.22value_regex.22.29">http://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL#Key.2Fvalue_matches_regular_expression_.28.7E.22key_regex.22.7E.22value_regex.22.29</a><br></span></div><div id="yui_3_16_0_1_1421985085995_2832"><span id="yiv4125796376yui_3_16_0_1_1421977166232_32685"><br></span></div><div id="yui_3_16_0_1_1421985085995_2961"><span id="yiv4125796376yui_3_16_0_1_1421977166232_32685">Would it be efficient to make</span><span id="yiv4125796376yui_3_16_0_1_1421977166232_32685"> efficient Regex queries with postgresql? Then, </span><span id="yiv4125796376yui_3_16_0_1_1421977166232_32685">I think that the order of the elements would be less a problem.</span> </div></div><div id="yiv4125796376yui_3_16_0_1_1421977166232_29714"><div dir="ltr" id="yiv4125796376yui_3_16_0_1_1421977166232_35209"><br clear="none"></div><div class="yiv4125796376" dir="ltr" id="yiv4125796376yui_3_16_0_1_1421977166232_32690" style=""> </div></div><div class="yiv4125796376signature" id="yiv4125796376yui_3_16_0_1_1421977166232_29713"><span id="yiv4125796376yui_3_16_0_1_1421977166232_31987" style="font-style:italic;color:rgb(0, 0, 191);font-weight:bold;">Pierre <br clear="none"></span></div><br clear="none"> <div id="yiv4125796376yui_3_16_0_1_1421977166232_29655" style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px;"> <div id="yiv4125796376yui_3_16_0_1_1421977166232_29654" style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div dir="ltr" id="yiv4125796376yui_3_16_0_1_1421977166232_29653"> <hr id="yiv4125796376yui_3_16_0_1_1421977166232_32331" size="1"> <font id="yiv4125796376yui_3_16_0_1_1421977166232_29652" size="2" face="Arial"> <b><span style="font-weight:bold;">De :</span></b> Rafael Avila Coya <ravilacoya@gmail.com><br clear="none"> <b><span style="font-weight:bold;">À :</span></b> hot@openstreetmap.org <br clear="none"> <b id="yiv4125796376yui_3_16_0_1_1421977166232_31989"><span id="yiv4125796376yui_3_16_0_1_1421977166232_31988" style="font-weight:bold;">Envoyé le :</span></b> Jeudi 22 janvier 2015 21h24<br clear="none"> <b><span style="font-weight:bold;">Objet :</span></b> Re: [HOT] Damage evaluation tagging schema<br clear="none"> </font> </div> <div class="qtdSeparateBR"><br><br></div><div class="yiv4125796376yqt5683243218" id="yiv4125796376yqt06944"><div class="yiv4125796376y_msg_container" id="yiv4125796376yui_3_16_0_1_1421977166232_31790"><br clear="none">Hi Pierre:<br clear="none"><br clear="none">I like this schema. Only two questions:<br clear="none"><br clear="none">What do you mean with evaluation and revision?<br clear="none">Why not the event in 3rd and type of object at the end?<br clear="none"><br clear="none">Cheers,<br clear="none"><br clear="none">Rafael.<br clear="none"><br clear="none">On 23/01/15 02:33, Pierre Béland wrote:<br clear="none">> From the discusssion about mapping North of Nigeria, I open a distinct<br clear="none">> thread about the Damage evaluation discussion about the more technical<br clear="none">> aspects related to Damage evaluation and tagging schema.<br clear="none">> <br clear="none">> This wiki page describes the schema used for the Haiyan typhoon.<br clear="none">> <a rel="nofollow" shape="rect" target="_blank" href="http://wiki.openstreetmap.org/wiki/Damaged_buildings_crisis_mapping">http://wiki.openstreetmap.org/wiki/Damaged_buildings_crisis_mapping</a><br clear="none">> <br clear="none">> As we discussed at the beginning of the Haiyan activation, while<br clear="none">> establishing a temporary schema, this was be revised later to not affect<br clear="none">> tags such as building or highway. Distinct tags should be added to<br clear="none">> reflect damages, road obstacles, debris or any other damage related<br clear="none">> objects. Any modifications will also have to be reflected in the<br clear="none">> humanitarian style to have the capacity to show damages on the map as we<br clear="none">> did for Haiyan.<br clear="none">> <br clear="none">> While the BaseMap is our priority, there might be some emergencies where<br clear="none">> we are asked to collaborate to Damage evaluation. For each of these<br clear="none">> events, we have to discuss among us and carefully evaluate if it is<br clear="none">> pertinent to do so.<br clear="none">> <br clear="none">> Methodology is an other aspect. As it was discussed after Haiyan, there<br clear="none">> are limits to what can be done with Imagery. We cannot have the same<br clear="none">> classification / hierarchy of damages from an aerial evaluation (often<br clear="none">> poor quality images in the context of climate related disasters) and<br clear="none">> field evaluation.<br clear="none">> <br clear="none">> While we might decide to not do these evaluations, it is important to<br clear="none">> establish a good tagging schema and be ready for our next such action.<br clear="none">> <br clear="none">> It dont think that this is a solution to have two attributes on the same<br clear="none">> key like *building="commercial; damaged"*. It would be more difficult to<br clear="none">> query and this would breaks the rules for the map renderer styles. <br clear="none">> <br clear="none">> There are also discussions about adding permanently tags to the database<br clear="none">> and later not revising it. More then a year after Haiyan, there are<br clear="none">> still a lot of damage related tags. I have started to analyze how to<br clear="none">> revise this. But not yet processed.<br clear="none">> <br clear="none">> There are various aspects to consider.<br clear="none">> - Use a map style to render damages (like the Humanitarian style for Haiyan)<br clear="none">> - Distinct methodology for aerial views or survey evaluations -> <br clear="none">> Specific role + limits of aerial views vs structure damages<br clear="none">> - Evaluation vs Revision (either imagery or field survey)<br clear="none">> <br clear="none">> The objects to evaluate can vary from one disaster to the other. From<br clear="none">> the Haiyan experience, below I present proposals for tagging schema<br clear="none">> specific to an event. In this example, in the context of the Haiyan<br clear="none">> typhoon damages. Tnis same logic could be extended to objects affected<br clear="none">> by other type of disasters. <br clear="none">> <br clear="none">> There are also various evaluation actions and status of actions that<br clear="none">> sometimes need to be registered.<br clear="none">> - Type of action: aerial evaluation and revision, field evaluation and<br clear="none">> revision<br clear="none">> - Status of the revision : cloud coverage limited the evaluation.<br clear="none">> <br clear="none">> The OSM key could be structured with various levels separated by<br clear="none">> semi-colons (ie damage:evaluation:building:haiyan).<br clear="none">> <br clear="none">> If both evaluation and revision key where present, the style renderer<br clear="none">> rules could give a priority of revision over evaluation tags.<br clear="none">> <br clear="none">> damage:evaluation:building:haiyan=no_damage<br clear="none">> would supersedeeffect of<br clear="none">> damage:revision:building:haiyan=collapsed<br clear="none">> <br clear="none">> <br clear="none">> Level<br clear="none">> ===========================<br clear="none">> 1 damage<br clear="none">> 2. evaluation, revision<br clear="none">> 3. type, building, barrier, debris<br clear="none">> 4. event (ie. haiyan)<br clear="none">> <br clear="none">> <br clear="none">> key value<br clear="none">> --------------------------------------------------------------------------------<br clear="none">> damage:evaluation:type:haiyan imagery, survey<br clear="none">> damage:revision:type:haiyan imagery, survey<br clear="none">> <br clear="none">> damage:evaluation:building:haiyan damaged, collapsed, no<br clear="none">> damage:revision:building:haiyan damage, collapsed, no<br clear="none">> <br clear="none">> <br clear="none">> Highway Barrier on nodes<br clear="none">> <br clear="none">> damage:evaluation:barrier:haiyan debris, no<br clear="none">> damage:revision:barrier:haiyan debris, no<br clear="none">> <br clear="none">> Impassable highway sections<br clear="none">> <br clear="none">> damage:evaluation:status:haiyan impassable, passable<br clear="none">> <br clear="none">> Area Debris<br clear="none">> <br clear="none">> damage:evaluation:landuse:haiyan brownfield, no<br clear="none">> damage:revision:landuse:haiyan brownfield, no<br clear="none">> <br clear="none">> <br clear="none">> <br clear="none">> <br clear="none">> Example<br clear="none">> <br clear="none">> <tag k='building' v='yes' /><br clear="none">> <tag k='damage:evaluation:type:haiyan' v='imagery' /><br clear="none">> <tag k='damage:evaluation:building:haiyan' v='damaged' /><br clear="none">> <tag k='damage:revision:type:haiyan' v='imagery' /><br clear="none">> <tag k='damage:revision:building:haiyan' v='collapsed' /><br clear="none">> <tag k='damage:revision:type:haiyan' v='survey' /><br clear="none">> <tag k='damage:revision:building:haiyan' v='collapsed' /><br clear="none">> <br clear="none">> <tag k='highway' v='trunk' /><br clear="none">> <tag k='damage:evaluation:haiyan' v='yes' /><br clear="none">> <tag k='damage:revision:haiyan' v='yes' /><br clear="none">> <tag k='damage:evaluation:barrier:haiyan' v='debris' /><br clear="none">> <tag k='damage:evaluation:type' v='imagery' /><br clear="none">> <tag k='damage:revision:debris:haiyan' v='no' /><br clear="none">> <tag k='damage:revision:type' v='survey' /><br clear="none">> <tag k=damage:haiyan' v='yes' /><br clear="none">> <br clear="none">> <br clear="none">> Pierre<br clear="none">> <br clear="none">> <br clear="none">> _______________________________________________<br clear="none">> HOT mailing list<br clear="none">> <a rel="nofollow" shape="rect" ymailto="mailto:HOT@openstreetmap.org" target="_blank" href="mailto:HOT@openstreetmap.org">HOT@openstreetmap.org</a><br clear="none">> <a rel="nofollow" shape="rect" target="_blank" href="https://lists.openstreetmap.org/listinfo/hot">https://lists.openstreetmap.org/listinfo/hot</a><br clear="none">> <br clear="none"><br clear="none">-- <br clear="none">Twitter: <a rel="nofollow" shape="rect" target="_blank" href="http://twitter.com/ravilacoya">http://twitter.com/ravilacoya</a><br clear="none"><br clear="none">--------------------------------<br clear="none"><br clear="none">Por favor, non me envíe documentos con extensións .doc, .docx, .xls,<br clear="none">.xlsx, .ppt, .pptx, aínda podendoo facer, non os abro.<br clear="none"><br clear="none">Atendendo á lexislación vixente, empregue formatos estándares e abertos.<br clear="none"><br clear="none"><a rel="nofollow" shape="rect" target="_blank" href="http://es.wikipedia.org/wiki/OpenDocument#Tipos_de_ficheros">http://es.wikipedia.org/wiki/OpenDocument#Tipos_de_ficheros</a><div class="yiv4125796376qtdSeparateBR"><br clear="none"><br clear="none"></div><div class="yiv4125796376yqt6015571285" id="yiv4125796376yqtfd00753"><br clear="none"><br clear="none">_______________________________________________<br clear="none">HOT mailing list<br clear="none"><a rel="nofollow" shape="rect" ymailto="mailto:HOT@openstreetmap.org" target="_blank" href="mailto:HOT@openstreetmap.org">HOT@openstreetmap.org</a><br clear="none"><a rel="nofollow" shape="rect" target="_blank" href="https://lists.openstreetmap.org/listinfo/hot">https://lists.openstreetmap.org/listinfo/hot</a><br clear="none"></div><br clear="none"><br clear="none"></div></div> </div> </div> </div></div></div></div></body></html>