|
|
hi,
=?UTF-8?Q?J=c3=b6rg_=22Yadgar=22_Bleimann?= <yaz### [at] gmxde> wrote:
> ...
> >> This probably would not be possible, as 2 TB additional webspace is at
> >> the upper limit I can afford - and the original files come as *.zip from
> >> the NASA server...
> ...
> I tried xz... but my mesh2 inc files are still about 80 MB after
> compressing - so I will still need some 700 GB of webspace make them
> available for download. I recently did some research in webspace prices
> - and found out that 2 TB would be MUCH too expensive for me, as they
> usually are around 500 US$/year... the largest webspace offer I could
> afford is 500 GB for 36 euros/year, and that probably would be not
> enough for all 8000+ tiles processed into compressed mesh2 inc files.
on the source (zip) files -- you wrote a 3601x3601 tile needs ~1.5G. that is
~115 bytes per pixel; likely, some/much of that information will not be
required. suggest recoding those, to a custom file format.
on the mesh2 storage -- what if meshes were only created on-the-fly[*], when
needed for rendering that part of povearth? sure, performance hits everywhere,
but within budget.
another "budgeting" option would be to focus on a single continent, initially,
and only produce those meshes. (maybe, when you retire, your pension will allow
you to buy more cloud-storage. :-))
[*] ini file 'Pre_{Frame,Scene}_Command'.
regards, jr.
Post a reply to this message
|
|