Mark Piper
Mark Piper
Another use case: * Perform model calculations valid at initial time step (This is a request from @sc0tts.)
Yeah, having a separate BMI for Fortran would solve this. The more I think about it, though, I think you guys did it right. The *iso_c_binding* module has been standard...
@gregtucker This PR addresses the geospatial BMI task from CSDMS 3.
The docs for the branch are active: https://bmi.readthedocs.io/en/mdpiper-get-grid-projection/
These should be enumerated, like commandments.
We could add language to the docs to the effect of > BMI doesn't specify how to flatten arrays. This is left to the implementation. @aaraney If you have suggestions...
In BMI 2.0, we implicitly assume grid dimensions are named *x*, *y*, and *z*. Not only may this be a misnomer (what if the model uses natural coordinates or geographic...
The new function would provide the *name* parameter of the suggested *get_grid_units* function in #87 and *get_grid_node_coordinates* function in #88.
One possibility for this function, suggested [here](https://github.com/csdms/bmi/issues/87#issuecomment-961445180), is: ```java int get_grid_dimension_names(in int grid, out array names); ``` It could return ["x", "y", "z"] or ["x1", "x2", "x3"] or N names...
I updated the title and description based on the comments from @hrajagers and @mcflugen.