Closed dschwilk closed 7 years ago
OK, on second thought, since we want raster maps at the end anyway, I guess I'll leave the raster code, but we still need to put all the plot data in one dataframe for modeling. I will not introduce a new dependency by using fuzzyjoin.
Totally. Just wanted you to hey my baby steps.
On Aug 4, 2017, at 3:48 PM, Dylan Schwilk notifications@github.com wrote:
We have a lot of code and computation devoted to splitting up our climate data into separate variables, then re-assembling as a raster stack, then extracting just plot locations. This is overkill for what is essentially a simple merge or join. I suggest we replace all of that code with geo_join() from the fuzzy_join package. This will make it much easier to combine data from all three mtn ranges for species distribution models.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
We have a lot of code and computation devoted to splitting up our climate data into separate variables, then re-assembling as a raster stack, then extracting just plot locations. This is overkill for what is essentially a simple merge or join. I suggest we replace all of that code with geo_join() from the fuzzy_join package. This will make it much easier to combine data from all three mtn ranges for species distribution models.