Thanks Even Rebuilding my HDF+netCDF+GDAL stack, but now when issue the final
nmake /f makefile.vc devinstall it errors after a while with (complains about doxygen). This didn't use to happen. I have a Win doxygen but it's not (never been) in the path. make: Entering directory '/c/programs/compa_libs/gdal_GIT/gdal/doc' mkdir -p build/xml && cd .. && ((cat Doxyfile | sed "s/PREDEFINED = /PREDEFINED = DOXYGEN_XML /"; printf "GENERATE_HTML=NO\nGENERATE_XML=YES\nXML_OUTPUT=doc/build/xml\nXML_PROGRAMLISTING=NO") | doxygen -) /bin/sh: doxygen: command not found make: *** [Makefile:22: .doxygen_up_to_date] Error 127 make: Leaving directory '/c/programs/compa_libs/gdal_GIT/gdal/doc' NMAKE : fatal error U1077: 'C:\MinGW64\msys64\usr\bin\make.EXE' : return code '0x2' Stop. |>-----Original Message----- |>From: Even Rouault <even.roua...@spatialys.com> |>Sent: Saturday, June 1, 2019 9:38 AM |>To: gdal-dev@lists.osgeo.org |>Cc: Joaquim Manuel Freire Luís <jl...@ualg.pt> |>Subject: Re: [gdal-dev] vsicurl access to a netcdf file does not see the |>coordinates |> |>On vendredi 31 mai 2019 23:49:09 CEST Joaquim Manuel Freire Luís wrote: |>> Hi, |>> |>> GDAL master here |>> |>> When I run gdalinfo on a remote nc file, instead of reporting the |>> coordinates it prints the array size |> |>Joaquim, |> |>Note that in the /vsicurl/ case, the file gets opened by the HDF5Image driver |>whereas in the non vsicurl case, by the netCDF driver, hence the difference. |>A recent enough version (4.5 I believe) of libnetcdf must be used so that / |>vsicurl/ can be used by the netCDF driver (you must see 'NetCDF has |>netcdf_mem.h: yes' in configure output) |> |>Even |> |>-- |>Spatialys - Geospatial professional services http://www.spatialys.com _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
