Preset Pipelines

MapPrism ships with six pre-built recipe presets that cover the most common processing workflows. Each preset is a complete recipe that can be submitted directly as an inline recipe in a job request.

Note: The recipe JSON shown in each preset page is a snapshot at a specific point in time (v3.0.0). Actual recipes registered in Ordo may differ. To get the authoritative current definition, query the Ordo step_executor table or check /ordo/reference/mapprism/ in the repository.

---

Preset index

Preset	Recipe name	Reprojection	Output format
build-copc	copc-conversion	No	COPC (LAZ)
build-ept	ept-conversion	No	EPT
build-potree	potree-conversion	No	Potree
reproject-and-build-copc	reproject-copc	Yes	COPC (LAZ)
reproject-and-build-ept	reproject-ept	Yes	EPT
reproject-and-build-potree	reproject-potree	Yes	Potree

---

Choosing a preset

Use a direct preset (build-copc, build-ept, build-potree) when:

• Your dataset is already in the correct coordinate system
• You just need to convert to a web-ready format

Use a reproject-and-build preset when:

• Your dataset is in a local or survey CRS that needs normalization
• The target system expects a specific CRS (e.g. EPSG:3857 for web viewers)

Use a custom recipe when:

• You need colorization (COLORIZE_AS_DEM or COLORIZE_FROM_TIF) before tiling
• You need surface reconstruction (REGRID_LAS) for bathymetric data
• You need multiple output formats from a single job

---

Common structure

All six presets share the same structure:

• A main conversion step (BUILD_COPC, BUILD_EPT, or BUILD_POTREE)
• A DATASET_INFO step running in parallel to extract metadata
• A CALL_WEBHOOK step in on_exit that fires when the job completes

The webhook fires after DATASET_INFO completes, so the full metadata is available in the webhook payload.