Riverscape Project Collections #220
-
The ProblemThis problem has been discussed in the context of "project references" but is best summed up nicely in this logical question from Steve Bennett:
We have kept riverscape projects at "manageable" sizes (and I think are leaning towards doing more of this) mainly governed by download size (i.e. < 1.5 GB). I like the idea of projects being smaller unit chunks and they themselves repeat. However the idea of a Project Collection might be worth exploring: Examples Include
I think this is a different idea than a project reference. I think in a project reference, you bring across the one (or more) key layers that project needs as a depenency (e.g. A DEM) and typically as an input, and just mention that it came from this project if they want to dig deeper. This, by contrast, is just the original projects, and then a Collector project, that just opens up their own project business logic in Nodes underneath that collection. It is not a copy. It is the original project. Just a way of orgnizing them. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
@MattReimer thought you'd get a kick out of this. I think your Warehouse 2.0 captures this nicely: https://docs.google.com/document/d/16njoqtsvAMyHkl2APtyYI2kLydoqbEpV9n9PF03i2is/edit#heading=h.d2luccrd3eev |
Beta Was this translation helpful? Give feedback.
@MattReimer thought you'd get a kick out of this. I think your Warehouse 2.0 captures this nicely: https://docs.google.com/document/d/16njoqtsvAMyHkl2APtyYI2kLydoqbEpV9n9PF03i2is/edit#heading=h.d2luccrd3eev