Closed sckott closed 6 years ago
the /info
ERDDAP request is returning the wrong information.
e.g. https://upwell.pfeg.noaa.gov/erddap/info/noaa_esrl_d7ee_ffb3_d5a0/index.json
is returning for latitude
["attribute", "latitude", "actual_range", "float", "-89.75, 89.75"],
which is in the opposite order from what the web interface has https://upwell.pfeg.noaa.gov/erddap/griddap/noaa_esrl_d7ee_ffb3_d5a0.html
we definitely depend on the order of the min and max of lat and long to be in the same order that the ERDDAP server expects, so AFAICT we're at a dead end here unless maybe the ERDDAP /info
request is returning the wrong data, and it can be fixed?
thoughts @rmendels ?
Hi Scott:
This is exactly what I reported to you in issue #68, and warned you that you needed to change. The reason for this is the CF standard now says that the metadata for the range should have the lowest first and the highest second, regardless of the ordering in the file. The solution, as I reported in Issue #68, is to use the latitude_spacing. I even gave sample (but kludgy) code, based on what is already contained in a call to rerddap::info().
I have already changed this in rerddapXtracto, so that I change the latitudes myself based on spacing, and it goes through rerddap.
-Roy
should be fixed in #68