Alan D. Snow

This is how rioxarray adds coordinates based on the transform: https://github.com/corteva/rioxarray/blob/c15b86061feff8c2c7b0964f19922a3154a85f1a/rioxarray/_io.py#L1203-L1206

#209 may be helpful.

This was by design to keep the logic simple. As you demonstrated, there are cases where you would transform from geographic to projected coordinate systems or the other way around....

Thank you for sharing, that looks useful. > And so I am wondering: where do you think those functionalities should live if we build an xarray accessor? I think it...

Side note: The `.geo` accessor is being used by [geoxarray](https://github.com/geoxarray/geoxarray/).

@RichardScottOZ are you able to provide a simple, reproducible example?

@veenstrajelmer, I don't think your example is related to this discussion. I believe that it is more closely related to: https://github.com/corteva/rioxarray/issues/174

I had thought about using that. Not opposed to using that as an engine for interpolation.

https://github.com/corteva/rioxarray/pull/600#discussion_r1011706293 > The variable name should only contain alphanumeric characters and underscores. The band description could potentially be a sentence with any characters. This ensures consistency and stability.

I don't think this is too terrible for users to do if they have a safe `long_name`: ```python image = image.rename({band:image[band].attrs["long_name"] for band in image}) ```