Philip Chmielowiec

> In fact, a bigger and a fundamental issue to me is that the whole uxarray and routines assume the lat and long geographical coordinate system. I wish uxarray eventually...

@kjnam In addition to projections, supporting different coordinate systems (like how GeoPandas does) could also be of value. https://geopandas.org/en/stable/docs/reference/api/geopandas.GeoSeries.crs.html

@kafitzgerald > @philipc2, I think you're on the right track with "x" and "y", but I don't know enough about the internals of UXarray to know if overloading node_x and...

I'd like to mention that many of our algorithms are written assuming that we are working with spherical geometry, which typically involves us using normalized Cartesian (x, y, z) coordinates...

For the MPAS grids above, here is the rough size of each array (with `n_max_face_nodes=10`) ## Cartesian | Resolution | FP64 Values | Size (GB) | |------------|----------------|------------| | 30km |...

> Sorry for repeatedly asking this type of questions, but I thought grid loading was made much better than this recently (regarding ~114 seconds for 3.75 km grid for instance)....

@erogluorhan This is a better representation of the Grid load times. | Resolution | Nodes | Faces | Edges | Grid Load Time (Eager) | Grid Load Time (Dask) |...

I shared an initial Parallel Numba implementation (which I still need to fully revise to match the current implementation as @hongyuchen1030 pointed out) in #1180. These are the results for...

https://doc.cgal.org/latest/Arrangement_on_surface_2/index.html#aos_ssec-basic-dcell

Here are timings for the `face_face_connectivity` construction. | Resolution | Nodes | Faces | Edges | face_face | |------------|-----------|-----------|-------------------------------|-----------| | 30km | 1,310,720 | 655,362 | 1,966,080 | 14.81s |...