Alan D. Snow

I like the work organization, that is very helpful. Thanks @sgillies @groutr for your upcoming work! I am looking forward to it. My free time is uncertain, so I cannot...

I am sorry to hear that @sgillies. I wish you the best as you take a break and move forward.

I have tested 1.4a2 on other libraries that depend on it and everything seems to be working as expected.

> Is there a functional reason to putting things like this in .encoding or are you just trying to cache things in a less visible place compared to .coords? Does...

> what things would you have done differently in rioxarray as far as dimension and CRS handling? Nothing comes to mind at the moment. The philosophy is to be able...

> There is a good chance that I'll be copying large chunks of rioxarray (let's be nice and say "extracting") for CRS handling...if that's OK with you and you don't...

> Doesn't this prevent users from assigning their own CRS? Or does it not come up very often? `.write_crs` is the recommended method. Otherwise, the CRS doesn't persist very well....

> What performance issues is this comment referring to This is the issue that inspired the change: https://github.com/corteva/rioxarray/issues/241 However, pyproj/PROJ have had performance improvements since such that I don't think...

> If I make set_crs private with _set_crs, then this means there is no concept for the user of setting CRS information inside the accessor, right? Correct. > Biggest problem...

> don't you run into the same issues you had/have with CRS as far as persisting the information across instances of the Accessor? Yes, the same issues exist. > Or...