Even,
Thank you for your response. I also suspect there is some mixing going
on. I will have a deeper look at that.
Thank you for your time.
Hernán
BTW the output of the command you suggest is very much like yours:
> grep HDF4 CMakeCache.txt | grep -v INTERNAL | grep -v ADVANCED
//Set ON
Hernan,
this works for me both with HDF4 4.2.14 as available on my system, and
also against 4.3.0 built from source with the exact configure command
line your provided
Can you show the result of "grep HDF4 CMakeCache.txt | grep -v INTERNAL
| grep -v ADVANCED" in your GDAL build directory?
Hi,
I can't help you with building GDAL but I can show where to learn the
difference between --formats and --format:
https://gdal.org/en/latest/programs/raster_common_options.html#raster-common-options
-Jukka Rahkonen-
Lähettäjä: Hernán De Angelis
Lähetetty: maanantai 11. marraskuuta 2024 14.
Thank you for your response, Jukka.
That is interesting. I set cmake to build hdf4, cmake sees it and it
does not throw errors during the build. In fact, I see:
[ 38%] Built target gdal_HDF4
but the command you gave gives not HDF4
gdalinfo --format hdf4
(should be "formats" instead?)
gdalin
Hi,
Have you checked with gdalinfo if you have managed to build the HDF4 driver?
gdalinfo --format hdf4
Your test file opens for me with GDAL from OSGeo4W.
-Jukka Rahkonen-
Lähettäjä: gdal-dev Puolesta Hernán De
Angelis via gdal-dev
Lähetetty: maanantai 11. marraskuuta 2024 13.37
Vastaanottaj
I recently compiled a minimal GDAL (3.10) with HDF4 support (using HDF
4.3.0) for processing MODIS L1B data. However, the resulting command
line tools cannot understand the format. Perhaps I am doing something
wrong, or missing something important, or both.
Do I understand correctly that MODIS
