Tom Vo

Hey @jasonb5 and @chengzhuzhang, I found these features from `geocat-comp`. Can you take a look and see if it fits our requirements so we don't end up duplicating functionalities? -...

Thanks for opening this issue @ezekiel-lemur! We'll take a look at it.

> In most case xcdat presumes dataArray for coordinate or axis to be 1-dimensional (@tomvothecoder please correct me if I am wrong) Thanks for helping debug, Jiwoo! Yes this is...

> If someone else could verify this on Mac, then I think this might be isolated to a cftime + linux issue. I created a fresh environment with `conda create...

I ran the same sets of code in my above [comment](https://github.com/xCDAT/xcdat/issues/648#issuecomment-2075390607) on Linux (RH7) and I get the same error. I think this confirms it is a `cftime` + Linux...

@ezekiel-lemur Of course! Thanks for working with us through this issue. Hopefully it can be resolved soon. The (inconvenient) alternative is to try your code on a non-Linux based machine...

Just an update about why this bug only happens on Linux ([comment](https://github.com/Unidata/cftime/issues/328#issuecomment-2086109486)): > I suspect that the problem is that the operations with NaNs can give compiler-dependent results (hence the...

> Hey! I see the issue was closed on Nctime, but I am not sure what the solution is for now? Would you be so kind and let me know...

> Just a note...it's not clear to me that things will work correctly after the cftime PR is merged (I'm not sure how xarray is going to handle masked arrays...

Thanks for opening for this Steve. > If the latitude axis doesn't have `axis=Y` set, we should still be able to recognize it as a latitude axis if it is...