Hi,
I’m looking for a simple convention to represent SRS and Geotransform
information for HDF5 arrays. A fairly thorough reading of available HDF5
geospatial data representation specs hasn’t resulted in a satisfactory
solution. I know that HDF-EOS5 is a published spec but the unintuitive nam
Maybe it is configurable as Gdal.SetConfigOption("GDAL_TIFF_INTERNAL_MASK",
"YES"); before Gdal.wrapper_GDALTranslate calling?
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
h
How to send the parameter "--config GDAL_TIFF_INTERNAL_MASK YES" as option to
the method Gdal.wrapper_GDALTranslate.
There is an exception if I split it as follows:
"--config GDAL_TIFF_INTERNAL_MASK YES"
or
"--config", "GDAL_TIFF_INTERNAL_MASK YES"
or
"--config", "GDAL_TIFF_INTERNAL_MASK", "YES"
How to send the parameter "--config GDAL_TIFF_INTERNAL_MASK YES" as option to
the method Gdal.wrapper_GDALTranslate.
There is an exception if I split it as follows:
"--config GDAL_TIFF_INTERNAL_MASK YES"
or
"--config", "GDAL_TIFF_INTERNAL_MASK YES"
or
"--config", "GDAL_TIFF_INTERNAL_MASK", "YES"
I tried the following:
git clone https://github.com/GeographicaGS/Docker-GDAL2.git
cd Docker-GDAL2/2.2.4
#Edit Dockerfile and set 'ENV OPENJPEG_VERSION 2.3.0'
docker build -t gdal2:local ./
cd /path/to/jp2
docker run -t -i gdal2:local -v $(pwd):/data /bin/bash
gdalinfo -stats /data/850011.jp2
An
> That must be some developper sense of humour.
Consider that my attempt at nudging the GDAL community to improve their
documentation :-)
/Kristian
> On 19 Jun 2018, at 21:05, Erik Sørngård
> wrote:
>
> Hello Even,
>
> Thank you clarifying that PROJ documentation is not accurate. I had seen
On mardi 19 juin 2018 16:57:30 CEST Stephen Woodbridge wrote:
> Hi all,
>
> I'm having a problem readding jp2 files. My goal is to be able to
> display them through mapserver, but I'm have problems with gdalinfo and
> gdal_translate. I set up a docker image with the latest gdal2 in it like
> the f
Hi all,
I'm having a problem readding jp2 files. My goal is to be able to
display them through mapserver, but I'm have problems with gdalinfo and
gdal_translate. I set up a docker image with the latest gdal2 in it like
the following. I have 1074 jp2 files and all that I have tried are
throwi
Hello Even,
Thank you clarifying that PROJ documentation is not accurate. I had seen the
source code before, but was hoping for a supporting document as well.
Based on your input and looking at the source code again today, I expect the
data to be stored as longitude and latitude offset pairs, e
On 19 June 2018 at 11:50, Alex HighViz wrote:
> On 19/06/2018 10:28, Mateusz Loskot wrote:
>> On 19 June 2018 at 11:22, Alex HighViz wrote:
>>> Regrettably I overstated the performance in my previous post, due to a bug
>>> that is now solved. With the solved bug, Pronto is about 50% slower than
Erik,
>
> I have been looking at PROJ's support for grid files, and notice that they
> refer to "GDAL documentation" for format details about CTable2.
>
> While browsing the GDAL site I have so far not been able to locate this
> information, except for being part of the list of supported file fo
Dear Sirs,
I have been looking at PROJ's support for grid files, and notice that they
refer to "GDAL documentation" for format details about CTable2.
While browsing the GDAL site I have so far not been able to locate this
information, except for being part of the list of supported file formats:
On 19/06/2018 10:28, Mateusz Loskot wrote:
> On 19 June 2018 at 11:22, Alex HighViz wrote:
>> Regrettably I overstated the performance in my previous post, due to a bug
>> that is now solved. With the solved bug, Pronto is about 50% slower than
>> GDAL directly. I believe this is still good co
On 19 June 2018 at 11:22, Alex HighViz wrote:
>
> Regrettably I overstated the performance in my previous post, due to a bug
> that is now solved. With the solved bug, Pronto is about 50% slower than GDAL
> directly. I believe this is still good considering the benefits, but not as
> glamorous
> Even Rouault wrote
> A few thoughts:
[ ]
> 1000x1000 is somewhat small. Perhaps benchmark on larger rasters
I am still working on your other suggestions, but thought it would be fair to
report on my progress.
Regrettably I overstated the performance in my previous post, due to a bug that
is
15 matches
Mail list logo