Start here

Tip

New to EncDotNet.S100? Choose one path below and get a visible result in minutes.

Why it matters

The project has strong technical depth across multiple S-100 products and pipelines. This page gives you a focused on-ramp so you can get to value faster.

Quick win

Use the Viewer: Download a release, open a dataset, pan and inspect.
Integrate the Library: install EncDotNet.S100 and render your first PNG in a few lines.
Contribute to the Engine: run the test suite, pick a subsystem, and make a focused improvement.

Deep dive

Path 1: Use the Viewer

Best for chart analysts, QA, pilots, and domain experts.

Start with: Getting started
Then: Viewer guide
Next: MCP server guide for AI-assisted workflows

Path 2: Integrate the Library

Best for .NET developers embedding S-100 reading/rendering.

Start with: Getting started
Then: Loading datasets — files, folders, ZIPs, exchange sets and S-101 updates
Then: Reading product data — each product's features, typed models, coverage grids and time series
For encrypted ENCs: Reading protected exchange sets
For your own symbology or QA checks: Custom catalogues and validation
For interactive maps: Embedding the renderer
Reference: Top APIs

Path 3: Contribute to the Engine

Best for contributors improving datasets, pipelines, and renderers.

Architecture at a glance

flowchart LR
  A[Dataset files\nISO8211 / HDF5 / GML] --> B[Dataset readers\nS101/S102/S104/...]
  B --> C[Portrayal pipeline\nLua or XSLT]
  C --> D[Drawing instructions / coverage styles]
  D --> E[Renderers\nSkia / Mapsui]
  E --> F[Viewer / CLI / Library output]

Troubleshooting

Important

Common first-run issue: dataset format mismatch. .000/ISO8211, .h5/HDF5, and .gml have different readers and feature sets.

Warning

For EPSG:4326 GML coordinates, follow S-100 Part 10b ordering (lat lon) when validating source data and debugging geometry placement.

Next step

Continue with Getting started
Jump into scenarios:

Table of Contents