you need
gdalinfo --config GDAL_HTTP_HEADERS="Authorization: Bearer "
"/vsicurl/https://n5eil01u.ecs.nsidc.org/…
Where "" is an Earthdata access token from your account.
https://urs.earthdata.nasa.gov/documentation/for_users/user_token
HTH (there are other methods like setting GDAL_HTTP_HEAD
> This HDF5 (requires earthdata credentials your "Authorization: Bearer
> " in GDAL_HTTP_HEADERS, or equiv) presents without geolocation arrays.
gdalinfo
"/vsicurl/https://n5eil01u.ecs.nsidc.org/AMSA/AU_SI12.001/2012.07.02/AMSR_U2_L3_SeaIce12km_B04_20120702.he5";
-sd 26
Excuse for this little
Oh wow, that's fantastic - thanks so much. Lots for me to learn from there
too, with the HDF5EOS GRID details.
Cheers, Mike
On Tue, Apr 30, 2024 at 6:08 AM Even Rouault
wrote:
> Michael,
>
> actually support for those products was already there at 95% since they
> use the HDF5EOS GRID formalis
Michael,
actually support for those products was already there at 95% since they
use the HDF5EOS GRID formalism which we support since 3.7. But that
particular type of products has an oddity. They have an empty
GROUP=Dimension within the GROUP=GridStructure in the HDF5EOS metadata,
which our
