<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 6, 2020, at 10:35 PM, Warin <<a href="mailto:61sundowner@gmail.com" class="">61sundowner@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class="">
<div class="">
<div class="moz-cite-prefix">On 7/2/20 3:47 pm, Graeme Fitzpatrick
wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:CAP4zaXocpWn37za_zzoeHyEBZqUF_+D8d_cu8VMRorSZ-_RDtA@mail.gmail.com" class="">
<meta http-equiv="content-type" content="text/html; charset=UTF-8" class="">
<div dir="ltr" class="">
<div dir="ltr" class=""><br clear="all" class="">
<br class="">
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, 7 Feb 2020 at 14:30,
Warin <<a href="mailto:61sundowner@gmail.com" moz-do-not-send="true" class="">61sundowner@gmail.com</a>>
wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div class=""><p class="">Let say a hospital has collapsed. <br class="">
</p><p class="">The crisis mapping page I linked to would have you add
the tag damaged=collapsed to the amenity=hospital. <br class="">
</p><p class="">So the render would render the hospital the same as a
fully functional hospital. That is certainly not want
I'd want. <br class="">
</p><p class=""><br class="">
</p><p class="">Better if life cycle things were rendered .. but
different from fully functional things. <br class="">
</p>
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">How about rendering a nice, big red X overlaying the
outline of the building when it's marked as disused! :-)</div>
</div>
</div>
</blockquote><p class=""><br class="">
</p><p class="">Not only buildings.. paths, roads, train stations/tracks shops,
etc. And not only disused, abandoned, razed, etc... <br class="">
</p>
Rendering is not easy. <br class="">
</div><br class=""></div></blockquote></div><br class=""><div class="">+1</div><div class=""><br class=""></div><div class="">Based on the little rendering that I’ve been doing, it seems to me that each and every feature may require different treatment when handling lifecycle tagging. I handle lifecycle tagging on buildings as there are a number of them along some of the trails I hike and they are distinct landmarks so I’d like them to be on my hiking focused maps. But my treatment of lifecycle tagging on buildings would not be suitable for rendering a ruined railway or highway bridge. I’ve yet to hike (and map) a trail that took me within sight of a ruined bridge so I haven’t thought about how it could be rendered in a manner appropriate to my general map style.</div><div class=""><br class=""></div><div class="">I think a strong argument can be made that the style used to generate the “standard” map at <a href="https://www.openstreetmap.org/" class="">https://www.openstreetmap.org/</a> should ignore ruins:* and, by extension, objects that also have “ruins=yes” tags. Though maybe it ought to treat disused:* and maybe abandoned:* as null prefixes (i.e. render the same as the equivalent *). But for maps where the state of a building or other feature is more important, like rendering for HOT, some effort should be made to support lifecycle prefixes on as many types of objects as possible.</div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Tod</div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>