<div dir="ltr">Hi Rainer,<div><br></div><div>Tried that, and got the same result. <div><br></div><div># SELECT PostGIS_Extensions_Upgrade();<br>NOTICE: Updating extension postgis 3.4.2<br>NOTICE: Updating extension postgis_raster 3.4.2<br> postgis_extensions_upgrade <br>------------------------------------------------------------------------------------<br> Upgrade to version 3.4.2 completed, run SELECT postgis_full_version(); for details<br>(1 row)<br></div></div><div><br></div><div>Andreas</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, Dec 19, 2024 at 6:27 PM Rainer Hurling <<a href="mailto:rhurlin@gwdg.de">rhurlin@gwdg.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Am 19.12.2024 um 10:09 schrieb Andreas B:<br>
> I checked the extent of the tiles, and 'NHS-D0309_50M_E25833.tif' has a different extent that is incompatible with the other tiles.<br>
> All the other tifs are lined up with coordinates ending in 00, 25, 50 and 75; 'NHS-D0309_50M_E25833.tif' does not.<br>
> <br>
> This explains the not aligned-stuff, and if I remove that tile, no misalignment notices are given.<br>
> This does not solve my problem regarding the data looking strange in QGIS, unfortunately. I still get an image like the one in merge_raster2pgsql.png.<br>
> <br>
> I also tried with a (more) recent version of PostgreSQL/PostGIS and raster2pgsql, but the issue is still there:<br>
> <br>
> # SELECT version();<br>
> PostgreSQL 16.3 [..]<br>
> <br>
> # SELECT PostGIS_full_version();<br>
> POSTGIS="3.4.2 POSTGIS_REVISION" [EXTENSION] (liblwgeom version mismatch: "3.4.2 c19ce56") PGSQL="160" GEOS="3.13.0-CAPI-1.19.0" (compiled against GEOS 3.12.2) PROJ="9.5.1<br>
> NETWORK_ENABLED=OFF URL_ENDPOINT=<a href="https://cdn.proj.org" rel="noreferrer" target="_blank">https://cdn.proj.org</a> <<a href="https://cdn.proj.org/" rel="noreferrer" target="_blank">https://cdn.proj.org/</a>> USER_WRITABLE_DIRECTORY=/var/lib/postgres/.local/share/proj DATABASE_PATH=/usr/share/proj/proj.db" GDAL="GDAL 3.10.0, r<br>
> eleased 2024/11/01" LIBXML="2.13.5" LIBJSON="0.18" LIBPROTOBUF="1.5.0" WAGYU="0.5.0 (Internal)" (core procs from "3.4.2 c19ce56" need upgrade) RASTER (raster procs from "3.4<br>
> .2 c19ce56" need upgrade)<br>
<br>
Maybe that I missed something here. But did you try<br>
<br>
SELECT PostGIS_Extensions_Upgrade();<br>
<br>
before using the database with your new combo of PostgreSQL/PostGIS and raster2pgsql?<br>
<br>
HTH,<br>
Rainer<br>
<br>
> $ raster2pgsql<br>
> RELEASE: 3.4.2 GDAL_VERSION=310 (POSTGIS_REVISION)<br>
> <br>
> Another observation is that the choice of tile size varies (I'm using -t auto):<br>
> <br>
> With vrt as input, always uses 128x128:<br>
> <br>
> INFO: Using computed tile size: 128x128<br>
> <br>
> With *.tif as input the tile size varies depending on which tile is processed first, e.g.:<br>
> <br>
> INFO: Using computed tile size: 215x274<br>
> <br>
> or<br>
> <br>
> INFO: Using computed tile size: 97x46<br>
> <br>
> or<br>
> <br>
> INFO: Using computed tile size: 18x10<br>
> <br>
> Just testing and thinking out loud!<br>
> <br>
> Best,<br>
> Andreas<br>
> <br>
> <br>
> On Sun, Dec 15, 2024 at 12:35 AM Regina Obe <<a href="mailto:lr@pcorp.us" target="_blank">lr@pcorp.us</a> <mailto:<a href="mailto:lr@pcorp.us" target="_blank">lr@pcorp.us</a>>> wrote:<br>
> <br>
> Sorry haven’t had a chance to look thru this yet. Going to be tied up for the next two weeks so I might not get a chance until much later.____<br>
> <br>
> __ __<br>
> <br>
> If any others are interested in investigating, please don’t wait for me.____<br>
> <br>
> __ __<br>
> <br>
> Thanks,____<br>
> <br>
> Regina____<br>
> <br>
> __ __<br>
> <br>
> *From:*Andreas B <<a href="mailto:panden@gmail.com" target="_blank">panden@gmail.com</a> <mailto:<a href="mailto:panden@gmail.com" target="_blank">panden@gmail.com</a>>><br>
> *Sent:* Friday, December 13, 2024 6:48 AM<br>
> *To:* <a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a> <mailto:<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>><br>
> *Subject:* Re: Importing tiles with raster2pgsql____<br>
> <br>
> __ __<br>
> <br>
> Regina,____<br>
> <br>
> __ __<br>
> <br>
> I'm linking to a folder with a zip containing a subset of tiles that demonstrates my problem, a script to run the commands, and two screenshots.<br>
> Note that I'm a PostGIS beginner, so it's possible I'm doing something wrong!____<br>
> <br>
> The issues encountered differs a bit from what I described yesterday, but the essence is the same.____<br>
> <br>
> __ __<br>
> <br>
> Link to folder: <a href="https://www.dropbox.com/scl/fo/bk8cwktahry0oj0ab2rsz/AHdTD73unb4Efxtgf7exfm0?rlkey=esjtw2iyzysan2hdqklwmj5e3&st=hupv5tsr&dl=0" rel="noreferrer" target="_blank">https://www.dropbox.com/scl/fo/bk8cwktahry0oj0ab2rsz/AHdTD73unb4Efxtgf7exfm0?rlkey=esjtw2iyzysan2hdqklwmj5e3&st=hupv5tsr&dl=0</a> <<a href="https://www.dropbox.com/scl/fo/bk8cwktahry0oj0ab2rsz/AHdTD73unb4Efxtgf7exfm0?rlkey=esjtw2iyzysan2hdqklwmj5e3&st=hupv5tsr&dl=0" rel="noreferrer" target="_blank">https://www.dropbox.com/scl/fo/bk8cwktahry0oj0ab2rsz/AHdTD73unb4Efxtgf7exfm0?rlkey=esjtw2iyzysan2hdqklwmj5e3&st=hupv5tsr&dl=0</a>>____<br>
> <br>
> __ __<br>
> <br>
> Best,____<br>
> <br>
> Andreas____<br>
> <br>
> __ __<br>
> <br>
> On Thu, Dec 12, 2024 at 3:26 PM Regina Obe <<a href="mailto:lr@pcorp.us" target="_blank">lr@pcorp.us</a> <mailto:<a href="mailto:lr@pcorp.us" target="_blank">lr@pcorp.us</a>>> wrote:____<br>
> <br>
> Andreas,____<br>
> <br>
> ____<br>
> <br>
> Yes I would expect them to give the same result.____<br>
> <br>
> ____<br>
> <br>
> What version of raster2pgsql are you running? It should tell you if you run raster2pgsql without any args.____<br>
> <br>
> ____<br>
> <br>
> Also what platform are you on? Any chance you have some of those tiles available so we can check it out?____<br>
> <br>
> ____<br>
> <br>
> *From:*Andreas B <<a href="mailto:panden@gmail.com" target="_blank">panden@gmail.com</a> <mailto:<a href="mailto:panden@gmail.com" target="_blank">panden@gmail.com</a>>><br>
> *Sent:* Thursday, December 12, 2024 6:17 AM<br>
> *To:* <a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a> <mailto:<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>><br>
> *Subject:* Importing tiles with raster2pgsql____<br>
> <br>
> ____<br>
> <br>
> Hi all,<br>
> <br>
> I have a dataset with several hundred tiles (GeoTIFFs) that make up a digital terrain model.<br>
> Each tile is 0.5d x 0.5d.<br>
> <br>
> I tried to load these GeoTIFFs to PostGIS with:<br>
> <br>
> $ raster2pgsql -s 32631 -I -M -F -C -t auto -d -l 2,4,8,16,32 tif/*.tif (1)<br>
> <br>
> The data was loaded, but when viewing in QGIS, it looked like jagged lines with areas of white overlain by pieces of neighboring tiles, etc.<br>
> This didn't look right.<br>
> I also noticed that for each tif, the constraints were printed.<br>
> I expected this to be done once, after the last tile was loaded.<br>
> <br>
> I then created a virtual raster with gdalbuildvrt:<br>
> <br>
> $ gdalbuildvrt merge.vrt tif/*.tif (2)<br>
> <br>
> And then used raster2pgsql to load in the vrt:<br>
> <br>
> $ raster2pgsql -s 32631 -I -M -F -C -t auto -d -l 2,4,8,16,32 merge.vrt | psql (3)<br>
> <br>
> The data was loaded, and looked good in QGIS.<br>
> <br>
> Shouldn't commands (1) and (3) give the same results, or am I misunderstanding?<br>
> <br>
> Best, Andreas____<br>
> <br>
<br>
</blockquote></div>