Interface HonuaOgcProcessJobAccepted

Outcome of POST /processes/{id}/execution.

The same envelope carries both Core response shapes so one typed surface covers a raw third-party server and the Honua facade:

  • asynchronous — jobID names the created job and synchronous is false.
  • synchronous — the server answered 200 with the results document inline. jobID is "" (Core assigns no job identifier to a synchronous execution), status is "successful", synchronous is true, and results holds the document.
interface HonuaOgcProcessJobAccepted {
    jobID: string;
    links?: HonuaOgcLink[];
    processID?: string;
    results?: HonuaOgcProcessJobResults;
    status: OgcProcessStatus;
    statusInfo?: HonuaOgcProcessJobStatus;
    statusPath?: string;
    synchronous?: boolean;
}

Properties

jobID: string

Server-assigned job id; "" for a synchronous execution (no job exists).

links?: HonuaOgcLink[]
processID?: string

Results document, populated only when synchronous is true.

Initial (often accepted or running) status payload, when reported.

statusPath?: string

Same-origin request path derived from the async Location header (or the accepted document's self link). Polling follows it instead of templating {basePath}/jobs/{jobId}.

synchronous?: boolean

true when the server answered inline with the results document.