Honua.Sdk.Abstractions 1.13.1

Honua.Sdk.Abstractions

Shared, provider-neutral contracts used across the Honua .NET SDK. Defines the core feature interfaces (IHonuaFeatureQueryClient, IHonuaFeatureEditClient, IHonuaFeatureAttachmentClient, IHonuaFeatureDescriptorClient, IHonuaSource, SourceDescriptor), the unified IHonuaFeatureGateway / HonuaFeatureGateway that route attachments and temporal / grouped-statistics queries to a capable provider (so a geoprocessing tool reaching media or time-aware queries over gRPC never hits NotSupportedException), feature query/edit request and result models, feature stream-event processors, the provider-neutral routing client (IHonuaRoutingClient) and routing models, scene client and scene-package contracts, Studio analysis-report and analysis-result-package DTOs, utility-network trace contracts, plugin contracts, and HonuaException.

Also ships browser-safe Honua Console contracts under Honua.Sdk.Abstractions.Console and Honua.Sdk.Abstractions.Environments: shell descriptors, route guards, permission grants, environment profiles, transport capabilities, and native mTLS trust-state DTOs. These models are selectors and status envelopes only; host apps own persistence, secure storage, certificate lookup, and platform trust validation.

Also ships the Studio report contracts under Honua.Sdk.Abstractions.Studio: HonuaAnalysisReport, the kind-discriminated HonuaAnalysisReportSection hierarchy, HonuaRenderedReport, and HonuaAnalysisResultPackage projections. The transport client that reads and renders reports lives in Honua.Sdk.Studio.

Also ships the offline sync contracts under the Honua.Sdk.Offline.Abstractions.* namespaces: OfflineReplicaManifest, OfflinePackageManifest, OfflineSyncState, OfflineSyncCheckpoint, OfflineChangeJournalEntry, conflict envelopes, push/pull result records, the IOfflineFeatureStore / IOfflineChangeJournal / IOfflineConflictStore / IOfflineSyncCheckpointStore / IOfflineSyncStateStore / IOfflineSyncRunner storage interfaces, and IReplicaSyncClient.

This package does not ship a server client. Take a dependency on it from a library to write code that targets multiple Honua protocols (FeatureServer, gRPC, WFS, OGC API Features, etc.) through a single set of interfaces; concrete implementations live in the protocol-specific packages.

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.Abstractions

In a library .csproj:

<ItemGroup>
  <PackageReference Include="Honua.Sdk.Abstractions" Version="1.13.1" /> 
</ItemGroup>

Quick usage

using Honua.Sdk.Abstractions.Features;

public sealed class FeatureExporter(IHonuaFeatureQueryClient client)
{
    public async Task<int> CountAsync(SourceDescriptor source, CancellationToken cancellationToken)
    {
        var request = new FeatureQueryRequest
        {
            Source = source,
            Where = "1=1",
            ReturnGeometry = false,
        };

        var total = 0;
        await foreach (var page in client.QueryPagesAsync(request, cancellationToken))
        {
            total += page.Features.Count;
        }
        return total;
    }
}

A concrete provider package (for example Honua.Sdk.GeoServices or Honua.Sdk.Grpc) registers an IHonuaFeatureQueryClient implementation in DI; your library code stays provider-neutral.

Observability

SDK clients do not emit their own distributed-tracing spans uniformly; instead, observability is delegated to the underlying transports, which are already instrumented:

• REST clients flow through HttpClient. Enable AddHttpClientInstrumentation() (OpenTelemetry) — or the System.Net.Http EventSource/DiagnosticSource — to capture per-request spans, status codes, and timings for every Honua.Sdk.* REST client.
• gRPC client flows through Grpc.Net.Client; enable AddGrpcClientInstrumentation() for gRPC call spans.

The resilience pipeline (Microsoft.Extensions.Http.Resilience / Polly) also emits telemetry for retries, timeouts, and circuit-breaker transitions. A few clients add finer-grained SDK-level spans on top of this (e.g. the WFS client); these are additive and not required for baseline tracing.

Documentation

• Quickstart
• Authentication
• Troubleshooting
• Source facade
• Console client contracts
• Plugin contracts

License

Apache 2.0