EncDotNet.S100.Datasets.S131 0.16.0

EncDotNet.S100.Datasets.S131

Reader and Lua portrayal pipeline for IHO S-131 Marine Harbour Infrastructure datasets (GML encoding, S-100 Part 10b).

Specification editions

Screenshot

S-131 Halifax Harbour sample rendered in the S-100 Viewer:

Architecture — GML + Lua hybrid

S-131 is unique in this codebase: it combines GML data encoding (like S-122, S-124, S-125, S-127, S-128, S-411, S-421) with Lua portrayal (like S-101). All other GML products use XSLT portrayal; all other Lua products use ISO 8211 or HDF5 encoding. S-131 is the first GML+Lua hybrid.

The bridge architecture:

S-131 GML → S131DatasetReader → S131Dataset
                                    ↓
                             S131LuaDataProvider (GML→Lua Host API)
                                    ↓
                             S131LuaRuleExecutor (MoonSharp Lua 5.2)
                                    ↓
                             DrawingInstructionParser (reused from S-101)
                                    ↓
                             VectorPipeline → MapsuiDisplayListRenderer

Key design decisions

• Custom S131DatasetProcessor: Does not extend GmlDatasetProcessorBase (which hardwires XSLT). Instead follows the S101DatasetProcessor pattern with Lua infrastructure.
• Numeric ID mapping: GML string IDs (gml:id) are mapped to sequential numeric IDs for the Lua Host API contract.
• Synthetic spatial records: GML embeds geometry inline; the data provider synthesizes spatial association structures compatible with S-101's HostGetSpatialData contract.
• FC-driven discrimination: Feature vs. information type classification uses a set of known information type codes from the Feature Catalogue, handling S-131's unified <S131:members> container (no <member>/<imember> split).

GML shape

<S131:Dataset xmlns:S131="http://www.iho.int/S131/1.0"
              xmlns:S100="http://www.iho.int/s100gml/5.0">
  <S131:members>
    
    <S131:Berth gml:id="f1">...</S131:Berth>
    <S131:ContactDetails gml:id="info1">...</S131:ContactDetails>
  </S131:members>
</S131:Dataset>

Public API

Typed DataModel

The EncDotNet.S100.Datasets.S131.DataModel namespace provides a "Pass 2" strongly-typed projection layered on top of the raw S131Dataset graph, following the same pattern used by the other GML-encoded products (S-122 / S-124 / S-125 / S-127 / S-128 / S-129 / S-201 / S-411 / S-421). The projection is independent of portrayal — the Lua pipeline continues to consume the raw feature graph unchanged.

Entry point

var raw = S131Dataset.Open("dataset.gml");
var typed = S131HarbourInfrastructureDataset.From(raw, out var diagnostics);

foreach (var berth in typed.LayoutFeatures.Where(l => l.Kind == S131LayoutKind.Berth))
    Console.WriteLine($"{berth.Id}: {berth.Geometry.Points.FirstOrDefault()}");

foreach (var authority in typed.Authorities)
    Console.WriteLine($"{authority.Id} → contact={authority.ContactDetails?.Id}");

Family hierarchy

Concrete feature types are grouped into four families derived statically from the FC supertype graph (FC Ed 1.0.0 §B.2 / §B.5). The projection does not walk the FC at runtime — schema introspection remains the job of the Feature Catalogue reader.

Information-type hierarchy

Information types in S-131 never carry geometry; the S131Authority shortcuts (ContactDetails, Applicability) are typed for the common Authority-binding pattern.

Geometry

S131Geometry wraps the four parallel coordinate collections on S131Feature into a single record with GeometryType (None, Point, Curve, Surface). Coordinates are GeoPosition(Latitude, Longitude) in decimal degrees per S-100 Part 10b §6.2.

Cross-references

xlink:href references on role-bearing child elements (e.g. <S131:applicability xlink:href="#info1"/>) are resolved into S131ResolvedReference { Role, TargetRef, Target } entries on the ResolvedReferences property of both features and information types. Unresolved references carry a null Target plus a paired xlink.unresolved / s131.reference.dangling diagnostic.

Diagnostic codes

The projection reports issues via ProjectionDiagnostic rather than throwing (the only fatal condition is an empty source dataset):

Feature Catalogue note

The typed enum lists are derived from the standalone FC at content/S131/fc/FeatureCatalogue.xml (FC Ed 1.0.0). The PC-bundled FC at content/S131/pc/.../131_FC_2.0.0.20251025.xml may contain additional codes — any divergence surfaces as s131.feature.unknown / s131.information.unknown diagnostics, and the affected objects still project cleanly as S131OtherFeature / S131OtherInformationType. The projection has no runtime FC dependency.

Usage

// Parse a dataset
var dataset = S131Dataset.Open("path/to/dataset.gml");

// Or from a stream
using var stream = File.OpenRead("dataset.gml");
var dataset = S131Dataset.Open(stream);

// Access features
foreach (var feature in dataset.Features)
{
    Console.WriteLine($"{feature.FeatureType}: {feature.Id}");
}

Validation

S131HarbourInfrastructureRules.Default is a pilot rule set of Tier-1/Tier-2 checks that run against a typed S131HarbourInfrastructureDataset. Each rule's ID traces to an S-131 or S-100 spec clause.

var typed = S131HarbourInfrastructureDataset.From(dataset, out _);
var report = S131HarbourInfrastructureRules.Validate(typed);
foreach (var f in report.Findings)
    Console.WriteLine($"[{f.Severity}] {f.RuleId}: {f.Message}");

Tier-3 cross-dataset rules (e.g. cross-checking Berth depths against a loaded S-102 bathymetric surface) are out of scope here; they would reach sibling datasets via ValidationContext.Services.

Dependencies

• EncDotNet.S100.Core — GML abstractions, pipeline interfaces
• EncDotNet.S100.Datasets.S101 — DrawingInstructionParser reuse
• EncDotNet.S100.Features — Feature Catalogue decoder
• EncDotNet.S100.Portrayals — Portrayal Catalogue types