<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">The once-and-for-all solution would be a full history DB schema from which vector tiles could be extracted for any point in time.<div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">Martijn van Exel</div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Jan 30, 2017, at 1:26 PM, Maarten Deen <<a href="mailto:mdeen@xs4all.nl" class="">mdeen@xs4all.nl</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 2017-01-30 12:07, Simon Poole wrote:<br class=""><blockquote type="cite" class="">I suspect the main problem is that in 2007 we didn't really have a lot<br class="">of data so rendering tiles or it is really not such a big issue.<br class="">However 2010 and later would require per point in time a rather<br class="">largish rendering DB plus space for tiles a model that neither scales<br class="">nor would seem to be a particular good use of resources.<br class=""></blockquote><br class="">You could mitigate that in the future by making a copy of the current tileset at a fixed point (1st of january for example).<br class=""><br class="">But I agree that it would need quite some space for a gimmick. But with Seagate announcing 16TB drives and prices of drives dropping steadily, I assume this argument will be laughed at in 5 years time.<br class=""><br class="">Regards,<br class="">Maarten<br class=""><br class=""><blockquote type="cite" class="">Am 30.01.2017 um 11:04 schrieb Martijn van Exel:<br class=""><blockquote type="cite" class="">My poor little tile server machine doesn’t have the storage for<br class="">that, but it would sure be cool to set this up for more points in<br class="">time. The server itself is not hard to get up and running, although<br class="">I did find the instructions on switch2osm to be out of date. I<br class="">followed the instructions here:<br class=""></blockquote><a href="https://www.linuxbabe.com/linux-server/openstreetmap-tile-server-ubuntu-16-04" class="">https://www.linuxbabe.com/linux-server/openstreetmap-tile-server-ubuntu-16-04</a>.<br class=""><blockquote type="cite" class="">The only extra step was to download osmosis 0.35 and convert the 0.5<br class="">planet to 0.6. For older planets you’d need to come up with a way<br class="">to convert 0.3 / 0.4 planets to 0.6. There is a script to convert<br class="">from 0.4 to 0.5 but I don’t know of anything that can handle 0.3<br class="">planets.<br class="">Martijn van Exel<br class="">On Jan 28, 2017, at 5:08 PM, joost schouppe<br class=""><<a href="mailto:joost.schouppe@gmail.com" class="">joost.schouppe@gmail.com</a>> wrote:<br class="">Any chance we'll see some middle version there too in the future?<br class="">(say, 2012. And than later, 1/1/20**)<br class="">You gave us a finger, let me grab your entire arm :)<br class="">2017-01-26 23:17 GMT+01:00 Martijn van Exel <<a href="mailto:m@rtijn.org" class="">m@rtijn.org</a>>:<br class="">Hi all,<br class="">I resuscitated the OSM then and now service, where you can compare<br class="">OSM as it was in October 2007 with now.<br class="">The service is a bit slow because 2007 tiles above z10 are not<br class="">pre-rendered. This will improve as tiles get cached.<br class="">Here is the location of SOTM 2016 as an example:<br class=""><a href="http://mvexel.github.io/thenandnow/#15/50.8178/4.3971" class="">http://mvexel.github.io/thenandnow/#15/50.8178/4.3971</a> [1]<br class="">Martijn van Exel<br class="">_______________________________________________<br class="">talk mailing list<br class=""><a href="mailto:talk@openstreetmap.org" class="">talk@openstreetmap.org</a><br class="">https://lists.openstreetmap.org/listinfo/talk [2]<br class="">--<br class="">Joost Schouppe<br class="">OpenStreetMap [3] | Twitter [4] | LinkedIn [5] | Meetup [6]<br class=""></blockquote>_______________________________________________<br class="">talk mailing list<br class=""><a href="mailto:talk@openstreetmap.org" class="">talk@openstreetmap.org</a><br class="">https://lists.openstreetmap.org/listinfo/talk<br class="">Links:<br class="">------<br class="">[1] http://mvexel.github.io/thenandnow/#15/50.8178/4.3971<br class="">[2] https://lists.openstreetmap.org/listinfo/talk<br class="">[3] http://www.openstreetmap.org/user/joost%20schouppe/<br class="">[4] https://twitter.com/joostjakob<br class="">[5] https://www.linkedin.com/pub/joost-schouppe/48/939/603<br class="">[6] http://www.meetup.com/OpenStreetMap-Belgium/members/97979802/<br class="">_______________________________________________<br class="">talk mailing list<br class="">talk@openstreetmap.org<br class="">https://lists.openstreetmap.org/listinfo/talk<br class=""></blockquote><br class="">_______________________________________________<br class="">talk mailing list<br class=""><a href="mailto:talk@openstreetmap.org" class="">talk@openstreetmap.org</a><br class="">https://lists.openstreetmap.org/listinfo/talk<br class=""></div></div></blockquote></div><br class=""></div></body></html>