Closed bnlawrence closed 1 week ago
Part of the commit referenced above is designed to handle this, but I need unit tests, but I don't know how to set up the cfa file correctly. See the end of the cfa_resources
fixture in test_60_cfa_import.py
. I need help from the CFA team.
I have a temporary expedient in the unit tests now, using xarray, but we should remove that.
Explicitly, we should remove the xarray hack in the test cfa_resource
found in test_60
and use the correct CF interface. Given that interface is new, it may be worth considering whether or not it is fit for purpose as is.
This is probably too woolly as a problem description. Suffice to say I think the first issue is to set up some tests, and then pass me the problem of fixing the backend.
We've got rid of base locations!
E.g. fragment names like this are wrong:
Unavailable should be a location. We are not stripping these correctly, or dealing with the substitution variables properly.