Artifact Types

Artifacts are typed. The type determines what executors can accept them and what they contain.

Type reference

Type	Description	Produced by	Consumed by
las	LAS or LAZ point cloud file	REPROJECT_LAS, REGRID_LAS, COLORIZE_AS_DEM, COLORIZE_FROM_TIF, BUILD_COPC	BUILD_COPC, BUILD_EPT, BUILD_POTREE, REPROJECT_LAS, REGRID_LAS, COLORIZE_AS_DEM, COLORIZE_FROM_TIF, DATASET_INFO
ept	Entwine Point Tile directory	BUILD_EPT	(web viewers, not pipeline steps)
potree	Potree tileset directory	BUILD_POTREE	(Potree viewers, not pipeline steps)
tif	GeoTIFF raster file	(external input only)	COLORIZE_FROM_TIF
json	JSON file	DATASET_INFO	(external consumption via webhook)

Note: BUILD_COPC produces output_copc with type las because COPC is a LAS-compatible format (.copc.laz file).

Type enforcement

Ordo enforces artifact types through the executor contract system. If a step's accepts slot requires las and you wire a tif artifact to it, recipe validation fails with a slot mismatch error.

External inputs

Artifacts provided in the job inputs map can have any of the registered types. For standard MapPrism pipelines, the input is always las:

"inputs": {
  "job:input_las": {
    "type": "las",
    "uri": "development/survey/dataset.las",
    "hash": "abc123"
  }
}

For COLORIZE_FROM_TIF pipelines, you also provide a tif:

"inputs": {
  "job:input_las": {
    "type": "las",
    "uri": "development/survey/dataset.las",
    "hash": "abc123"
  },
  "job:input_tif": {
    "type": "tif",
    "uri": "development/survey/orthophoto.tif",
    "hash": "def456"
  }
}