@tcstewar has very explicitly said that his data logging tool ("ccmsuite": https://github.com/tcstewar/ccmsuite) has served him well in his 10 years logging two kinds of data: "continuous" (ie floating point) time serieses, single-summary statistics, and discrete events.
We are very interested in aping [http://corridordesign.org/](these folks). For example, we want to see deer corridors, or butterfly corridors, or pine tree corridors all arise naturally out of our model, and we want to be able to see their development over time. Yes, we could tree this all as a large number (per-pixel) of individual time series, but it seems like there is some spatially-explicit code framework out to be written.
@tcstewar has very explicitly said that his data logging tool ("ccmsuite": https://github.com/tcstewar/ccmsuite) has served him well in his 10 years logging two kinds of data: "continuous" (ie floating point) time serieses, single-summary statistics, and discrete events.
We are very interested in aping [http://corridordesign.org/](these folks). For example, we want to see deer corridors, or butterfly corridors, or pine tree corridors all arise naturally out of our model, and we want to be able to see their development over time. Yes, we could tree this all as a large number (per-pixel) of individual time series, but it seems like there is some spatially-explicit code framework out to be written.