EncDotNet.S100.Specifications
0.25.0
See the version list below for details.
dotnet add package EncDotNet.S100.Specifications --version 0.25.0
NuGet\Install-Package EncDotNet.S100.Specifications -Version 0.25.0
<PackageReference Include="EncDotNet.S100.Specifications" Version="0.25.0" />
<PackageVersion Include="EncDotNet.S100.Specifications" Version="0.25.0" />
<PackageReference Include="EncDotNet.S100.Specifications" />
paket add EncDotNet.S100.Specifications --version 0.25.0
#r "nuget: EncDotNet.S100.Specifications, 0.25.0"
#:package EncDotNet.S100.Specifications@0.25.0
#addin nuget:?package=EncDotNet.S100.Specifications&version=0.25.0
#tool nuget:?package=EncDotNet.S100.Specifications&version=0.25.0
EncDotNet.S100.Specifications
This package embeds the feature catalogues and portrayal catalogues for each
supported product, so an application can read and portray datasets without
asking its users to find and download catalogue files. Reference it when you
need a bundled catalogue directly, for example to start from it and override
part of it. The EncDotNet.S100 package uses it
for you.
Install
dotnet add package EncDotNet.S100.Specifications
Open a bundled catalogue
using EncDotNet.S100.Core;
using EncDotNet.S100.Specifications;
// The bundled S-111 feature catalogue XML.
await using Stream fc = await Specification.OpenFeatureCatalogueAsync("S-111");
// An asset source over the bundled S-111 portrayal catalogue.
using IAssetSource pc = Specification.CreatePortrayalCatalogueSource("S-111");
Product names can be written with or without the hyphen ("S-111" or
"S111").
Main members
All members are on the static Specification class:
| Member | Returns |
|---|---|
AvailableSpecs |
The products with bundled content: S-101, S-102, S-104, S-111, S-122, S-124, S-125, S-127, S-128, S-129, S-131, S-201, S-401, S-411 and S-421. |
AvailableSpecRefs |
The same list as SpecRefs. Their version is 0.0.0, because no manifest records the bundled edition; read the catalogue itself for its version. |
OpenFeatureCatalogueAsync(productSpec) |
The feature catalogue XML as a stream. |
TryOpenFeatureCatalogue(productSpec), TryOpenFeatureCatalogueAsync(productSpec) |
The feature catalogue XML, or null if there isn't one. |
HasFeatureCatalogue(productSpec) |
Whether a feature catalogue is bundled. |
CreateFeatureCatalogueSource(productSpec) |
An IAssetSource over the feature catalogue folder, cached in memory after the first read. Register it with FeatureCatalogueManager.SetSource. |
HasPortrayalCatalogue(productSpec) |
Whether a portrayal catalogue is bundled. |
CreatePortrayalCatalogueSource(productSpec) |
An IAssetSource over the portrayal catalogue folder, with each asset cached in memory after the first read. |
To use your own catalogues instead, see Custom catalogues and validation.
Content layout
Each product has a folder under content/, named without the hyphen. Every
file under content/ is embedded:
content/
S101/
fc/
FeatureCatalogue.xml
pc/
portrayal_catalogue.xml
ColorProfiles/
Rules/
Symbols/
...
S102/
...
fc/FeatureCatalogue.xml is the feature catalogue. pc/ holds the portrayal
catalogue: its portrayal_catalogue.xml manifest and the folders it refers to,
such as Rules/, Symbols/, LineStyles/, AreaFills/, ColorProfiles/
and Fonts/. S-104 has no portrayal catalogue, so its pc/ folder is empty.
Some products have a README with their source, edition and any changes made when they were copied:
Fonts bundled with the S-124, S-201 and S-421 portrayal catalogues are under
the Apache License 2.0; see
LICENSE-Fonts.txt.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- EncDotNet.S100.Core (>= 0.25.0)
-
net8.0
- EncDotNet.S100.Core (>= 0.25.0)
NuGet packages (4)
Showing the top 4 NuGet packages that depend on EncDotNet.S100.Specifications:
| Package | Downloads |
|---|---|
|
EncDotNet.S100.Datasets.S201
Libraries for manipulating S-100 based nautical charts. |
|
|
EncDotNet.S100.Datasets.S57
Libraries for manipulating S-100 based nautical charts. |
|
|
EncDotNet.S100.Datasets.Pipelines
Per-spec IDatasetProcessor implementations, the DatasetPipelineFactory (file -> processor detection), the headless image-render capability, the S-98 interoperability authority, and the validation runner for IHO S-100 product datasets. Consumed by the EncDotNet.S100 convenience package, the viewer, and the s100 CLI. |
|
|
EncDotNet.S100
Open an IHO S-100 dataset, read its features and render it to an image using the bundled feature and portrayal catalogues. Wraps EncDotNet.S100.Specifications and EncDotNet.S100.Datasets.Pipelines behind a small, format-agnostic API; the underlying readers and catalogues remain available for custom wiring. |
GitHub repositories
This package is not used by any popular GitHub repositories.