-
-
Notifications
You must be signed in to change notification settings - Fork 589
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updates to c5 #698
Updates to c5 #698
Conversation
Fix #695 Thanks to rspatial/terra#450
Heads-up @Nowosad this is good to go. Looking at it, it's a long chapter. I think that splitting out the raster-vector interactions content into a new dedicated chapter could represent a quick win, it's a long chapter and the topic is so important as to merit it's own chapter IMO atm. |
@Robinlovelace Yes -- I think that is a good idea. What do you think @jannes-m ? |
Good stuff, I've created a new issue #706 on the topic. Will merge this now to keep things moving. |
Aside from reducing the length of chapter 5, it would be sensible to split out the raster-vector stuff into a new chapter simply because extracting values from a raster is not changing the geometry of an spatial object (and therefore strictly speaking it does not belong to c5) and because raster-vector operations are somehow special in any case. |
Thanks for the comment Jannes, sounds like there's consensus! |
No description provided.