Edzer Pebesma

Thanks - this needs a bit more time to fix.

Please define "grain" and "spatial heterogeneity". How about computing the sample variogram of your simulated variables?

That would definitely ease the adoption by people from the modelling communities who use udunits2. Note however that units and calendars have a difficult relationship, [here](https://www.unidata.ucar.edu/software/udunits/udunits-2.0.4/udunits2lib.html) you will read: "_CAUTION:...

Cc @rsbivand @paleolimbot

I would advice against recommending a CRS that defines axis order in the opposite way they actually are, as `EPSG:4326` does: it preserves the bad habit of using a standard...

You are right. I was looking at the output of `OGRSpatialReference::exportToWkt(..., "FORMAT=WKT2")` , which seems to skip the ensemble info given by `projinfo`, but gives ``` GEOGCRS["WGS 84", DATUM["World Geodetic...

I think that for a user (or software writer) it is most useful if a file at least reveals whether coordinates are geographic or Cartesian, because it matters for computing...

> Does https://github.com/opengeospatial/geoparquet/blob/main/format-specs/geoparquet.md#edges handle this? Or is this something slightly different? It's related, but slightly different: if you'd convert a GeoJSON to a geoparquet file, it would have geographical coordinates...

> which is to say, please write CRS except if it is OGC:CRS84 > Yes, this would make the world a nicer place. It takes away the ambiguity for missing...

@r-barnes it seems that the upstream memory issues have been solved: https://github.com/sahrk/DGGRID/issues/24 - have you tried updating & resubmitting this package to CRAN?