Bring intersectr netcdf traversal for unstructured grids into climateR. about climater HOT 5 CLOSED

I'm fine with it. intersectr (now ncdfgeom) also works on totally irregular stuff like polygons, so that's a nice to have.

from climater.

Hi @dblodgett-usgs, I would like to reopen this discussion now that this package is much more stable and easy to maintain. To date, the entirety of the climateR-catalog built here is used in this package and a lot of general tooling around reading NetCDF/VRT/TIF/OPeNDAP resources lives here. I am debating whether to bring zonal over here as well and your thoughts on that and intersectr would be really appreciated.

from climater.

I did bring a couple of the key pieces of intersectr into ncdfgeom in DOI-USGS/ncdfgeom#80

Just glancing at the call stack that leads to your read_dap_file function, I'm not quite sure how you would shoe horn the pattern I have in here (or if it would add anything to what you have?)

I get the indices for my total request here: https://github.com/DOI-USGS/intersectr/blob/main/R/execute_intersection.R#L100

Then call this for each time step: https://github.com/DOI-USGS/intersectr/blob/main/R/execute_intersection.R#L331

The rest of the execute_intersection logic is more or less already in here?

I just noticed this is declared twice... https://github.com/mikejohnson51/climateR/blob/master/R/utils.R#L272

from climater.

What are your thoughts on bringing zonal's regular grid functions over here mixed with intersectr logic for curvilinear grids?

from climater.

Will reopen latter when we have a strategy :)

from climater.