<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 22 jul 2010, at 06:57, Brett Henderson wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Wed, Jul 21, 2010 at 11:52 PM, Lars Francke <span dir="ltr"><<a href="mailto:lars.francke@gmail.com">lars.francke@gmail.com</a>></span> wrote:<br><div>[...]<br>That format is fine and exactly what I would have expected. I suspect Osmosis would parse it okay, but without support for the visible attribute it won't be particularly useful.<br> </div></div></blockquote><div>Not for visualization purposes maybe, but for analysis purposes the visible attribute is not really an issue. My goal is to extract full history dumps for certain spatial extents and import them into a PostGIS, in order to calculate historical metrics exposing the crowd dynamics of OSM - for example number of contributors over time, version growth over time, movement of nodes over time. All this calculated for grid cells. </div><div><br></div><div>The full history dump is 13GB bz2 compressed. Anyone got a rough idea how long it would take for osmosis to extract, say, a bbox of the Netherlands out of that on a 4GB AMD Opteron quad core machine? More RAM would probaby help?</div><div><br></div><div>Best</div><div><br></div><div>-- Martijn</div><div><br></div></div></body></html>