No subject
Wed Jul 15 09:27:57 PDT 2009
eat a set of tiles making up a larger coverage as one.
Would you agree to that?
-Peter
On 07/27/2010 05:52 PM, Pierre Racine wrote:
BTW Peter,
in your site (http://kahlua.eecs.jacobs-university.de/trac/rasdaman/wiki/Wh=
yRasdaman) you say: "First and foremost, it (PostGIS WKT Raster) does not s=
upport tiling (partitioning) of raster arrays." This statement is false sin=
ce WKT Raster actually does support tiling of large rasters. You can partit=
ion any raster coverage by importing it as separate tiles or by using the -=
k option of gdal2wktraster.py. Each tile become a separate row in the table=
and the whole table is the coverage. The table is spatially indexed using =
the PostgreSQL GiST index.
I think it would be just fair if you could rectify this statement.
Thanks,
Pierre
From: Peter Baumann [mailto:p.baumann at jacobs-university.de]
Sent: 21 juillet 2010 17:28
To: Pierre Racine
Cc: PostGIS Users Discussion
Subject: Re: [postgis-users] WKTRaster : gdal2wktraster.py cannot read AIG/=
Arc/Info Binary Grid
Pierre-
rasdaman per se is domain agnostic - you can just as well maintain human br=
ain images (as we did). The petascope layer, which is part of the distro, a=
dds geo semantics by providing OGC interfaces.
PostgreSQL integration is not yet done, we are working on this; same for GD=
AL / MapServer.
-Peter
On 07/21/2010 08:29 PM, Pierre Racine wrote:
Peter,
Are rasters in rasdaman georeferenced? How do I convert my vectorial PostGI=
S points coordinates into rasdaman coordinates? Do I have to do all the mat=
h myself?
Pierre
From: Peter Baumann [mailto:p.baumann at jacobs-university.de]
Sent: 21 juillet 2010 04:41
To: Pierre Racine
Subject: Re: [postgis-users] WKTRaster : gdal2wktraster.py cannot read AIG/=
Arc/Info Binary Grid
Pierre-
let's see. First, I would not store 100k raster points in the relational ta=
ble as its terribly inefficient. We do have input data formats, though, whi=
ch are similar to what a PG dump of such a table would deliver. We import t=
his into an array and then can query it. Import via rasql or through an imp=
ort tool which internally generates rasql calls.
Then, for corner points (x0,y0) and (x1,y1) we retrieve as
select png( M[x0:y1,y0:y1] ) from MyMap as M
...in PNG format via the rasql cmd line utility or the C++ or Java API.
Alternatively, sending this this query over the API gets you the data into =
main memory ready for nested for loops =3D in the main memory format of you=
r client:
select M[x0:y1,y0:y1] from MyMap as M
-Peter
On 07/20/2010 10:03 PM, Pierre Racine wrote:
So if I already have a table of, say 100 000 points, uploaded in PostGIS, =
how do I use rasdaman to get the raster values of the pixels located under =
the points?
Pierre
From: Peter Baumann [mailto:p.baumann at jacobs-university.de]
Sent: 20 juillet 2010 12:08
To: PostGIS Users Discussion
Cc: Pierre Racine
Subject: Re: [postgis-users] WKTRaster : gdal2wktraster.py cannot read AIG/=
Arc/Info Binary Grid
On 07/20/2010 05:47 PM, Pierre Racine wrote:
Since we have this bug with big rasters,
proven, any-size, ... ;-)
Who is proven? Well, running a dozen-TB seamless mosaic on PostgreSQL for m=
any years, having online-demos available since years, etc... you decide, in=
comparison.
-Peter
I would suggest you split your raster with something like GDAL gdal_retile.=
py and then import your tiles into a single WKT Raster table following the =
instruction provided in our tutorial. Each tile will be stored in a column =
cell of type RASTER similar to the PostGIS GEOMETRY type.
As I said previously you can then query the raster in SQL like this:
SELECT ST_Value(rast, ST_Geomfromtext('Point(-78.1 58.1)', 4326))
FROM srtm_tiled_100x100
WHERE ST_Intersects(rast::geometry, ST_Geomfromtext('Point(-78.1 58.1)', 43=
26)) AND whatever you want.
Basically WKT Raster is the first true SQL interface with which is is simpl=
e to do such things... It's proven, any-size, cloud-scalable, and open sour=
ce :) Maybe not that prooven. But who is?
There is also rasdaman but I don't think you can use SQL. It would be nice =
if you could compare both... I can't find time for this. Jorge has started =
comparing PostGIS WKT Raster with Oracle Georaster though.
Pierre
From: postgis-users-bounces at postgis.refractions.net<mailto:postgis-users-bo=
unces at postgis.refractions.net> [mailto:postgis-users-bounces at postgis.refrac=
tions.net] On Behalf Of Sebastian E. Ovide
Sent: 20 juillet 2010 10:46
To: PostGIS Users Discussion
Subject: Re: [postgis-users] WKTRaster : gdal2wktraster.py cannot read AIG/=
Arc/Info Binary Grid
yes... with png worked... but it was a different png (a smaller one)...
so I've converted the ESRI into a png and tried to import it... and it didn=
't work neither...
so this is the situation:
A have huge rusters (from 150kx150k).. In Oracle I would just load it (the =
huge raster) in a single row of a GeoRaster table and then Oracle GeoRaster=
would split it in small tiles and store one tile per line of another table=
(Raster Data Table)... then I can run a query similar to this one: SELECT =
getcellvalue(t.rastercolumn,x,y) from GeoRasterTable t where t.id<http://t.=
id>=3D1; and GeoRaster will query automatically the spatial indexes and the=
Raster Data Table and it will find the right tile etc...
I do not know how WKTRaster works.... If I cannot import a such big image, =
of course I can split it in smaller georeferenced tiles... (how?)... but...=
. My main question is: after that, how will the table look like ? how can I=
do the same query (where id=3D1 or where name=3D"UK" etc...) ?
On Tue, Jul 20, 2010 at 2:31 PM, Pierre Racine <Pierre.Racine at sbf.ulaval.ca=
<mailto:Pierre.Racine at sbf.ulaval.ca>> wrote:
Wait. You first said the png was working. Now it's not? Did you try gdal_tr=
anslate with the ESRI grid? For sure I haven't test yet with such big raste=
rs. Is this the result of a merge or all your original raster are all this =
size? The point is that with WKT Raster you don't have to merge your raster=
first into a gigantic raster in order to get it store in a unique table li=
ke with Oracle Spatial.
Pierre
From: postgis-users-bounces at postgis.refractions.net<mailto:postgis-users-bo=
unces at postgis.refractions.net> [mailto:postgis-users-bounces at postgis.refrac=
tions.net<mailto:postgis-users-bounces at postgis.refractions.net>] On Behalf =
Of Sebastian E. Ovide
Sent: 20 juillet 2010 05:51
To: PostGIS Users Discussion
Subject: Re: [postgis-users] WKTRaster : gdal2wktraster.py cannot read AIG/=
Arc/Info Binary Grid
Hi Pierre,
Does gdal2wktraster.py have any limitation on the maximum number of columns=
xrows ?
in my case, my raster is 107759 x 168633...
gdal works well:
sebas at SeansPC:~/rasters$ gdal_translate -of PNG raster/ test.png
Input file size is 107759, 168633
0...10...20...30...40...50...60...70...80...90...100 - done.
sebas at SeansPC:~/rasters$ python gdal2wktraster.py -r raster/ -t sebastable =
-o ok.sql
gdal2wktraster.py:695: DeprecationWarning: 'H' format requires 0 <=3D numbe=
r <=3D 65535
hexwkb +=3D wkblify('H', xsize)
gdal2wktraster.py:696: DeprecationWarning: 'H' format requires 0 <=3D numbe=
r <=3D 65535
hexwkb +=3D wkblify('H', ysize)
gdal2wktraster.py:727: DeprecationWarning: integer argument expected, got f=
loat
hexwkb +=3D wkblify(pt2fmt(pixtype), nodata)
Traceback (most recent call last):
File "gdal2wktraster.py", line 1013, in <module>
main()
File "gdal2wktraster.py", line 976, in main
wkblify_raster(opts, filename, i)
File "gdal2wktraster.py", line 921, in wkblify_raster
summary =3D wkblify_raster_level(options, ds, options.overview_level, b=
and_range, infile, i)
File "gdal2wktraster.py", line 888, in wkblify_raster_level
hexwkb +=3D wkblify_band(options, band, level, xoff, yoff, read_block_s=
ize, block_size, infile, b)
File "gdal2wktraster.py", line 777, in wkblify_band
target_block_size[0], target_block_size[1])
File "/usr/lib/python2.6/dist-packages/osgeo/gdal.py", line 895, in ReadA=
sArray
buf_xsize, buf_ysize, buf_obj )
File "/usr/lib/python2.6/dist-packages/osgeo/gdal_array.py", line 228, in=
BandReadAsArray
ar =3D numpy.empty([buf_ysize,buf_xsize], dtype =3D typecode)
MemoryError
sebas at SeansPC:~/rasters$ python gdal2wktraster.py -r test.png -t sebastabl=
e -o ok.sql
gdal2wktraster.py:695: DeprecationWarning: 'H' format requires 0 <=3D numbe=
r <=3D 65535
hexwkb +=3D wkblify('H', xsize)
gdal2wktraster.py:696: DeprecationWarning: 'H' format requires 0 <=3D numbe=
r <=3D 65535
hexwkb +=3D wkblify('H', ysize)
gdal2wktraster.py:727: DeprecationWarning: integer argument expected, got f=
loat
hexwkb +=3D wkblify(pt2fmt(pixtype), nodata)
Traceback (most recent call last):
File "gdal2wktraster.py", line 1013, in <module>
main()
File "gdal2wktraster.py", line 976, in main
wkblify_raster(opts, filename, i)
File "gdal2wktraster.py", line 921, in wkblify_raster
summary =3D wkblify_raster_level(options, ds, options.overview_level, b=
and_range, infile, i)
File "gdal2wktraster.py", line 888, in wkblify_raster_level
hexwkb +=3D wkblify_band(options, band, level, xoff, yoff, read_block_s=
ize, block_size, infile, b)
File "gdal2wktraster.py", line 777, in wkblify_band
target_block_size[0], target_block_size[1])
File "/usr/lib/python2.6/dist-packages/osgeo/gdal.py", line 895, in ReadA=
sArray
buf_xsize, buf_ysize, buf_obj )
File "/usr/lib/python2.6/dist-packages/osgeo/gdal_array.py", line 228, in=
BandReadAsArray
ar =3D numpy.empty([buf_ysize,buf_xsize], dtype =3D typecode)
MemoryError
On Mon, Jul 19, 2010 at 5:56 PM, Pierre Racine <Pierre.Racine at sbf.ulaval.ca=
<mailto:Pierre.Racine at sbf.ulaval.ca>> wrote:
Hi Sebastian,
I can convert ESRI Grid file to .sql without problem using gdal2wktraster.p=
y and the same parameters as you. I can do both integer and floating point =
rasters.
Maybe this is a GDAL problem. Try to convert it using gdal_translate (to ti=
ff for example). This would be a better test than just gdalinfo.
Could you provide us with a file sample?
Pierre
From: postgis-users-bounces at postgis.refractions.net<mailto:postgis-users-bo=
unces at postgis.refractions.net> [mailto:postgis-users-bounces at postgis.refrac=
tions.net<mailto:postgis-users-bounces at postgis.refractions.net>] On Behalf =
Of Sebastian E. Ovide
Sent: 19 juillet 2010 12:28
To: PostGIS Users Discussion
Subject: [postgis-users] WKTRaster : gdal2wktraster.py cannot read AIG/Arc/=
Info Binary Grid
Hi All,
trying to create a SQL with gdal2wktraster.py. It works on PNG but it doesn=
't on AIG files...
Note: As Gdal works fine.
C:\Program Files\PostgreSQL\8.4\bin>gdalinfo c:\tmp\raster
Driver: AIG/Arc/Info Binary Grid
Files: c:\tmp\raster
c:\tmp\raster\dblbnd.adf
c:\tmp\raster\hdr.adf
c:\tmp\raster\metadata.xml
c:\tmp\raster\prj.adf
c:\tmp\raster\sta.adf
c:\tmp\raster\vat.adf
c:\tmp\raster\w001000.adf
c:\tmp\raster\w001000x.adf
c:\tmp\raster\w001001.adf
c:\tmp\raster\w001001x.adf
c:\tmp\raster\z001001.adf
c:\tmp\raster\z001001x.adf
c:\tmp\raster\z001002.adf
c:\tmp\raster\z001002x.adf
c:\tmp\raster\z001003.adf
c:\tmp\raster\z001003x.adf
c:\tmp\raster\z001004.adf
c:\tmp\raster\z001004x.adf
c:\tmp\raster\z001005.adf
c:\tmp\raster\z001005x.adf
c:\tmp\raster\z001006.adf
c:\tmp\raster\z001006x.adf
c:\tmp\raster\z001007.adf
c:\tmp\raster\z001007x.adf
c:\tmp\raster\z001008.adf
c:\tmp\raster\z001008x.adf
c:\tmp\raster\z001009.adf
c:\tmp\raster\z001009x.adf
c:\tmp\raster\z001010.adf
c:\tmp\raster\z001010x.adf
c:\tmp\raster\z001011.adf
c:\tmp\raster\z001011x.adf
c:\tmp\raster\z001012.adf
c:\tmp\raster\z001012x.adf
c:\tmp\raster\z001013.adf
c:\tmp\raster\z001013x.adf
c:\tmp\raster\z001014.adf
c:\tmp\raster\z001014x.adf
c:\tmp\raster\z001015.adf
c:\tmp\raster\z001015x.adf
Size is 107759, 168633
Coordinate System is:
PROJCS["unnamed",
GEOGCS["Unknown datum based upon the Airy 1830 ellipsoid",
DATUM["Not_specified_based_on_Airy_1830_ellipsoid",
SPHEROID["Airy 1830",6377563.396,299.3249646,
AUTHORITY["EPSG","7001"]],
AUTHORITY["EPSG","6001"]],
PRIMEM["Greenwich",0,
AUTHORITY["EPSG","8901"]],
UNIT["degree",0.01745329251994328,
AUTHORITY["EPSG","9122"]],
AUTHORITY["EPSG","4001"]],
PROJECTION["Transverse_Mercator"],
PARAMETER["latitude_of_origin",49],
PARAMETER["central_meridian",-2],
PARAMETER["scale_factor",0.9996012717],
PARAMETER["false_easting",400000],
PARAMETER["false_northing",-100000],
UNIT["METERS",1]]
Origin =3D (128110.000000000000000,813270.000000000000000)
Pixel Size =3D (5.000000000000000,-5.000000000000000)
Corner Coordinates:
Upper Left ( 128110.000, 813270.000) ( 6d29'37.32"W, 57d 7'47.53"N)
Lower Left ( 128110.000, -29895.000) ( 5d45'40.00"W, 49d34'10.24"N)
Upper Right ( 666905.000, 813270.000) ( 2d24'41.72"E, 57d 7'58.04"N)
Lower Right ( 666905.000, -29895.000) ( 1d41'32.29"E, 49d34'18.23"N)
Center ( 397507.500, 391687.500) ( 2d 2'15.04"W, 53d25'18.19"N)
Band 1 Block=3D256x4 Type=3DByte, ColorInterp=3DUndefined
Min=3D1.000 Max=3D4.000
NoData Value=3D255
C:\Program Files\PostgreSQL\8.4\bin>python gdal2wktraster.py -r c:\tmp\rast=
er -t sebastable -o c:\tmp\sebas.sql
gdal2wktraster.py:644: DeprecationWarning: 'H' format requires 0 <=3D numbe=
r <=3D 65535
hexstr =3D binascii.hexlify(struct.pack(fmt_little, data)).upper()
gdal2wktraster.py:644: DeprecationWarning: integer argument expected, got f=
loat
hexstr =3D binascii.hexlify(struct.pack(fmt_little, data)).upper()
ERROR 2: Multiplication overflow : 107759 * 168633 * 1
Traceback (most recent call last):
File "gdal2wktraster.py", line 1013, in <module>
main()
File "gdal2wktraster.py", line 976, in main
wkblify_raster(opts, filename, i)
File "gdal2wktraster.py", line 921, in wkblify_raster
summary =3D wkblify_raster_level(options, ds, options.overview_level, b=
and_range, infile, i)
File "gdal2wktraster.py", line 888, in wkblify_raster_level
hexwkb +=3D wkblify_band(options, band, level, xoff, yoff, read_block_s=
ize, block_size, infile, b)
File "gdal2wktraster.py", line 777, in wkblify_band
target_block_size[0], target_block_size[1])
File "C:\OSGeo4W\apps\gdal-16\pymod\osgeo\gdal.py", line 835, in ReadAsAr=
ray
buf_xsize, buf_ysize, buf_obj )
File "C:\OSGeo4W\apps\gdal-16\pymod\osgeo\gdal_array.py", line 140, in Ba=
ndReadAsArray
ar =3D numpy.reshape(ar, [buf_ysize,buf_xsize])
File "C:\OSGeo4W\apps\Python25\lib\site-packages\numpy\core\fromnumeric.p=
y", line 116, in reshape
return reshape(newshape, order=3Dorder)
ValueError: total size of new array must be unchanged
Any ideas ?
--
Sebastian E. Ovide
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net<mailto:postgis-users at postgis.refracti=
ons.net>
http://postgis.refractions.net/mailman/listinfo/postgis-users
--
Sebastian E. Ovide
skype: sebastian.ovide
+353 (0) 87 6340149
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net<mailto:postgis-users at postgis.refracti=
ons.net>
http://postgis.refractions.net/mailman/listinfo/postgis-users
--
Sebastian E. Ovide
--
Dr. Peter Baumann
- Professor of Computer Science, Jacobs University Bremen
www.faculty.jacobs-university.de/pbaumann<http://www.faculty.jacobs-univ=
ersity.de/pbaumann>
mail: p.baumann at jacobs-university.de<mailto:p.baumann at jacobs-university.=
de>
tel: +49-421-200-3178, fax: +49-421-200-493178
- Executive Director, rasdaman GmbH Bremen (HRB 147737)
www.rasdaman.com<http://www.rasdaman.com>, mail: baumann at rasdaman.com<ma=
ilto:baumann at rasdaman.com>
tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
"Si forte in alienas manus oberraverit hec peregrina epistola incertis vent=
is dimissa, sed Deo commendata, precamur ut ei reddatur cui soli destinata,=
nec preripiat quisquam non sibi parata." (mail disclaimer, AD 10xx)
--
Dr. Peter Baumann
- Professor of Computer Science, Jacobs University Bremen
www.faculty.jacobs-university.de/pbaumann<http://www.faculty.jacobs-univ=
ersity.de/pbaumann>
mail: p.baumann at jacobs-university.de<mailto:p.baumann at jacobs-university.=
de>
tel: +49-421-200-3178, fax: +49-421-200-493178
- Executive Director, rasdaman GmbH Bremen (HRB 147737)
www.rasdaman.com<http://www.rasdaman.com>, mail: baumann at rasdaman.com<ma=
ilto:baumann at rasdaman.com>
tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
"Si forte in alienas manus oberraverit hec peregrina epistola incertis vent=
is dimissa, sed Deo commendata, precamur ut ei reddatur cui soli destinata,=
nec preripiat quisquam non sibi parata." (mail disclaimer, AD 10xx)
--
Dr. Peter Baumann
- Professor of Computer Science, Jacobs University Bremen
www.faculty.jacobs-university.de/pbaumann<http://www.faculty.jacobs-univ=
ersity.de/pbaumann>
mail: p.baumann at jacobs-university.de<mailto:p.baumann at jacobs-university.=
de>
tel: +49-421-200-3178, fax: +49-421-200-493178
- Executive Director, rasdaman GmbH Bremen (HRB 147737)
www.rasdaman.com<http://www.rasdaman.com>, mail: baumann at rasdaman.com<ma=
ilto:baumann at rasdaman.com>
tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
"Si forte in alienas manus oberraverit hec peregrina epistola incertis vent=
is dimissa, sed Deo commendata, precamur ut ei reddatur cui soli destinata,=
nec preripiat quisquam non sibi parata." (mail disclaimer, AD 10xx)
--
Dr. Peter Baumann
- Professor of Computer Science, Jacobs University Bremen
www.faculty.jacobs-university.de/pbaumann<http://www.faculty.jacobs-univ=
ersity.de/pbaumann>
mail: p.baumann at jacobs-university.de<mailto:p.baumann at jacobs-university.=
de>
tel: +49-421-200-3178, fax: +49-421-200-493178
- Executive Director, rasdaman GmbH Bremen (HRB 147737)
www.rasdaman.com<http://www.rasdaman.com>, mail: baumann at rasdaman.com<ma=
ilto:baumann at rasdaman.com>
tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
"Si forte in alienas manus oberraverit hec peregrina epistola incertis vent=
is dimissa, sed Deo commendata, precamur ut ei reddatur cui soli destinata,=
nec preripiat quisquam non sibi parata." (mail disclaimer, AD 10xx)
--_000_87A96661E65C5541AB4D20721C2DD7F880A3C48D08EXCHMBXAulava_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3Dwhite lang=3DEN-US link=3Dblue vlink=3Dpurple>
<div class=3DWordSection1>
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>A table of tiles form a large coverage as one. Every process
might be done one tile at a time but SQL GROUP BY statements help regroupin=
g
things together if needed.<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Pierre<o:p></o:p></span></p>
<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'>
<div>
<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'>
<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif";
color:windowtext'>From:</span></b><span style=3D'font-size:10.0pt;font-fami=
ly:
"Tahoma","sans-serif";color:windowtext'> Peter Baumann
[mailto:p.baumann at jacobs-university.de] <br>
<b>Sent:</b> 28 juillet 2010 04:27<br>
<b>To:</b> Pierre Racine<br>
<b>Cc:</b> PostGIS Users Discussion<br>
<b>Subject:</b> Re: [postgis-users] WKTRaster : gdal2wktraster.py cannot re=
ad
AIG/Arc/Info Binary Grid<o:p></o:p></span></p>
</div>
</div>
<p class=3DMsoNormal><o:p> </o:p></p>
<p class=3DMsoNormal>Pierre,<br>
<br>
admittedly this was a little inexact, and I certainly will correct it. A mo=
re
accurate phrasing I guess is "does not support retrieval on a raster a=
rray
consisting of a set of tiles, rather tiles have to be treated
individually."<br>