Forum

The coordinate arrays are recognized as "geolocation arrays": ``` gdalinfo NETCDF:"S3B_OLCI_ERRNT.20250101T164657.L2.IOP.NRT.nc":/geophysical_data/bb_443 ... Geolocation: SRS=GEOGCS["WGS 84",DATUM["WGS_1984",SPHEROID["WGS 84",6378137,298.257223563,AU...

I've made a note of this and will try to get this fixed in a future GDAL, this is presumably a common way to georeference with the XDim/YDim coord values. Just generally, I would suggest reporting examples like this directly as issues on the repo, or ask on gdal-dev, there's no end to the variations...

I'm exploring the virtual JSON kerchunk stores, and I can't find out how to authorize for data-read. I can connect to a remote store and see the dataset md fine: ```python import xarray u = "https://archive.podaac.earthdata.nasa.gov/podaac-ops-cumulus-docs/ccmp/open/L4_V3.1/docs/CCMP_WINDS_10M6...

Very glad to see this reported, I heard about it and had emailed it so just wanted to indicate I'm aware of this discussion. We're working on a reformat into GeoTIFF and I'd like to discuss further issues that we see with these files. The degenerate rectilinear coords have sufficient noise that they...

R can lazy load from netcdf via URLs in the usual ways, here the {terra} package leverages GDAL to do the work (I'm not using your dataset exactly but happy to rejig if you want to share specifics): ``` library(terra) url <- "https://archive.podaac.earthdata.nasa.gov/podaac-ops-cumulus-protecte...