processExecution.json

{
   "id" : "Contours250",
   "process" : "ElevationContours",
   "inputs" : [
      { "collection" : "vtp/Daraa2/Daraa_DTED" }
   ],
   "parameters" : { "distance" : 250 }
}

processExecution2.json

{
   "id" : "ContoursAndRoadsMap",
   "process" : "RenderMap",
   "inputs" : [
      {
         "id" : "Contours250",
         "process" : "ElevationContours",
         "inputs" : [
            { "collection" : "vtp/Daraa2/Daraa_DTED" }
         ],
         "parameters" : { "distance" : 250 }
      },
      { "collection" : "vtp/Daraa2/TransportationGroundCrv" }
   ],
   "parameters" : { "style" : "night" }
}

processExecution3.json

{
   "id" : "ContoursRoadsAndRouteMap",
   "process" : "RenderMap",
   "inputs" : [
      {
         "id" : "Contours250",
         "process" : "ElevationContours",
         "inputs" : [
            { "collection" : "vtp/Daraa2/Daraa_DTED" }
         ],
         "parameters" : { "distance" : 250 }
      },
      { "collection" : "vtp/Daraa2/TransportationGroundCrv" },
      {
         "id" : "MyRoute",
         "process" : "OSMEcereRoutingEngine",
         "inputs" : [ { "collection" : "vtp/Daraa2/TransportationGroundCrv" } ],
         "parameters" :
         {
            "waypoints": {
               "type": "MultiPoint",
               "coordinates": [
                  [-77.0196532723585, 38.8205846067614],
                  [-77.0862070084951, 38.9443670022042]
               ]
            }
         }           
      }
   ],
   "parameters" : { "style" : "night" }
}

Usage Examples

- POST to /collections
  - Create a new virtual collection (usable like a regular collection, can be features, imagery or coverage depending on what the process execution generation)

- POST to the process directly
  - e.g. /processes/ElevationContours, /processes/OSMEcereRoutingEngine, /processes/RenderMap aka /map) itself
  - In this case the top-level "process" is redundant and not necessary, 
  - Get the output right away (e.g. GeoJSON, GeoTIFF or PNG of the full extent, or specify a BBOX, width & height)
  - Async options

- POST to the process directly, but with Tiles support
  - e.g. /map/tiles, /processes/ElevationContours/tiles,
  - In this case the top-level "process" is redundant and not necessary
  - Get a tiles template & tileMatrixLink back, if you include TileMatrixSet in request you only get TMS link for that one
  - The link is not made public to anyone else, but the server can cache, and it can give the same link to someone else asking for the same tiles 
  
- POST to /tiles
  - In this case the process identified is useful
  - Get a tiles template & tileMatrixLink back, if you include TileMatrixSet in request you only get TMS link for that one
  - The link is not made public to anyone else, but the server can cache, and it can give the same link to someone else asking for the same tiles 

- Retrieve process invocation description from virtual collection
  - e.g. GET /collections/ContoursRoadsAndRouteMap/sourceExecution