Open jsta opened 3 years ago
Thanks a lot @jsta for these very useful comments. It would be great if you could transform them into direct edits and submit a pull request, especially as direct contributions to the primary document are something we are very actively wanting to encourage and cultivate. A few responses from my side to help ensure we're seeing things the same way, beginning with the following comments of yours with which i entirely agree and ask you to formulate something specific via pull request:
Z
dimensionEPSG
codes as alternative to PROJ4
stringsunits
package: by "not using" is meant that a package need not Import
, Depend
or directly use routines from the units
package, but merely that input data with components in classes defined by this package should be accepted. Any clarifications of that also appreciated!Responses to other comments:
netCDF
is perhaps a bit too specific. That's only likely to be relevant to a very small portion of the spatial community in general, and so better handled directly somewhere like the tidync
package.Looking forward to some more direct input from you - please feel free to continue the discussion there. Thank you! (You can also close this issue once you've - hopefully! - proceeded on over to a pull request.)
General comments
Overall this looks like a great section of the book! Happy to submit a PR (or two) if I get a thumbs up.
Things I felt were missing
Specific comments
6.8.2.1 Spatial Scales and Units / SP2.10 Spatial software should accept inputs defined via the units package.
units
package but to accept units defined by it? As a package author, I wouldn't know how to comply.6.8.3 Algorithms