Should we keep all the Exercises at the end of the chapters for consistency, or add additional Exercises before the end? (Latest thinking: have a main Excercises section at the end of each chapter but include some exercises mid-chapter where appropriate.)
How should we handle units? At present we describe them briefly in the context of simple features in Section 2.4 and then again in exercises 3.7 but we were wondering if a more systematic coverage of this potentially tricky topic is needed
Likewise for CRSs - we introduce them in 2.3 but plan a larger section, going into more detail about how to select and modify them, in Chapter 6. Sound good?
At present we have tried to keep vector and raster data relatively well-integrated. However, there has been discussion of splitting-out some of the raster stuff (see github discussion) in the context of matrix algebra, which blurs the boundary between spatial and non-spatial operations. Any thoughts on this?
We'd also appreciate feedback on the book's structure. Our thinking has evolved as we've written the first fie chapters and, as documented in our_chapters.md, the latest plan is to have 4 parts of the basic format methods1 -> applications1 -> methods2 -> applications2. Whether these Parts are formal in the index (like in R for Data Science) or just used for our own benefit is an open question (we're not in any rush to formalise them) but any comments on the book's structure would be appreciated. The thinking is that 'getting stuck in' with practical examples asap after the foundations have been learned will be fun and conducive to learning, so readers don't get bored before the more advanced methods sections.
We would like to know if you think that there is a need for a chapter on cloud computing/big data in a geocomputation context?