The CPU power vs file space is noted, thanks...we ahev much more space than
power.  The actual sat photos will have to stay in tiff format for their
georeferencing and pixel (ie spectral) values, which are very important
characteristics.  But the thumbnails (100x100 px) can be in crayon for all I
care, as long as they show up in NS4.x and IE4.x.  The thumbs are simply
meant to be a guideline for the users so they can assess cloud cover,
locale, etc.  The real info is in the tif, which the user may download if
they choose.  

I will try the imagemagik as someone else mentioned for its usefulness.
With the archived images I can create thumbs and store them on the file
system, that's not too bad, but I really wanted the on-the-fly capability to
generate 100x100 px thumbs for the 4+ tif images we receive daily so someone
does not have to manually create them each time.

-Dave
----------------------------------------------------------------------------
-------------


TIFF supports every compression format known to man :) including LZW so you
might want to check that.

If they're actual sat photographs (not computer generated or
colour-enhanced) they're idea candidates for JPEG compression. And JPEG is
the highest compression format that browsers currently support (smallest
file size).

I'd strongly suggest saving the thumbs to the server as on-the-fly image
compression isn't trival as far as CPU power needed. It's a question of a
lot of CPU power or a lot of file space.

--min


----------------------------------------------------------------------------
--
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to