-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ASF GRFN products and GDAL3's vsis3 #25
Comments
Turns out this is related to them building conda packages on old kernels: userfaultfd support: no This is unlikely to change anytime soon. Piyush |
@piyushrpt We don't have a formal way to announce possible bugs that aren't directly related to to notebook servers but are worth mentioning. So I guess that issuing a The current notebook servers are built using GDAL 2.4. For ISCE, It's install on Ubuntu 18.04 via (https://github.com/asfadmin/asf-jupyter-container/blob/master/dockerfile):
I ran the test script you mentioned in the production cluster and got
So it would appear that GRFN products are interpreted as HDF5. |
Tracking this here: conda-forge/gdal-feedstock#323 |
I reran the script against production again and got
Since the tracked conda-forge link has closed the issue and the products are reported as netCDF, this issue appears to be resolved. |
Hi,
Don't know if this is the right place to report this. Most of us end up using jupyter via conda and looks like gdal3 build with conda might not be recognizing netcdf_mem.h correctly. If this is not an issue with custom build GDAL; then this should be reported to conda-forge/gdal-feedstock.
I remember this being addressed by OSGeo/gdal#1328
Here is a test script that shows that GRFN products are interpreted as HDF5:
Piyush
The text was updated successfully, but these errors were encountered: