# STN013411 resource model and naming

releaseId: `20260919-v35`
knowledgeVersion: `2026.09.19-v35`
branch: `64`
track: `stn013411-symbology`

## L, G and B

The catalogue uses three resource-kind prefixes as explanatory labels:

- `L` = line symbol / MicroStation custom line style,
- `G` = Graphic Cell,
- `B` = Point Cell.

The prefix is not part of the MicroStation resource name itself. The actual name follows it.

Examples:

- `L 2.24` -> line-style resource name `2.24`
- `G 6.120` -> Graphic Cell resource name `6.120`
- `B 6.120_` -> Point Cell resource name `6.120_`

## Point/Graphic name convention

Where the same semantic map symbol is provided as both Graphic and Point Cell, the Point Cell form is distinguished by a **final underscore** in the resource name.

Example:

| Semantic symbol | Catalogue form | Actual cell resource |
| --- | --- | --- |
| same symbol, Graphic Cell | `G 6.120` | `6.120` |
| same symbol, Point Cell | `B 6.120_` | `6.120_` |

The underscore does not create a new STN meaning. It identifies a different MicroStation cell type/placement behavior for the same semantic symbol.

The general host behavior of Point versus Graphic cells is documented separately in `reference.microstationCells`. Load that reference when the authoring decision depends on active symbology, view behavior, level placement or snapping.

## Line-style names

For standard STN-oriented custom line styles, the resource name is directly the catalogue number, for example `2.24`.

The current `STN013411.rsc` snapshot contains many resource-name tokens in this form, including `2.19`, `2.20`, `2.21`, `2.22`, `2.23`, `2.24`, `2.25`, `2.26`, `2.27`, `4.223`, `5.01`, `5.02` and many utility-network styles in the `6.*` family.

The `plus` library uses its own extension names where no STN ordinal exists or where a practical variant is derived. The 2012 visual catalogue shows examples such as:

- `L 2_19a` - boundary variant with junction mark,
- `L 2_19b`, `L 2_19c`, `L 2_19d`, `L 2_19e` - related variants,
- analogous `2_20*`, `2_21*`, `2_22*`, `2_26*`, `2_27*` families,
- `L 6_01`, `L 6_02`, `L 6_03` - protective-conduit variants.

Do not normalize underscore-style `plus` names into dot-style STN names. The exact library resource name is authoritative for authoring.

## Line-family placeholder `x`

In table 6 of the reviewed visual catalogue, many utility-network line styles are published as a **family** such as `L 6.602x` rather than as one literal MicroStation name. The catalogue note defines `x` as a kind-of-line suffix:

- `5` = nadzemné vedenie (above-ground/overhead),
- `6` = podzemné vedenie (underground),
- `7` = neoverený priebeh (unverified/approximate course),
- `8` = podzemné vedenie according to the catalogue's STN article-114(b) variant.

Therefore `6.602x` is the semantic family for **vonkajšie silové vedenie nízkeho napätia - NN**, while concrete authoring uses a real resource such as `6.6025`, `6.6026`, `6.6027` or, where applicable and available, `6.6028`. The same family rule applies to multiple water, sewer, gas, heat, electrical and communication rows in table 6.

`x` is a catalogue placeholder, **not** a literal character to send to MicroStation. Resolve the semantic family + required line kind to the concrete resource name, then verify that the concrete resource is available in the applicable library/environment. Do not assume that every suffix exists for every family solely from the family notation.

The `plus` catalogue uses the same idea in families such as `6_842x` (Vedenie VO) and `6_852x` (Oznamovacie vedenie OK). The current `STN013411_plus.rsc` snapshot positively exposes the concrete `...5`, `...6`, `...7` and `...8` names for both of those families.

## Line style and Graphic Cell in the same catalogue row

Some table-6 rows publish both a line family and a Graphic Cell, for example a form conceptually like `L 6.512x` together with `G 6.512`. Treat those as **related representations of the same semantic network object**, not as unrelated resources:

- `L ...x` represents the continuous network using a custom line style,
- `G ...` is a Graphic Cell representation that can be placed/rotated on the corresponding line when that local representation is useful.

Current GRAPHICO/iNGs MSet practice strongly prefers the custom **line-style representation for continuous network drawing when an appropriate `L ...x` family exists**. The Graphic Cell remains a valid alternative for local/special placement or historical/project-specific practice. This preference is current MSet practice, not a claim that STN itself forbids the Graphic Cell form.

## Selected semantic examples

The visual catalogue and maintained MSet usage evidence include examples such as:

| Meaning | Resource representation |
| --- | --- |
| Hydrant nadzemný | `G 6.120` / `B 6.120_` |
| Hydrant podzemný | `G 6.130` / `B 6.130_` |
| Orná pôda | `G 3.019` / point form `3.019_` where used |
| Hranica ochranného pásma | line-style family identified by its catalogue/resource number |
| Vedenie VO (verejné osvetlenie) | `plus` line-style family `6_842x` in the 2012 catalogue |
| Oznamovacie vedenie OK (optický kábel) | `plus` line-style family `6_852x` in the 2012 catalogue |

The exact symbol/resource must still be checked against the current STN reference or a verified project resource contract before authoring. Do not invent a nearby-looking number.

## Naming is a resource contract

A valid MSet command is not enough. `ac=<name>` or `lc=<name>` is environment-ready only when that exact cell/line-style resource is known to exist in the target Standards environment or is explicitly provisioned with the instruction package/workspace.

This track gives a shared default resource contract; a project-specific resource contract may override it.