[Gdal-dev] RE: gdal_translate versus mrsiddecode
Chris G. Nicholas
cgn at globexplorer.com
Thu Jul 21 15:07:07 EDT 2005
One more tidbit...
--------------------------------------------------------------------
pogo-> mrsidinfo /data/f04/contentapu1/apu01_2ft_aus_2.sid
mrsidinfo: (c) 2004 LizardTech, Inc. All rights reserved.
basic image info:
format: MRSID
width: 188933
height: 47333
nband: 3
color space: RGB
datatype: uint8
precision: 8
dyn range min: (natural)
dyn range max: (natural)
background color: (0, 0, 0)
nodata color: (255, 255, 255)
metadata records: 20
geo coordinate info:
X UL: 2.9673e+06
Y UL: 1.01493e+07
X res: 1.5
Y res: -1.5
X rot: 0
Y rot: 0
geo points (pixel centers):
upper left: (2967300.750000, 10149299.250000)
upper right: (3250698.750000, 10149299.250000)
lower left: (2967300.750000, 10078301.250000)
lower right: (3250698.750000, 10078301.250000)
center: (3108999.750000, 10113800.250000)
MrSID image info:
number of levels: 8
is locked: false
file version: 1.0.1.
MrSID/MG2-specific image info:
is dithered: false
pogo->
-----Original Message-----
From: Chris G. Nicholas
Sent: Thu 7/21/2005 12:05 PM
To: gdal-dev at lists.maptools.org
Cc:
Subject: gdal_translate versus mrsiddecode
Just checked out the latest/greatest CVS snapshot, as well as the same for MrSid DSDK, and not sure why, but mrsiddecode is *_way_* faster for some simple cases; I'm just trying to make thumbnails of some monster images we have sitting around, and doing some simple non-geographic extracts.
Something like:
gdal_translate -of jpeg -outsize 500 500 /data/f04/contentapu1/apu01_2ft_aus_2.sid /tmp/foo.jpg
Input file size is 188933, 47333
goes out to lunch for several minutes. mrsiddecode does the equivalent in under a second.
Am I doing something wrong?
thanks in advance!
Chris
More information about the Gdal-dev
mailing list