<html style="direction: ltr;">
<head>
<meta content="text/html; charset=windows-1255"
http-equiv="Content-Type">
<style type="text/css">body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
</head>
<body style="direction: ltr;"
bidimailui-detected-decoding-type="preferred-charset"
bgcolor="#FFFFFF" text="#000000">
On 01/10/2013 11:47 PM, Angelos Tzotsos wrote:
<blockquote cite="mid:50EF370D.9060900@gmail.com" type="cite">Hi
Peter and thanks for bringing this topic here.
<br>
<br>
It would be great to have more data space and perhaps we can save
some space if we track which projects use non common data-sets.
<br>
From the IRC discussion there was a thought to include a
hyperspectral dataset so that rasdaman, OTB, OSSIM, EOxServer and
GRASS to use in common. Any thoughts on that? Should we play safe
with free MODIS dataset or is there another suggestion? Would it
be ok if we limit this to ~50MB size or would we need more? I know
this is not enough for a good remote sensing dataset, but we are
short on disk space currently.
<br>
<br>
</blockquote>
<br>
We've all seen the strong growth of FOSS4G software in the last 5
years or so, and this will most likely continue in the years to
come. The popularity of the OSGeo Live platform will create ever
increasing pressure to add more and more applications. I think that
we'll have to face the prospect, sooner or later, of splitting into
two versions : a "Desktop" DVD and a "Server" DVD. With some clever
juggling of sample data, this can probably be put off for a while,
but eventually 4GB (or 4.4 on a DVD) just won't be enough. <br>
<br>
My 0.02 €,<br>
Micha<br>
<br>
<blockquote cite="mid:50EF370D.9060900@gmail.com" type="cite">I
liked the idea of using some web services for demo purposes in
addition to data included in the disk as long as there is a notice
to the user that those are available only with internet
connection.
<br>
<br>
About projects mentioned:
<br>
MapGuide is actually not included in the disk due to that large
footprint (caused by mono dependency).
<br>
Marble in large because its dependencies for Qt bring in large
parts of the KDE libraries.
<br>
<br>
We definitely need to hear more from the projects on this!
<br>
<br>
Best,
<br>
Angelos
<br>
<br>
<blockquote type="cite">Hi listers,
<br>
<br>
as space is running short on the ISO we need to reconsider
sizings. In today's OSGel Live chat I was tasked to initiate
this discussion. Current disk footprint of each application is
available from
<br>
<a class="moz-txt-link-freetext" href="https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13">https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13</a>
<br>
<br>
Top riders currently:
<br>
- mapguide: 550mb
<br>
- marble: 300 mb (includes disk caching!)
<br>
- grass >250mb
<br>
<br>
One way of saving space is to enlarge it (ie, go to 8 GB) which
is unclear due to some unresolved questions; another one is to
deflate unused datasets, a third one to share data among
applications.
<br>
<br>
Can I ask all those with 3-digit disk hunger to chime into this
discussion.
<br>
<br>
thanks,
<br>
Peter </blockquote>
<br>
<br>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Micha Silver
GIS Consultant, Arava Development Co.
<a class="moz-txt-link-freetext" href="http://www.surfaces.co.il">http://www.surfaces.co.il</a></pre>
</body>
</html>