Agree... <br><br>by the way, the script finished in only 10 minutes and it has created a file of 35GB ! Still I cannot compare it with Oracle as I do not know yet how much space it will consume inside PG (in oracle it consumes around 16GB if not compressed and around 300M if compressed)<br>
<br>sebas@SeansPC:~/rasters$ ls -lh ok.sql<br>-rw-r--r-- 1 sebas sebas 35G 2010-07-22 17:52 ok.sql<br><br>running the sql with psql I'm getting only errors:<br><br>sebas@SeansPC:~/rasters$ time psql -d sebas -h 10.0.1.50 -U sebas -f ok.sql<br>
BEGIN<br>psql:ok.sql:2: NOTICE: CREATE TABLE will create implicit sequence "sebastable_rid_seq" for serial column "sebastable.rid"<br>psql:ok.sql:2: NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "sebastable_pkey" for table "sebastable"<br>
CREATE TABLE<br>psql:ok.sql:3: ERROR: Invalid SRID<br>CONTEXT: SQL statement "SELECT AddRasterColumn('', $1 , $2 , $3 , $4 , $5 , $6 , $7 , $8 , $9 , $10 , $11 , $12 , $13 )"<br>PL/pgSQL function "addrastercolumn" line 4 at SQL statement<br>
psql:ok.sql:4: ERROR: current transaction is aborted, commands ignored until end of transaction block<br>psql:ok.sql:5: ERROR: current transaction is aborted, commands ignored until end of transaction block<br>psql:ok.sql:6: ERROR: current transaction is aborted, commands ignored until end of transaction block<br>
psql:ok.sql:7: ERROR: current transaction is aborted, commands ignored until end of transaction block<br>psql:ok.sql:8: ERROR: current transaction is aborted, commands ignored until end of transaction block<br>psql:ok.sql:9: ERROR: current transaction is aborted, commands ignored until end of transaction block<br>
p<br><br>any ideas ?<br><br><div class="gmail_quote">On Thu, Jul 22, 2010 at 6:55 PM, Pierre Racine <span dir="ltr"><<a href="mailto:Pierre.Racine@sbf.ulaval.ca">Pierre.Racine@sbf.ulaval.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Well it's still a bug that the process fail without the -k option, but we can lower the priority. If we could have one of those rasters...<br>
<font color="#888888"><br>
Pierre<br>
</font><div class="im"><br>
>-----Original Message-----<br>
>From: <a href="mailto:postgis-users-bounces@postgis.refractions.net">postgis-users-bounces@postgis.refractions.net</a> [mailto:<a href="mailto:postgis-users-">postgis-users-</a><br>
</div><div class="im">><a href="mailto:bounces@postgis.refractions.net">bounces@postgis.refractions.net</a>] On Behalf Of Jorge Arévalo<br>
>Sent: 22 juillet 2010 12:56<br>
>To: PostGIS Users Discussion<br>
</div><div><div></div><div class="h5">>Subject: Re: [postgis-users] gdal2wktraster.py wildchar not working<br>
><br>
>On Thu, Jul 22, 2010 at 6:45 PM, Sebastian E. Ovide<br>
><<a href="mailto:sebastian.ovide@gmail.com">sebastian.ovide@gmail.com</a>> wrote:<br>
>> Hi Jorge,<br>
>><br>
>> running the same gdal2wktraster script with those options that have<br>
>> suggested have fixed the error...<br>
>><br>
>> i.e:<br>
>><br>
>> sebas@SeansPC:~/rasters$ time ./gdal2wktraster.py -k 512x512 -s 81989 -I -r<br>
>> raster/ -t sebastable -o ok.sql<br>
>> ./gdal2wktraster.py:727: DeprecationWarning: integer argument expected, got<br>
>> float<br>
>> hexwkb += wkblify(pt2fmt(pixtype), nodata)<br>
>><br>
>> that means that if the image is too big, "-k is mandatory" (probably it<br>
>> should be set with some default...)<br>
>><br>
>> I have to go now.. if it gives any error I'll let you know !<br>
>><br>
>> thanks<br>
>><br>
><br>
>Great. So, we only have to focus on the wildcard problem. Keep us<br>
>informed if you experiment more problems :-)<br>
><br>
>Best regards,<br>
>Jorge<br>
><br>
><br>
><br>
>> 2010/7/22 Jorge Arévalo <<a href="mailto:jorge.arevalo@deimos-space.com">jorge.arevalo@deimos-space.com</a>><br>
>>><br>
>>> Hi Sebastian,<br>
>>><br>
>>> On Wed, Jul 21, 2010 at 6:35 PM, Sebastian E. Ovide<br>
>>> <<a href="mailto:sebastian.ovide@gmail.com">sebastian.ovide@gmail.com</a>> wrote:<br>
>>> >> Also, normally you will also want to retile your smaller rasters with<br>
>>> >> the<br>
>>> >> -k option to tiles (something like 100x100 or 200x200), specify the<br>
>>> >> reference system with the -s option and create an index with the -I<br>
>>> >> option.<br>
>>> >> Did you read the tutorial?<br>
>>> >><br>
>>> >><br>
>>> ><br>
>>> > it should not matter for gdal2wktraster.py right ?<br>
>>> ><br>
>>><br>
>>> Could you please provide a link to download the big raster that caused<br>
>>> the first problem in Linux? We're trying to reproduce it, in the same<br>
>>> conditions. You should be able to deal with big rasters by splitting<br>
>>> them into small blocks by using -k option to specify the size of the<br>
>>> blocks, and -I option to create an index, without using any other tool<br>
>>> before.<br>
>>><br>
>>> About the wildcard problem, we're working on it too. Thanks for reporting<br>
>>> it.<br>
>>><br>
>>> Best regards,<br>
>>> Jorge<br>
>>><br>
>>> >><br>
>>> >> Pierre<br>
>>> >><br>
>>> >><br>
>>> >><br>
>>> >> From: <a href="mailto:postgis-users-bounces@postgis.refractions.net">postgis-users-bounces@postgis.refractions.net</a><br>
>>> >> [mailto:<a href="mailto:postgis-users-bounces@postgis.refractions.net">postgis-users-bounces@postgis.refractions.net</a>] On Behalf Of<br>
>>> >> Sebastian E. Ovide<br>
>>> >> Sent: 21 juillet 2010 04:15<br>
>>> >> To: PostGIS Users Discussion<br>
>>> >> Subject: [postgis-users] gdal2wktraster.py wildchar not working<br>
>>> >><br>
>>> >><br>
>>> >><br>
>>> >> Hi All,<br>
>>> >><br>
>>> >> as gdal2wktraster.py has a bug that prevents importing big rasters, I<br>
>>> >> have<br>
>>> >> split the raster using<br>
>>> >><br>
>>> >> gdal_retile.py -v -ps 10000 10000 -targetDir test test.png<br>
>>> >><br>
>>> >> I created a lot of tif files...<br>
>>> >><br>
>>> >> then I've tried to create a sql with this:<br>
>>> >><br>
>>> >> ./gdal2wktraster.py -r test/*.tif -t newtable -o newtable.sql<br>
>>> >><br>
>>> >> and gdal2wktraster.py read only 1 file:<br>
>>> >><br>
>>> >> sebas@SeansPC:~/rasters$ ./gdal2wktraster.py -r test/*.tif -t newtable<br>
>>> >> -o<br>
>>> >> newtable.sql<br>
>>> >> ------------------------------------------------------------<br>
>>> >> Summary of GDAL to WKT Raster processing:<br>
>>> >> ------------------------------------------------------------<br>
>>> >> Number of processed raster files: 1 (test/test_01_01.tif)<br>
>>> >> List of generated tables (number of tiles):<br>
>>> >> 1 newtable (1)<br>
>>> >><br>
>>> >><br>
>>> >> any other easy way to import big rasters ?<br>
>>> >><br>
>>> >><br>
>>> >><br>
>>> >> --<br>
>>> >> Sebastian E. Ovide<br>
>>> >><br>
>>> >><br>
>>> >><br>
>>> >> _______________________________________________<br>
>>> >> postgis-users mailing list<br>
>>> >> <a href="mailto:postgis-users@postgis.refractions.net">postgis-users@postgis.refractions.net</a><br>
>>> >> <a href="http://postgis.refractions.net/mailman/listinfo/postgis-users" target="_blank">http://postgis.refractions.net/mailman/listinfo/postgis-users</a><br>
>>> >><br>
>>> ><br>
>>> ><br>
>>> > --<br>
>>> > Sebastian E. Ovide<br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > _______________________________________________<br>
>>> > postgis-users mailing list<br>
>>> > <a href="mailto:postgis-users@postgis.refractions.net">postgis-users@postgis.refractions.net</a><br>
>>> > <a href="http://postgis.refractions.net/mailman/listinfo/postgis-users" target="_blank">http://postgis.refractions.net/mailman/listinfo/postgis-users</a><br>
>>> ><br>
>>> ><br>
>>> _______________________________________________<br>
>>> postgis-users mailing list<br>
>>> <a href="mailto:postgis-users@postgis.refractions.net">postgis-users@postgis.refractions.net</a><br>
>>> <a href="http://postgis.refractions.net/mailman/listinfo/postgis-users" target="_blank">http://postgis.refractions.net/mailman/listinfo/postgis-users</a><br>
>><br>
>><br>
>><br>
>> --<br>
>> Sebastian E. Ovide<br>
>><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> postgis-users mailing list<br>
>> <a href="mailto:postgis-users@postgis.refractions.net">postgis-users@postgis.refractions.net</a><br>
>> <a href="http://postgis.refractions.net/mailman/listinfo/postgis-users" target="_blank">http://postgis.refractions.net/mailman/listinfo/postgis-users</a><br>
>><br>
>><br>
>_______________________________________________<br>
>postgis-users mailing list<br>
><a href="mailto:postgis-users@postgis.refractions.net">postgis-users@postgis.refractions.net</a><br>
><a href="http://postgis.refractions.net/mailman/listinfo/postgis-users" target="_blank">http://postgis.refractions.net/mailman/listinfo/postgis-users</a><br>
_______________________________________________<br>
postgis-users mailing list<br>
<a href="mailto:postgis-users@postgis.refractions.net">postgis-users@postgis.refractions.net</a><br>
<a href="http://postgis.refractions.net/mailman/listinfo/postgis-users" target="_blank">http://postgis.refractions.net/mailman/listinfo/postgis-users</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Sebastian E. Ovide<br><br><br><br><br>