Alan D. Snow

@Zeitsperre is this something you still have interest in implementing?

Maybe something like: ```python self._obj.assign_coords( {self.x_dim: (((self._obj[self.x_dim] + 180) % 360) - 180)} ).sortby(self.x_dim) ```

@Zeitsperre can you provide a simplified code-example of your workflow?

Hmmm, I don't have a suggestion at the moment. Would probably have to get pretty deep into the weeds before I could do so.

The `.sortby(self.x_dim)` is something that is sometimes necessary for geospatially referencing the data: https://github.com/corteva/rioxarray/issues/58#issuecomment-612062722

There are likely minor differences in the decimal precision of the transform/boundary your files that could cause the issue. I think the solution you provided is a great way to...

Mind printing the transform similar to how you did the bounds/resolution?

Thanks - as a side note, in rioxarray, transform is a method as there are options you can pass in. You will be able to see the value by calling...

That is definitely strange. Based on what you have posted, I don't see anything different between the rasters.

Seems related to #73. They must have moved it again.