Pipeline triggering
There are multiple ways pipelines can be triggered via the API.
Available pipeline retrieval
Available pipelines can be requested by using the below graphql for a specific grouped asset
query {
availableProcessingPipelines(groupedAssetId: "40b18de4-7749-45a6-a129-dbc9b1850df9") {
outputFormat
processingPipelineName
}
}
Response:
{
"data": {
"availableProcessingPipelines": [
{
"outputFormat": "LAS",
"processingPipelineName": "MYVR_HSPC_TO_LAS"
},
{
"outputFormat": "PTS",
"processingPipelineName": "MYVR_HSPC_TO_PTS"
},
{
"outputFormat": "E57",
"processingPipelineName": "MYVR_HSPC_TO_E57"
},
{
"outputFormat": "BINARY_MAP",
"processingPipelineName": "IMMERSAL_COARSE_REGISTRATION_TO_VISUAL_MAP"
}
]
}
}
Triggering export pipeline manually
With the above information available it is possible to trigger a pipeline for the given grouped asset:
mutation {
triggerProcessingV2(
params: {
groupedAssetId: "9cb8853f-2ca6-47fe-942e-8846dc57dc2f"
outputFormat: E57
processingPipelineName: MYVR_HSPC_TO_E57
}
) {
... on TriggerProcessingOutput {
success
}
}
}
Response:
{
"data": {
"triggerProcessingV2": {
"success": true
}
}
}
Meshing pipeline trigger
To trigger the meshing pipeline( converting HSPC to OGC3DTILES, with the additional downloadable OBJ) the below mutation can be used:
mutation {
triggerMeshingV2(
params: {
groupedAssetId: "[GROUPED_ASSET_ID]"
scanningDeviceType: RTC360 #The type of device used for scanning the asset
}
) {
... on TriggerProcessingOutput {
success
}
}
}
Response:
{
"data": {
"triggerMeshingV2": {
"success": true
}
}
}
JS-SDK reference
Pipelines
HxDR Pipelines