Hi,
Just to notify (mostly packagers) that libxml2 2.12 has been released 2
days ago, and GDAL needs the following 2 patches to build against it:
-
https://github.com/OSGeo/gdal/commit/cbed9fc91dffba30d0f9a6a06a412a04d9cd36fa
-
https://github.com/OSGeo/gdal/commit/ec33f6d6dfe944f59dc5454
Hei,
flesh-and-bones-user from Norway here too.
When the OpenFYBA library and the OGR-SOSI driver were revived roughly 10 years ago, Kartverket already had plans to replace the SOSI format and communicated what you now heared at the community sprint, Even. I see that Mathieu confirmed that
Hi again,
I am not and have never been a contributor the to (Open)FYBA library. When it
comes to challenges inherent to keeping an updated version of the SOSI driver
in GDAL/OGR, I am not the best person to elaborate on that matter.
The statement "SOSI will no longer be used as exchange format
Hello,
I have a question about how to properly set the -tr flag when using
gdalwarp.
In particular, I'm using gdalwarp for resampling a GeoTiff from its
original resolution to a target resolution.
Let's consider, for simplicity, the original pixel size equal to (5m, 5m)
and the target resolution e
Giovanni,
gdalwarp takes the absolute value of the second tr value, so -tr 10 -10
is understood as -tr 10 10
It is expected that gdalinfo reports a negative value for the pixel size
factor for the vertical axis, as in GeoTIFF when the image is north-up,
the first line of the image is intende
Thank you very much.
Just to be sure, gdalwarp takes the absolute value of the second tr value
independently from the units of the pixel size.
It can be either meters or degrees depending on the coordinate reference
system. Is that correct?
Thanks again,
Giovanni
Il giorno sab 18 nov 2023 alle o
