Rafael Schouten

FYI you can probably just do `Raster(multifile)` and `RasterStack(multifile)` now that those constructors on AbstractDataset are merged.

Thats actually not the worst error to see, we simply need to get the trait for GRIB from the inner dataset. I'm guessing it cant hold mixed dataset types?

Yeah it can still work without coordinates, we know Lat and Lon are connected to values and are standard Lattitude and longitude, while there is no values variable

So it's a Point Geometry lookup (And I guess a 3d xy scatter over time)

I'm working on improving our CF compatability, this file should be able to load with a `MergedLookup` (basically points) for the `values` dimension that you can select directly with X...

Hmm nothing was designed for that possibility but I guess it could work? Often it's feature properties will win because `isfeature` is checked first. I guess that's an issue: packages...

I think we should instead deprecate GeoInterface methods like area. Using LibGEOS and GeometryOps methods directly is simpler and works on all objects without confusion over what package is doing...

read/write is a good example! It's basically the same problem. So we're talking about an "interface" where package specific functions have an identical definition following a specification, rather than methods...