We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Working with big spatial data workflows (or, what would John Snow do?)

Formale Metadaten

Titel
Working with big spatial data workflows (or, what would John Snow do?)
Serientitel
Anzahl der Teile
12
Autor
Lizenz
CC-Namensnennung - keine kommerzielle Nutzung - keine Bearbeitung 4.0 International:
Sie dürfen das Werk bzw. den Inhalt in unveränderter Form zu jedem legalen und nicht-kommerziellen Zweck nutzen, vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen.
Identifikatoren
Herausgeber
Erscheinungsjahr
Sprache

Inhaltliche Metadaten

Fachgebiet
Genre
Abstract
In situations where we have to handle big spatial data, I wonder: What would John Snow do? He would like us to use the proper FOSS4G tools. Most of our software is fueled by data. But when we deal with big spatial data, we have to deal with different data sources, formats, protocols,… that have to be processed at a speed we can’t handle manually. All of those are tedious and repetitive tasks that make developers quickly jump into scripting rough code, reinventing the wheel. Also, on this custom code, we are coupling something that should be decoupled. Could it be possible to decouple the systems while they are connected? With Integration Processes frameworks we can make it simpler and reuse expertise from other developers. We just have to worry defining the workflow and the data mappings and our FOSS will take care of the details. If one step of our data workflow changes, we could easily upgrade our workflow definition to adapt. On this demo we will do a basic example of how to create a spatial data workflow with free and open source tools.