[Live-demo] "big" data sets on OSGeo Live

Angelos Tzotsos gcpp.kalxas at gmail.com
Thu Jan 10 13:53:09 PST 2013


Another thing that was brought up was the possibility to use 8GB USB 
drives for FOSS4G, which would mean that the mini iso could go up to 
4.4G to fit on the DVD and the full iso (with the installers) would fit 
on the USB drive.
Can this extra cost be covered somehow?
Thoughts?

On 01/10/2013 11:47 PM, Angelos Tzotsos wrote:
> Hi Peter and thanks for bringing this topic here.
>
> 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.
> 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.
>
> 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.
>
> About projects mentioned:
> MapGuide is actually not included in the disk due to that large 
> footprint (caused by mono dependency).
> Marble in large because its dependencies for Qt bring in large parts 
> of the KDE libraries.
>
> We definitely need to hear more from the projects on this!
>
> Best,
> Angelos
>
>> Hi listers,
>>
>> 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
>> https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGIzd0VLLTBpQVJuNVlHMlBWSDhKLXc#gid=13 
>>
>>
>> Top riders currently:
>> - mapguide: 550mb
>> - marble: 300 mb (includes disk caching!)
>> - grass >250mb
>>
>> 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.
>>
>> Can I ask all those with 3-digit disk hunger to chime into this 
>> discussion.
>>
>> thanks,
>> Peter 
>
>


-- 
Angelos Tzotsos
Remote Sensing Laboratory
National Technical University of Athens
http://users.ntua.gr/tzotsos



More information about the Live-demo mailing list