Closed defuneste closed 1 year ago
The rayshader library uses this line to download data in their usage section:
download.file("https://tylermw.com/data/dem_01.tif.zip", loadzip)
Does this answer question 1?
Does this answer question 1?
Yes! Thanks @geographyclub for pointing that out ! This give us more option. We will probably have to ask Tyler if we use it.
Reading issue #560 it appears you wanted to contribute but didn't know how to use git. Well, I do not think you need to understand git at first we can just discuss in the issue section (is it fine @Robinlovelace ?). You can use {reprex} (https://reprex.tidyverse.org/) or just use the github markdown. Geocompr also have a discord if you prefer and we can start a thread here also.
One stuff that make Geocompr good is that it go deeper than a "tutorial" and provide both concept and code. I think we have to also go for that with {rayshader}. Sadly my level is not even that of a tutorial (but it can only improve :P).
On the topic of cesium I am also interested and I think it could be nice too. Should we open an other issue?
Should we open an other issue?
Not yet is my thinking. Issues are most effective when they are actionable and, to my knowledge, there is no mature R interface to Cesium. This issue is actionable now and {rayshader} is mature.
Superseded by https://github.com/Robinlovelace/geocompr/issues/882
Do you think it is a good idea to add a part in chap 09 Making maps with R about 3D mapping ?
I am thinking about rayshader but maybe other options should be or could be considered.
If the answer is yes then that brings to more questions:
What kind of data are we using and how can a reader access it? The minimum needed is a DEM but some satellite imagery can also be used.
How deep should we go in displaying uses of this package ? It can range to just mentioning it, to providing one or more reproducible examples.