Le 02/06/2021 à 22:08, Javier Jimenez Shaw a écrit :
Hi Evert,
As far as I know, TIFF data type is "constant" along the bands. You
cannot have a uint16 band and a byte band in the same page.
Yes, in theory this would be possible since the SampleFormat tag has as
many values as bands
Hi Evert,
As far as I know, TIFF data type is "constant" along the bands. You cannot
have a uint16 band and a byte band in the same page.
If you are worried about space, you can use the "nodata value", assigning a
single value for that purpose (assuming that you do not want intermediate
values,
Even,
Sounds good. Until there is consensus on what coordinate epoch means for
OGC:CRS84 GeoJSON, the official and most widely used kind, I think it would
be better if GDAL didn't extend the format. For now, applications that need
more precision can and should use another format.
On Thu, May 27,
Hi Sean,
I've got two questions. I don't think they need answers before we
vote, but I'm curious if asking them leads to any useful discussion.
Will we strictly require project proposals to be submitted and
approved before work starts? Will we allow works in progress to apply
for funding?
I
Dear all,
I was wondering if there is a best practice or guide for the data type of alpha
channels in geotiffs.
I have many files where the data type is constant over all bands (UInt16 for
example).
I would expect the alpha band to be a byte band or even bit.
Is it possible to have different
Hi Even,
I've got two questions. I don't think they need answers before we vote, but
I'm curious if asking them leads to any useful discussion.
Will we strictly require project proposals to be submitted and approved
before work starts? Will we allow works in progress to apply for funding?
However, if I run the full test suite, it fails collecting
alg/fillnodata.py
(I work it around with "pytest --continue-on-collection-errors")
The issue is that pytest 4.6.9 is too old. I've just bumped the min
version to 6.0.0
$ pytest
Test session starts (platform: linux, Python
Thanks Even and Andrew for your answers.
Andrew, somehow I had a workaround for the pytest-3 (that I absolutely
forgot), but thanks for the info.
Even, with the "--with-python" everything goes much better...
Now I can run tiff tests without any failure!
pytest gcore/tiff_*
However, if I run the
Javier,
CONTRIBUTING.md was missing the --with-python configure switch to build
the python bindings. Now fixed
So re-run ./configure --with-python && make -j8 -s , and also source
again ". scripts/setdevenv.sh" so that PYTHONPATH is set appropriately
You can check that everything is OK
On Wed, 2 Jun 2021, Javier Jimenez Shaw wrote:
Hello
I am trying to build GDAL (this worked) and run the tests (tons of
failures). Because it is over a clean clone of master, I think there is
something wrong in my configuration. Maybe you can help me.
cd ../autotest
pip install -r
Hello
I am trying to build GDAL (this worked) and run the tests (tons of
failures). Because it is over a clean clone of master, I think there is
something wrong in my configuration. Maybe you can help me.
OS: Ubuntu 20.04
Python: 3.8.5
$ apt list --installed | grep gdal
gdal-bin/focal,now
Hi,
are there any remaining comments before we put that to vote ?
Even
Le 19/05/2021 à 14:46, Even Rouault a écrit :
Hi,
in parallel to finalizing the last steps to get the relationship with
NumFOCUS fully operational, here's a new RFC for your consideration to
give guidelines on how we
12 matches
Mail list logo
