Jukka,
What's the exact use case for needing to know if a tiff is traditional or
BigTIFF? Is there a key tool that doesn't understand BigTIFF? The only one
I know of is Autodesk Civil3D.
Thanks,
-Kurt
On Thu, Nov 2, 2023 at 2:49 PM Even Rouault via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
>
Jukka,
Does it feel reasonable? I know that overviews may be standard TIFFs
while the main image is BigTIFF but maybe the information from the
header would be enough. Or have I missed some existing tool? I thought
that tiffinfo at least would report TIFF/BigTIFF but it doesn’t.
tiffdump
Hi,
I tried to find some easy way for checking with GDAL if an image is a standard
TIFF or BigTIFF but I could not find any. It seems that "more big.tiff" on
Windows finds "II+" from the beginning of the file if the image is BigTIFF and
"II*" otherwise. Or then I can open the image with a hex
Howard,
I would like to see some language that describes the expectations for
version compatibility of plugins (ie, what happens with a plugin built
against x.0 is used against a main library of y.0).
This RFC actually doesn't change anything regarding this. See the
mention of the
> On Nov 2, 2023, at 6:59 AM, Even Rouault via gdal-dev
> wrote:
>
> Hi,
>
> I'm seeking for feedback and review on a new RFC (RFC 96: Deferred in-tree
> C++ plugin loading),
> detailed in https://github.com/OSGeo/gdal/pull/8648, whose summary is:
>
> This RFC adds a mechanism to defer the
Hi Sean,
Rasterio's CI picked up a change to the AAIGrid driver in 3.8. The 3.7
version driver used to have whitespace before a row and no whitespace
after. It looks like this has flipped in 3.8. Is it intentional?
Yes: https://github.com/OSGeo/gdal/pull/8362
Even
--
I'm changing Rasterio's CI to test against both the head of the master
branch and the head of the current release branch, so in the future I'll
likely only speak up if something is broken right before the release.
3.7.3RC1 looks good to me. I can't think of anything missing.
On Wed, Nov 1, 2023
Hi Even,
Rasterio's CI picked up a change to the AAIGrid driver in 3.8. The 3.7
version driver used to have whitespace before a row and no whitespace
after. It looks like this has flipped in 3.8. Is it intentional? I only
noticed because one of my tests is parsing the file as text. It's certainly
Thanks Even for the RFC!
After a quick read, this seems reasonable. I was mostly concerned about the
impact on folks who statically build everything (my biggest use case), but
that is completely addressed in the doc.
On Thu, Nov 2, 2023 at 5:00 AM Even Rouault via gdal-dev <
Hi Rob,
This looks great from my perspective. Are there any downsides?
- A bit of additional coding complexity for driver development, but not
that much
- As mentioned in the backwards compatibility paragraph, for people
doing multi-step builds to build first libgdal and then plugins,
Hi Even,
On Thu, 2 Nov 2023 at 11:59, Even Rouault via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
>
> I'm seeking for feedback and review on a new RFC (RFC 96: Deferred
> in-tree C++ plugin loading), detailed in
> https://github.com/OSGeo/gdal/pull/8648, whose summary is:
>
> This RFC adds a
Hi,
I'm seeking for feedback and review on a new RFC (RFC 96: Deferred
in-tree C++ plugin loading),
detailed in https://github.com/OSGeo/gdal/pull/8648, whose summary is:
This RFC adds a mechanism to defer the loading of in-tree C++ plugin
drivers to
the point where their executable code is
Craig,
remove the leading end-of-line and spaces in your ExecuteSQL
l = ds.ExecuteSQL(
"""SELECT *
FROM "open-data-platform:v_s_parcel_proposed"
ORDER BY "parcel_pfi" ASC
"""
)
Also fixed
perhttps://github.com/OSGeo/gdal/commit/f6c7d95e2c66ba1f62f6ff17e31af37f7f8f6bc8
Even
13 matches
Mail list logo
