<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19019"></HEAD>
<BODY bgColor=#ffffff>
<DIV dir=ltr align=left><FONT face=Tahoma>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=281295817-14032011>Hello all,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=281295817-14032011></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff face=Arial><SPAN
class=281295817-14032011><FONT size=2>I worked a lot on the Haiti map a year ago
and used, along with hundreds of others, the key=value list on this wiki:
</FONT><A
title=blocked::http://wiki.openstreetmap.org/wiki/Humanitarian_OSM_Tags/Humanitarian_Data_Background
href="http://wiki.openstreetmap.org/wiki/Humanitarian_OSM_Tags/Humanitarian_Data_Background"><FONT
size=2>http://wiki.openstreetmap.org/wiki/Humanitarian_OSM_Tags/Humanitarian_Data_Background</FONT></A></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=281295817-14032011></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff face=Arial><SPAN
class=281295817-14032011><FONT size=2>It's a lot cleaner then the long and (for
me) to complicated one mentioned earlier in this thread: </FONT><A
title=blocked::http://wiki.openstreetmap.org/wiki/Humanitarian_OSM_Tags/Humanitarian_Data_Model
href="http://wiki.openstreetmap.org/wiki/Humanitarian_OSM_Tags/Humanitarian_Data_Model"><FONT
size=2>http://wiki.openstreetmap.org/wiki/Humanitarian_OSM_Tags/Humanitarian_Data_Model</FONT></A></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=281295817-14032011></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=281295817-14032011>(This mail could end up twice on the list, I had
some <SPAN class=984011718-14032011>mail </SPAN>issues <SPAN
class=984011718-14032011>which</SPAN> made the list think I wasn't a member; I
hope it works now<SPAN class=984011718-14032011>.</SPAN>)</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=281295817-14032011></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=281295817-14032011>Regards,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=281295817-14032011>Hans</SPAN></FONT></DIV></FONT></DIV><BR>
<BLOCKQUOTE
style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"
dir=ltr>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> Kate Chapman [mailto:kate@maploser.com]
<BR><B>Sent:</B> 14 March 2011 17:18<BR><B>To:</B> Andy Robinson
(blackadder-lists)<BR><B>Cc:</B>
<hot@openstreetmap.org><BR><B>Subject:</B> Re: [HOT] Japan - Request for
mission details<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Yes, simple tags. The goal of the HDM was to add tags to provide
information that doesn't exist. Those tags that do exist are supposed to
be worked into the model rather than make new ones to replace the regular OSM
tags. I realize what is there now isn't perfect and could be
improved.</DIV>
<DIV><BR></DIV>
<DIV>As far was making data that makes sense to responders, processes to
create those data transformations need to be further developed.</DIV>
<DIV><BR></DIV>
<DIV>Kate<BR><BR><BR></DIV>
<DIV><BR>On Mar 14, 2011, at 7:19 AM, "Andy Robinson \(blackadder-lists\)"
<<A href="mailto:ajrlists@gmail.com">ajrlists@gmail.com</A>>
wrote:<BR><BR></DIV>
<DIV></DIV>
<BLOCKQUOTE type="cite">
<DIV>
<DIV class=WordSection1>
<P style="MARGIN-BOTTOM: 12pt"><SPAN style="FONT-SIZE: 10pt">Peter Wendorff
[<A href="mailto:wendorff@uni-paderborn.de"><A
href="mailto:wendorff@uni-paderborn.de">mailto:wendorff@uni-paderborn.de</A></A>]
wrote<BR>>Sent: 14 March 2011 11:16 AM<BR>>To: <A
href="mailto:hot@openstreetmap.org"><A
href="mailto:hot@openstreetmap.org">hot@openstreetmap.org</A></A><BR>>Subject:
Re: [HOT] Japan - Request for mission
details<BR>><BR>>Hi.<BR>>Nevertheless the questions Matthias asked
are right.<BR>>There is this HOT Data Model - but that model is not
really good for<BR>interested<BR>>mappers.<BR>>Perhaps it's useful for
organizations using the data, but I miss a landing<BR>page in<BR>>the
wiki for "tags often used in crisis mapping".<BR>>The "standard" tags are
(I hope) the usual ones, but the tags in question<BR>are<BR>>repeatingly
the same:<BR>>- how to tag a collapsed building?<BR>>- how to tag a
collapsed bridge?<BR>>- how to tag a temporary bridge build by helping
organizations?<BR>>- how to tag a place where drinking water is
availlable?<BR>>- how to tag a place where "lost+found people" are
listed?<BR>>- (how) is it possible to state pre- and post crisis
sources?<BR>><BR>>And last but not least: where and why does the
tagging differ from standard<BR>>tagging in OSM?<BR>><BR>>As far as
I can see yet, HOT targets mainly at the "backend",
organization<BR>of<BR>>aerial photographs and data sources - and trying
to support organizations<BR>>using the data. I miss the mapper as a
target, yet.<BR>><BR>>regards<BR>>Peter<BR>><BR><BR>Having had
plenty of experience in creating tags in OSM I'll give my
view.<BR><BR>Richard Fairhurst wrote <A
href="http://wiki.openstreetmap.org/wiki/Duck_tagging"><A
href="http://wiki.openstreetmap.org/wiki/Duck_tagging">http://wiki.openstreetmap.org/wiki/Duck_tagging</A></A>
as a<BR>way of communicating a very simple point. If a tag is logical then
the human<BR>brain can read it and make sense of it. If the tag needs a
translation to<BR>make sense of it then it's not doing its job properly. If
things are tagged<BR>logically and in simple form then it's easy for
mappers, especially new<BR>mappers, to understand them and use them. The
KISS approach works best (Keep<BR>it Simple, Stupid).<BR><BR>The list in
Peter's post above actually says what the tags might logically<BR>be.
E.g. Building=collapsed, bridge=collapsed,
bridge=temporary,<BR>amenity=drinking_water, emergency=missing_persons,
earthquake=yes...... you<BR>get the idea.<BR><BR>Of course this
approach doesn't necessarily help humanitarian organisations<BR>with the
efforts on the ground, they use descriptions and codes that are on<BR>the
whole alien to OSM. Mapping from OSM tags to other data exchange
formats<BR>is needed and important but it doesn't need to be done by
mappers, and nor<BR>do I think it should be. Leave abstraction to those that
can best manage the<BR>data, by all means discuss tags here but keep it to
the conventional tagging<BR>format within OSM and don't try to solve the
wider issues.<BR><BR>Cheers<BR>Andy</SPAN><O:P></O:P></P>
<DIV style="TEXT-ALIGN: center" class=MsoNormal align=center><SPAN
style="mso-fareast-font-family: 'Times New Roman'">
<HR style="COLOR: #aca899" align=center SIZE=1 width="100%" noShade>
</SPAN></DIV>
<P class=avgcert>No virus found in this message.<BR>Checked by AVG - <A
href="http://www.avg.com"><A
href="http://www.avg.com">www.avg.com</A></A><BR>Version: 10.0.1204 / Virus
Database: 1498/3505 - Release Date:
03/13/11<O:P></O:P></P></DIV></DIV></BLOCKQUOTE>
<BLOCKQUOTE type="cite">
<DIV><SPAN>_______________________________________________</SPAN><BR><SPAN>HOT
mailing list</SPAN><BR><SPAN><A
href="mailto:HOT@openstreetmap.org">HOT@openstreetmap.org</A></SPAN><BR><SPAN><A
href="http://lists.openstreetmap.org/listinfo/hot">http://lists.openstreetmap.org/listinfo/hot</A></SPAN><BR></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>