Discover a raw (third-party) OGC API Processes service as a
capability/metadata result.
OGC API Processes is deliberately not a Source-backed protocol: a process
is an invocable operation, not a queryable dataset, so it never becomes a
connect()Source. This function is the raw-Processes counterpart to
connect() — it threads the discovered service-root path through the
Processes wire methods (the same basePath seam the Tiles / Maps / Records
adapters use), performs three bounded metadata requests (landing,
conformance, process list), and returns the advertised process list plus the
effective processes capability intersected from conformance. A service that
advertises no Processes conformance reports an empty capability set with a
structured diagnostic rather than inventing support.
Discover a raw (third-party) OGC API Processes service as a capability/metadata result.
OGC API Processes is deliberately not a Source-backed protocol: a process is an invocable operation, not a queryable dataset, so it never becomes a
connect()Source. This function is the raw-Processes counterpart toconnect()— it threads the discovered service-root path through the Processes wire methods (the samebasePathseam the Tiles / Maps / Records adapters use), performs three bounded metadata requests (landing, conformance, process list), and returns the advertised process list plus the effectiveprocessescapability intersected from conformance. A service that advertises no Processes conformance reports an empty capability set with a structured diagnostic rather than inventing support.