<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">Agreed!<br><br>"start_date" and "end_date" are best. Suppose for Burning Man, I can just go ahead and use these tags, and whatever bad result comes out can be used as motivation for the main rendering systems to tweak their processing (ie add an osmosis step) to deal with this. Or with updated stylesheets. Whatever works best for the renderers.<br><br>That may result in overlapping Burning Man maps .. that could be ok for OSM itself. For Burning Man, and possibly for Flickr, I've set up another rendering system.<br><br>-Mikel<br><br><br><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Andy Robinson
(blackadder-lists) <ajrlists@googlemail.com><br><b><span style="font-weight: bold;">To:</span></b> Mikel Maron <mikel_maron@yahoo.com>; talk@openstreetmap.org<br><b><span style="font-weight: bold;">Sent:</span></b> Tuesday, August 18, 2009 4:43:23 AM<br><b><span style="font-weight: bold;">Subject:</span></b> RE: [OSM-talk] Historic Mapping needs help Now!<br></font><br>
here's my thoughts.<br><br>If object is no longer present we need some sort of "ghost" tagging, and the<br>ghost tag take precedent when rendering. This means that the data that was<br>present is still available, its useful data after all. Ideally there would<br>be a start_date and end_date tag also that defines the period when the<br>object was present.<br><br>Now for rendering we need an engine/style sheet that respects these tags.<br>Burning Man 08 doesn't require many tiles, so it's something Y! can probably<br>render and hard code? Quick and dirty maybe and wouldn't scale, but it would<br>be a start. <br><br>Cheers <br><br><br>>-----Original Message-----<br>>From: <a ymailto="mailto:talk-bounces@openstreetmap.org" href="mailto:talk-bounces@openstreetmap.org">talk-bounces@openstreetmap.org</a> [mailto:talk-<br>><a ymailto="mailto:bounces@openstreetmap.org" href="mailto:bounces@openstreetmap.org">bounces@openstreetmap.org</a>] On
Behalf Of Mikel Maron<br>>Sent: 17 August 2009 10:01 PM<br>>To: <a ymailto="mailto:talk@openstreetmap.org" href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a><br>>Subject: [OSM-talk] Historic Mapping needs help Now!<br>><br>>Hi<br>><br>>I'm again working this year on mapping for the Burning Man arts festival,<br>>coming up in two weeks.<br>>This makes urgent a growing theme in OSM, with several presentations at<br>>this year's SOTM .. how to handle historic data.<br>><br>>Here's the current map of Burning Man for 2009. I haven't added Camp<br>>locations yet, will come soon.<br><span>><a target="_blank" href="http://playaevents.burningman.com/brc/2009/map/">http://playaevents.burningman.com/brc/2009/map/</a></span><br>><br>>That map data hasn't been added to <a target="_blank" href="http://OSM.org">OSM.org</a> yet, because the prior year's<br>>map is still there, and still being used. For
example, Flickr...<br><span>><a target="_blank" href="http://radar.oreilly.com/2008/08/flickr-burning-man-open-street-map.html">http://radar.oreilly.com/2008/08/flickr-burning-man-open-street-map.html</a></span><br>><br>>Why is 2008 historic map data now? Well each year, the location of the<br>>festival moves, to minimize impact on the area. Everything is rebuilt,<br>>created again over several weeks, existing as a place for one week, and<br>>then deconstructed over several weeks. However, the impact of Burning Man<br>>is year round, and for years to come; the amount of media generated and<br>>geotagged during the event is enormous. Take a look at the photos in the<br>>Flickr map to understand why.<br>><br>><br>>So I'd like to import 2009 BM into OSM now. But there's a need to retain<br>>the 2008 data. I'm opening the question up... what is the best way to mark<br>>this data as historic, keep it available as
needed, but make sure it<br>>doesn't show up in core renderings?<br>><br>>Look forward to some good ideas.<br>><br>>Thanks<br>>Mikel<br><br><br></div></div></div></body></html>