Moving Code

About

What is Moving Code?

Moving Code is both a paradigm and a software framework to enable running processes in a variety of environments. Moving code allows you to process data across runtime environments and to share processing functionality in a standardized yet simple way.

How does it work?

The basic unit of Moving Code is the Moving Code package. It contains a description file and all the required instructions to execute a programme, which is described in more detail below.

packagedescription.xml

A package description contains everything one needs to know to execute a process: information about the required infrastructure, software, rights of usage, and pratical files needed.

The most recent version of the schema is available in the SVN: https://svn.52north.org/svn/geoprocessing/main/movingcode-schema/trunk/src/main/xsd/

Research

The concepts behind Moving Code are developed mostly by Matthias Müller from TU Dresden. Take a look at his publications if you are interested in the details! Some examples/direct links:

• Moving code – Sharing geoprocessing logic on the Web > http://www.sciencedirect.com/science/article/pii/S0924271613000543
• http://agile.gis.geo.tu-dresden.de/web/Conference_Paper/CDs/AGILE%202012/proceedings/papers/Paper_Mueller_Moving_Code-Sharing_Geospatial_Computation_Logic_on_the_Web_2012.pdf

User Documentation

Take a look at the MovingCodeQuickIntro to understand the moving code software and try to run your process in a 52nWPS.

Contributor Documentation

Want to programme? Take a look at the MovingCodeDevelopmentBacklog to find tasks and goals/roadmap. General development aspects are described in MovingCodeDevelopment.

Modules

• 52n-mc-parent
  • 52n-mc-runtime
  • 52n-mc-xml-processors
• movingcode-schema

Prozessors

• PythonCLIProcessor
• JavaJARProcessor
• RCLIProcessor

Stage names taken

• MC Runtime
• MC Schema
• MC Python
• MC Octave
• MC Arrrr
• MC GECA

Metadata

• Topic created by: DanielNuest
• Topic created on: 2013-03-19