Philip Chmielowiec

Would you mind sharing the FESOM grid you used in the simple example notebook?

@fluidnumerics-joe Thanks for the example! I've opened up a pull request (https://github.com/UXARRAY/uxarray/pull/1013) for this. Will work on it this week.

This seems like a good candidate for our [cookbook](https://github.com/ProjectPythia/unstructured-grid-viz-cookbook).

@erogluorhan Do we want to close this and/or migrate this issue to our cookbook repo?

> Looks good. I tested the change and tried to replicate the issue #818 with the uxarray.UxDataArray.Indexes disappearing but had no problems. > > However, given this fix, I can...

@ahijevyc When remapping, should the coordinates from the original data array be dropped? It wouldn't make much sense to preserve them (unless I'm understanding it wrong), since the coordinates from...

> The _spatial_ coordinates should not be transferred, but if there are _non-spatial_ coordinates like `time`, `ensemble_member`, or `forecast_hour`, then those should be transferred to the destination. I think that's...

Following up on this. The minimum required variables needed to work with UXarray would be the following: * Attitude and Longitude of Corner Nodes * Face-Node connectivity (i.e. the indices...

> The general issue of requiring grid information included in each history file has been discussed here since before the issue was created Yeah, having every history file contain the...

> As @gold2718 mentioned we have discussed adding history file metadata containing the inputdata path to the ESMF mesh file corresponding to the ATM grid you are running. This is...