To test your own development, you may have a more pleasant experience
by directly running just the tests for your driver with something like
"pytest autotest/ogr/ogr_miramon.py" (be careful on Windows, the
content of $build_dir/autotest is copied from $source_dir/autotest
each time "cmake"
Hi Even,
I can share in private the image. Should I send it directly to your
@spatialys.com account?
Jesse
From: Even Rouault
Date: Friday, February 9, 2024 at 12:24 PM
To: "Meyer, Jesse R. (GSFC-618.0)[SCIENCE SYSTEMS AND APPLICATIONS INC]"
, "gdal-dev@lists.osgeo.org"
Subject: [EXTERNAL]
Le 09/02/2024 à 18:13, Meyer, Jesse R. (GSFC-618.0)[SCIENCE SYSTEMS AND
APPLICATIONS INC] via gdal-dev a écrit :
I noticed a warning after converting a gtiff image to jp2 stating
‘Warning 6: Unhandled projection method Albers_Conic_Equal_Area’. The
driver apparently completes the
I noticed a warning after converting a gtiff image to jp2 stating ‘Warning 6:
Unhandled projection method Albers_Conic_Equal_Area’. The driver apparently
completes the conversion and happily reports the projection correctly under
gdalinfo. But I find it weird that the format would care about
+1
Howard
> On Feb 9, 2024, at 8:04 AM, Rahkonen Jukka via gdal-dev
> wrote:
>
> +1
>
> -Jukka Rahkonen-
>
> -Alkuperäinen viesti-
> Lähettäjä: gdal-dev Puolesta Even Rouault
> via gdal-dev
> Lähetetty: perjantai 9. helmikuuta 2024 11.13
> Vastaanottaja: gdal-dev@lists.osgeo.org
>
Hi all,
I'm seeing an odd artifact when using gdal_fillnodata.py.
My source raster is (https://i.stack.imgur.com/t42tR.png)
(purple is no data, white and black are two different numeric values).
Using a mask exactly corresponding to the no data pixels (i.e. all no
data pixels are set to 0 in
Thanks TB!
From: thomas bonfort
Date: Friday, February 9, 2024 at 9:50 AM
To: "Meyer, Jesse R. (GSFC-618.0)[SCIENCE SYSTEMS AND APPLICATIONS INC]"
Cc: "gdal-dev@lists.osgeo.org"
Subject: Re: [EXTERNAL] Re: [gdal-dev] GeoTiff JXL sample format & bits per
sample restrictions?
CAUTION: This
doc update PR in https://github.com/OSGeo/gdal/pull/9220
On Fri, Feb 9, 2024 at 3:38 PM Meyer, Jesse R. (GSFC-618.0)[SCIENCE SYSTEMS
AND APPLICATIONS INC] wrote:
> We can work with the Uint16 case. These dtype limitations should be
> listed on the gtiff docs presumably.
>
>
>
> *From: *thomas
We can work with the Uint16 case. These dtype limitations should be listed on
the gtiff docs presumably.
From: thomas bonfort
Date: Friday, February 9, 2024 at 9:37 AM
To: "Meyer, Jesse R. (GSFC-618.0)[SCIENCE SYSTEMS AND APPLICATIONS INC]"
Cc: "gdal-dev@lists.osgeo.org"
Subject: [EXTERNAL]
JXL in tiff should support the 2 band case correctly. What is not supported
here is the int16 datatype. Only uint8, uint16 and float32 are supported.
TB
On Fri, Feb 9, 2024 at 3:32 PM Meyer, Jesse R. (GSFC-618.0)[SCIENCE SYSTEMS
AND APPLICATIONS INC] via gdal-dev wrote:
> We are trying to
Gladly,
Driver: GTiff/GeoTIFF
Files: in.tif
Size is 32000, 32000
Coordinate System is:
PROJCRS["Africa_Albers_Equal_Area_Conic",
BASEGEOGCRS["WGS 84",
DATUM["World Geodetic System 1984",
ELLIPSOID["WGS 84",6378137,298.257223563,
LENGTHUNIT["metre",1]]],
could you share the output of "gdalinfo in.tif" please?
On Fri, Feb 9, 2024 at 3:32 PM Meyer, Jesse R. (GSFC-618.0)[SCIENCE SYSTEMS
AND APPLICATIONS INC] via gdal-dev wrote:
> We are trying to convert a 2 band int16 ZSTD compressed geotiff to JXL
> compression. However for each band the
We are trying to convert a 2 band int16 ZSTD compressed geotiff to JXL
compression. However for each band the following error message is given “ERROR
1: GetJXLDataType:Unsupported combination of SampleFormat and BitsPerSample”.
On GDAL 3.8.3, released 2024/01/04. JXL v0.9.2
gdal_translate
+1
-Jukka Rahkonen-
-Alkuperäinen viesti-
Lähettäjä: gdal-dev Puolesta Even Rouault
via gdal-dev
Lähetetty: perjantai 9. helmikuuta 2024 11.13
Vastaanottaja: gdal-dev@lists.osgeo.org
Aihe: [gdal-dev] Motion: Adopt GDAL 3.8.4RC1 as 3.8.4 release
Hi,
Motion:
Adopt GDAL 3.8.4RC1 as
+1 Javier
On Fri, 9 Feb 2024 at 10:13, Even Rouault via gdal-dev <
gdal-dev@lists.osgeo.org> wrote:
> Hi,
>
> Motion:
>
> Adopt GDAL 3.8.4RC1 as 3.8.4 release
>
> Starting with my +1
>
> Even
>
> --
> http://www.spatialys.com
> My software is free, but my time generally not.
>
>
Abel,
Le 09/02/2024 à 10:55, Abel Pau via gdal-dev a écrit :
Hi,
I am at the lasts steps before pulling a request about the MiraMon
driver.
I need to write some documentation and formalize the tests.
After that, I’ll do the pull request to github.
I'd suggest first before issuing the pull
Hi,
I am at the lasts steps before pulling a request about the MiraMon driver.
I need to write some documentation and formalize the tests.
After that, I'll do the pull request to github.
I am a little confused about the testing. I can use pytest or ctest, right?
Which is the favourite? Are there
Hi,
Motion:
Adopt GDAL 3.8.4RC1 as 3.8.4 release
Starting with my +1
Even
--
http://www.spatialys.com
My software is free, but my time generally not.
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
18 matches
Mail list logo
