Honua.Sdk.Grpc 1.13.1

Honua.Sdk.Grpc

gRPC client for Honua native services. Provides typed FeatureService queries, server-side streaming for large result sets, apply-edits with spatial filters and statistics, and ProcessService job lifecycle access for native hosts.

Part of the Honua .NET SDK — see the repo README for the full package catalog, browser/WASM support, authentication, and release policy.

Install

Stable releases are on nuget.org and install anonymously. An unversioned add resolves to the newest stable release (the current SDK version is in the repo README). Prereleases stay on the authenticated GitHub Packages feed; see INSTALL.md.

dotnet add package Honua.Sdk.Grpc

Quick usage

using Honua.Sdk.Grpc;
using Honua.Sdk.Grpc.Extensions;
using Honua.Sdk.Grpc.Models;
using Microsoft.Extensions.DependencyInjection;

var services = new ServiceCollection();
services.AddHonuaGrpc(o => o.BaseAddress = new Uri("https://your-honua-server"));
using var provider = services.BuildServiceProvider();

var client = provider.GetRequiredService<IHonuaGrpcClient>();

var response = await client.QueryFeaturesAsync(
    new QueryFeaturesRequest
    {
        ServiceId = "parcels",
        LayerId = 0,
        Where = "city = 'Boulder'",
        OutFields = ["objectid", "parcel_no"],
        ResultRecordCount = 500,
    },
    cancellationToken);

await foreach (var page in client.QueryFeaturesStreamAsync(
    new QueryFeaturesRequest { ServiceId = "parcels", LayerId = 0 },
    cancellationToken))
{
    Console.WriteLine($"Page with {page.Features.Count} features");
}

Native Console and MAUI hosts can also resolve IHonuaProcessGrpcClient for the server-backed ProcessService path: validate plans, run dry runs, submit jobs, inspect job state, retrieve results, and cancel jobs while reusing the shared job models from Honua.Sdk.Processes.

using Honua.Sdk.Processes.Models;

var process = provider.GetRequiredService<IHonuaProcessGrpcClient>();

var plan = new HonuaAnalysisPlan
{
    PlanId = "plan-1",
    WorkflowFamily = "analyze",
    Outputs = ["featureLayer"],
    Steps =
    [
        new HonuaPlanStep
        {
            StepId = "buffer",
            Kind = "geoprocess",
            ProcessId = "geometry.buffer",
            Inputs = new Dictionary<string, string>
            {
                ["wkb"] = "AAAA",
                ["srid"] = "4326",
                ["distance"] = "25"
            }
        }
    ]
};

var validation = await process.ValidatePlanAsync(plan, cancellationToken);
var dryRun = await process.DryRunPlanAsync(plan, cancellationToken);
var job = await process.SubmitJobAsync(plan, cancellationToken: cancellationToken);
var status = await process.GetJobAsync(job.JobId, cancellationToken);

Console.WriteLine($"{validation.Valid}: {dryRun.Valid}: {status.Status}");

HonuaProcessGrpcClient uses the same HonuaGrpcClientOptions auth, deadline, retry, and PrimaryHttpMessageHandlerFactory behavior as the FeatureService client. Browser hosts should use Honua.Sdk.Processes REST instead of native gRPC.

HonuaProcessJobStatus.Status, HonuaProcessJobProgress.State, and HonuaProcessExecutionResult.Status are normalized to the OGC API Processes status values (accepted, running, successful, failed, dismissed) across both the REST and gRPC adapters so consumers get one contract regardless of transport.

ExecutePlanAsync and ExecutePlanStreamAsync are thin wrappers for the ProcessService proto methods. Current Honua Server deployments may return Unimplemented for those calls until synchronous execute and execute-stream support lands; use SubmitJobAsync, GetJobAsync, GetJobResultAsync, and CancelJobAsync for current server contract coverage.

DI-resolved IHonuaGrpcClient and IHonuaProcessGrpcClient instances are container-owned. Let the service provider dispose the underlying channel at shutdown; manually constructed concrete clients remain responsible for their own disposal.

Documentation

• Quickstart
• Authentication
• Console client contracts
• Troubleshooting
• Feature edits

License

Apache 2.0