charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"=
>
<TITLE>Message</TITLE>
<META content=3D"MSHTML 6.00.2719.2200" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D993270306-24092002><FONT face=3D"Verdana Ref" color=3D#0=
000ff=20
size=3D2>I would assume that the amongst the 30 to 40 file formats handled =
by GDAL=20
that some store the image data with pixel zero in the bottom-left corner an=
d=20
some store pixel zero at the top-left corner. Do RasterIO() and assoc=
iated=20
functions which give access to raster image pixels rationalize these=20
differences and always provide top-left pixel zero image to the client?&nbs=
p; Or=20
do client applications need to flip images vertically for some=20
formats?</FONT></SPAN></DIV>
<DIV><SPAN class=3D993270306-24092002><FONT face=3D"Verdana Ref" color=3D#0=
000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D993270306-24092002>
<DIV><SPAN class=3D993270306-24092002><FONT face=3D"Verdana Ref" color=3D#0=
000ff=20
size=3D2>Sorry if this is an excessively stupid=20
question...</FONT></SPAN></DIV></SPAN></DIV>
<DIV><SPAN class=3D993270306-24092002><FONT face=3D"Verdana Ref" color=3D#0=
000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D993270306-24092002><FONT face=3D"Verdana Ref" color=3D#0=
000ff=20
size=3D2>- Jay</FONT></SPAN></DIV></BODY></HTML>