<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="yui_3_16_0_1_1421977166232_30956">Hi Mark</div><div id="yui_3_16_0_1_1421977166232_30955"><br></div><div dir="ltr" id="yui_3_16_0_1_1421977166232_30788">I agree, we have to consider also aspects like how easy to extract for an event. For Haiyan, we had a specific tag. But what, if it would have be necessary to add tags recently for Hagupit?</div><div id="yui_3_16_0_1_1421977166232_31070" dir="ltr"><br></div><div id="yui_3_16_0_1_1421977166232_31069" dir="ltr">About SQL queries, are-they any efficient way (time related) to say</div><div id="yui_3_16_0_1_1421977166232_31068" dir="ltr">select objects where key contains "haiyan" ?<br></div><div id="yui_3_16_0_1_1421977166232_30787"><span></span></div><div id="yui_3_16_0_1_1421977166232_30559"> </div><div id="yui_3_16_0_1_1421977166232_30560" class="signature"><span style="font-style:italic;color:rgb(0, 0, 191);font-weight:bold;">Pierre <br></span></div><br> <div id="yui_3_16_0_1_1421977166232_30585" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 13px;"> <div id="yui_3_16_0_1_1421977166232_30584" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div id="yui_3_16_0_1_1421977166232_30583" dir="ltr"> <hr size="1"> <font id="yui_3_16_0_1_1421977166232_30586" size="2" face="Arial"> <b><span style="font-weight:bold;">De :</span></b> Markware Software Services <markwaresoftware@gmail.com><br> <b><span style="font-weight: bold;">À :</span></b> Pierre Béland <pierzenh@yahoo.fr> <br><b><span style="font-weight: bold;">Cc :</span></b> HOT Openstreetmap <hot@openstreetmap.org>; S Volk <svolk2@hotmail.com> <br> <b><span style="font-weight: bold;">Envoyé le :</span></b> Jeudi 22 janvier 2015 21h21<br> <b><span style="font-weight: bold;">Objet :</span></b> Re: [HOT] Damage evaluation tagging schema<br> </font> </div> <div id="yui_3_16_0_1_1421977166232_30590" class="y_msg_container"><br><div id="yiv0955663203"><div id="yui_3_16_0_1_1421977166232_30589"><div id="yui_3_16_0_1_1421977166232_30588" dir="ltr">Hi Pierre<div id="yui_3_16_0_1_1421977166232_30587"><br clear="none"></div><div id="yui_3_16_0_1_1421977166232_30591">Excellent Thoughts. Interestingly, I am working on a 3D rendering of buildings project now, and was planning on extending this to HOT's work when done with the commercial project.</div><div id="yui_3_16_0_1_1421977166232_30957"><br clear="none"></div><div id="yui_3_16_0_1_1421977166232_30595">Having everything in one tag "k=" as you propose helps the query and rendering scenario a lot. The only downside from a database perspective would be if you ever needed to query for data within the key data itself. This would be very slow. <br clear="none"></div><div id="yui_3_16_0_1_1421977166232_30596"><br clear="none"></div><div id="yui_3_16_0_1_1421977166232_30958">For Example: if someone wanted to display all Haiyan related data the query would be something like <b id="yui_3_16_0_1_1421977166232_30980">WHERE k is Not Null and lower(k) LIKE "haiyan%"</b> which would trigger a sequential Pattern Match Scan. <b>k</b> would need to be indexed, which would help somewhat.</div><div id="yui_3_16_0_1_1421977166232_30597"><br clear="none"></div><div id="yui_3_16_0_1_1421977166232_30598">One option would be to consider a couple of specific tags to help any searches on columns that can be indexed, like </div><div id="yui_3_16_0_1_1421977166232_30599"><br clear="none"></div><div id="yui_3_16_0_1_1421977166232_30600"><b>hot:damage</b>=type of damage string (as per your proposal)</div><div id="yui_3_16_0_1_1421977166232_30601"><b>hot:crisis</b>=Haiyan</div><div id="yui_3_16_0_1_1421977166232_30602"><br clear="none"></div><div id="yui_3_16_0_1_1421977166232_30603">This would allow rapid extraction of all Haiyan related data using indexes with a query like <b id="yui_3_16_0_1_1421977166232_30604">WHERE hot:damage is not null and lower(hot:crisis)="haiyan";</b><br clear="none"></div><div id="yui_3_16_0_1_1421977166232_31001"><br clear="none"></div><div id="yui_3_16_0_1_1421977166232_30605">Also, consider adding "hot:" to the tag as this makes it very clear where the data source is.</div><div id="yui_3_16_0_1_1421977166232_31002"><br clear="none"></div><div id="yui_3_16_0_1_1421977166232_31003">Just some thoughts for you to consider</div><div id="yui_3_16_0_1_1421977166232_31004"><br clear="none"></div><div id="yui_3_16_0_1_1421977166232_30606"><br clear="none"></div><div id="yui_3_16_0_1_1421977166232_31005">Also, Do you have a summary of what tagging schemes were actually used during Haiyan, I seem to recall building=damaged, or building=yes, damage=*</div><div id="yui_3_16_0_1_1421977166232_31021"><br clear="none"></div></div><div id="yui_3_16_0_1_1421977166232_30779" class="yiv0955663203gmail_extra"><br clear="all"><div id="yui_3_16_0_1_1421977166232_30778"><div id="yui_3_16_0_1_1421977166232_30777" class="yiv0955663203gmail_signature"><div id="yui_3_16_0_1_1421977166232_30776" dir="ltr"><div id="yui_3_16_0_1_1421977166232_30775"><br clear="none"></div><div>Regards</div><div><br clear="none"></div><div>Mark Cupitt</div><div><br clear="none"></div><div><div>"If we change the world, let it bear the mark of our intelligence"</div><div><br clear="none"></div><div><a rel="nofollow" shape="rect" target="_blank" href="https://www.openstreetmap.org/user/Mark_Cupitt">See me on Open Street Map</a><br clear="none"></div><div><a href="" rel="nofollow" shape="rect"></a><div><br clear="none"></div></div><div><a rel="nofollow" shape="rect" target="_blank" href="http://ph.linkedin.com/in/markcupitt">See me on LinkedIn</a><br clear="none"><img data-id="ba75241a-98b3-ffc7-8e95-fbd4a34fe449"><br clear="none"></div><span style="font-family:arial black, sans-serif;"></span><div><span style="font-family:arial black, sans-serif;"><br clear="none"></span></div><b><a rel="nofollow" shape="rect" target="_blank" href="http://gis.stackexchange.com/users/17846/mark-c">See me on StackExchange</a><br clear="none"></b><img data-id="ce9ded60-278c-84ae-e0b9-5786a1228372"><br clear="none"></div><div>===============================================================================================</div><div>The contents of this email are intended only for the individual(s) to whom it is addressed and may contain</div><div>confidential or privileged information. If you are not the intended recipient, you must not disclose, copy, distribute,</div><div>or use the contents of this email. If you have received this email in error, please notify the sender immediately and</div><div>delete the email and any attachments.<br clear="none"></div><div>
===============================================================================================
</div></div></div></div>
<br clear="none"><div class="yiv0955663203gmail_quote">On Fri, Jan 23, 2015 at 9:33 AM, Pierre Béland <span dir="ltr"><<a rel="nofollow" shape="rect" ymailto="mailto:pierzenh@yahoo.fr" target="_blank" href="mailto:pierzenh@yahoo.fr">pierzenh@yahoo.fr</a>></span> wrote:<br clear="none"><blockquote class="yiv0955663203gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="qtdSeparateBR"><br><br></div><div class="yiv0955663203yqt9280083500" id="yiv0955663203yqt71132"><div><div style="color:#000;background-color:#fff;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:13px;"><div dir="ltr"></div><div><div>From the discusssion about mapping North of Nigeria, I open a distinct thread about the Damage evaluation discussion about the more technical aspects related to Damage evaluation and tagging schema.<br clear="none"></div></div><br clear="none"><div dir="ltr">This wiki page describes the schema used for the Haiyan typhoon.</div><div dir="ltr"><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"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><div dir="ltr"><span>As we discussed at the beginning of the Haiyan activation, while establishing a temporary schema, this was be revised later to not affect tags such as building or
highway. Distinct tags should be added to reflect damages, road
obstacles, debris or any other damage related objects. Any modifications will also have to be reflected in the humanitarian style to have the capacity to show damages on the map as we did for Haiyan.<br clear="none"></span></div><br clear="none"><div dir="ltr"><span>While the BaseMap is our priority, there might be some emergencies where we are asked to collaborate to Damage evaluation. For each of these events, we have to discuss among us and carefully evaluate if it is pertinent to do so. <br clear="none"></span></div><div dir="ltr"><span><br clear="none"></span></div><div dir="ltr"><span>Methodology is an other aspect. As it was discussed after Haiyan, there are limits to what can be done with Imagery. We cannot have the same classification / hierarchy of damages from an aerial evaluation (often poor quality images in the context of climate related disasters) and field evaluation.</span></div><br clear="none"><span></span></div><div dir="ltr"><div dir="ltr"><span>While we might decide to not do these evaluations, it is important to establish a good tagging schema and be ready for our next such action.</span></div><div dir="ltr"><span><br clear="none"></span></div><div><span>It dont think that this is a solution to have two attributes on the same key like <b>building="commercial; damaged"</b>. It would be more difficult to query and this would breaks the rules for the map renderer styles. </span></div></div><div dir="ltr"><br clear="none"><span></span></div><div dir="ltr"><span>There
are also discussions about adding permanently tags to the database and
later not revising it. More then a year after Haiyan, there are still a
lot of damage related tags. I have started to analyze how to revise
this. But not yet processed.</span></div><div dir="ltr"><span><br clear="none"></span></div><div dir="ltr"><span>There are various aspects to consider. <br clear="none"></span></div><div dir="ltr"><span>- Use a map style to render damages (like the Humanitarian style for Haiyan)</span></div><div dir="ltr"><span>- Distinct methodology for aerial views or survey evaluations -> Specific role + limits of aerial views vs structure damages</span></div><div dir="ltr"><span>- Evaluation vs Revision (either imagery or field survey)<br clear="none"></span></div><div><br clear="none"></div><div dir="ltr">The
objects to evaluate can vary from one disaster to the other. From
the Haiyan experience, below I present proposals for tagging schema specific
to an event. In this example, in the context of the Haiyan typhoon damages. Tnis same logic could be extended
to objects affected by other type of disasters. <br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr">There are also various evaluation actions and status of actions that sometimes need to be registered.</div><div dir="ltr">- Type of action: aerial evaluation and revision, field evaluation and revision</div><div dir="ltr">- Status of the revision : cloud coverage limited the evaluation.</div><div dir="ltr"><br clear="none"></div><div dir="ltr">The OSM key could be structured with various levels separated by semi-colons (ie damage:evaluation:building:haiyan).</div><div dir="ltr"><br clear="none"></div><div dir="ltr">If both evaluation and revision key where present, the style renderer rules could give a priority of revision over evaluation tags.<br clear="none"></div><div dir="ltr"><div dir="ltr"><span><br clear="none"></span></div><blockquote><div dir="ltr"><span>damage:evaluation:building:haiyan=no_damage</span></div><div dir="ltr"><span>would supersede</span><span><span><span><span><span> effect of<br clear="none"></span></span></span></span></span></div><div dir="ltr"><span>damage:revision:building:haiyan=collapsed</span></div></blockquote></div><br clear="none"><div dir="ltr">Level</div><div dir="ltr">===========================<br clear="none"></div><div dir="ltr">1 damage</div><div dir="ltr">2. evaluation, revision<br clear="none"></div><div dir="ltr">3. type, building, barrier, debris</div><div dir="ltr">4. event (ie. haiyan)</div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><div dir="ltr"><span>key value</span></div><div dir="ltr"><span>--------------------------------------------------------------------------------<br clear="none"></span></div><div dir="ltr"><span>damage:evaluation:type:haiyan imagery, survey</span></div></div><div><span>damage:revision:type:haiyan imagery, survey</span><span></span><span></span></div><div dir="ltr"><div dir="ltr"><div dir="ltr"><span><br clear="none"></span></div><div dir="ltr"><div dir="ltr"><span>damage:evaluation:building:haiyan damaged, collapsed, no</span><span><span><span><span><span><br clear="none"></span></span></span></span></span></div></div><div dir="ltr"><span>damage:revision:building:haiyan damage, collapsed, no</span><span><span><span><span><span><br clear="none"></span></span></span></span></span></div><div dir="ltr"><span> </span><span><span><span><span><span></span></span></span></span></span></div><div dir="ltr"><br clear="none"></div><div dir="ltr">Highway Barrier on nodes</div><div dir="ltr"><span><span><span><span><span><br clear="none"></span></span></span></span></span></div></div><span></span><div dir="ltr"><div dir="ltr"><span>damage:evaluation:barrier:haiyan debris, no<br clear="none"></span><span><span><span></span></span></span></div><div dir="ltr"><span>damage:revision:barrier:haiyan debris, no<br clear="none"></span><span><span><span></span></span></span></div><div dir="ltr"><br clear="none"></div><div dir="ltr">Impassable highway sections</div><div dir="ltr"><br clear="none"></div><div dir="ltr"><span>damage:evaluation:status:haiyan impassable, passable<br clear="none"></span></div><div dir="ltr"><br clear="none"></div><div dir="ltr">Area Debris<br clear="none"></div><div dir="ltr"><span><br clear="none"></span></div><div dir="ltr"><span>damage:evaluation:landuse:haiyan brownfield, no<br clear="none"></span><span><span><span></span></span></span></div><div dir="ltr"><span>damage:revision:landuse:haiyan brownfield, no<br clear="none"></span><span><span><span></span></span></span></div><div dir="ltr"><br clear="none"></div><div dir="ltr"><br clear="none"></div></div><div dir="ltr"><br clear="none"></div></div><div dir="ltr"><br clear="none"></div><div dir="ltr">Example<span><span><span><span><span><span></span></span></span></span></span></span><span></span><span> </span><br clear="none"><br clear="none"></div><div dir="ltr"><span> <tag k='building' v='yes' /><br clear="none"> <tag k='damage:evaluation:type:haiyan' v='imagery' /></span></div><div dir="ltr"><span> <tag k='damage:evaluation:building:haiyan' v='damaged' /></span><span><span><span><span><span><br clear="none"></span></span></span></span></span></div><div><span> <tag k='damage:revision:type:haiyan' v='imagery' /></span><span></span><span></span></div><div dir="ltr"><span> <tag k='damage:revision:building:haiyan' v='collapsed' /></span><span><span><span><span><span><br clear="none"></span></span></span></span></span></div><span></span><div dir="ltr"><div dir="ltr"><span> <tag k='damage:revision:type:haiyan' v='survey' /></span><span></span><span></span></div><div dir="ltr"><span> <tag k='damage:revision:building:haiyan' v='collapsed' /></span><span><span><span><span><span><br clear="none"></span></span></span></span></span></div><span></span><div dir="ltr"><br clear="none"></div></div><div><span> <tag k='highway' v='trunk' /></span><span></span></div><div><span> <tag k='damage:evaluation:haiyan' v='yes' /></span></div><div dir="ltr"><span> <tag k='damage:revision:haiyan' v='yes' /></span></div><span></span><span></span><span> <tag k='damage:evaluation:barrier:haiyan' v='debris' /><br clear="none"></span><span><span><span> <tag k='damage:evaluation:type' v='imagery' /><br clear="none"></span><span><span></span></span> <tag k='damage:revision:debris:haiyan' v='no' /><br clear="none"></span></span><span><span><span><span> <tag k='damage:revision:type' v='survey' /><br clear="none"></span><span><span></span></span></span></span> <tag k=damage:haiyan' v='yes' /><span class="yiv0955663203HOEnZb"><font color="#888888"><br clear="none"></font></span></span><span class="yiv0955663203HOEnZb"><font color="#888888"><br clear="none"><br clear="none"></font></span><div><span style="font-style:italic;color:rgb(0,0,191);font-weight:bold;">Pierre <br clear="none"></span></div></div></div></div><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"></blockquote></div><br clear="none"></div></div></div><br><br></div> </div> </div> </div></body></html>