-
Notifications
You must be signed in to change notification settings - Fork 19
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Define the pipeline & decide ecosystem #237
Comments
(draft - feel free to edit)
|
The more I look at this, the more I think we should use SpineToolbox to integrate everything and the EDR as just one of several data sources. And maybe also be able to put results back into ESDL to share results with other models and use the MapEditor etc for analysis (depending on squeeze-to-juice ratio). Mostly when looking at the SpineToolbox column - it really highlights that SpineToolbox is an integrator. Really, all of these pieces are different tools that have just a bit of overlap. We should decide where the interfaces are. What I'm a bit concerned about is the whole system still working in 5 years. Seems a bit complex. |
Assigned myself although this is a group effort. |
Discussion: |
WHAT WE WANT
|
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Description
What do we need from Toolbox/ESDL and what's our pipeline going to be?
Related Issues
Blocking #94, #106, #105, #118, #88, #89, #115, #36
The text was updated successfully, but these errors were encountered: