# MSet 2026 / 64-bit STN013411 symbology transport bundle releaseId: `20260919-v35` knowledgeVersion: `2026.09.19-v35` branch: `64` track: `stn013411-symbology` bundleSchemaVersion: `2026.1` canonicalManifest: `https://www.graphico.sk/mset/ai/releases/20260919-v35/64/manifest.json` requiredPublishedModulesCount: `4` reference: `https://www.graphico.sk/mset/ai/releases/20260919-v35/64/reference/symbology/stn013411-resource-catalog.md` microstationCellsReference: `https://www.graphico.sk/mset/ai/releases/20260919-v35/64/reference/microstation/cells-point-vs-graphic.md` sourceCount: `6` payloadUtf8Bytes: `38912` payloadSha256: `CE7B53F51BA615DF2BF929ED827207B9484B356DD40FC3DB0E7E950AA71E3D25` completionMarker: `` This file is a deterministic on-demand transport artifact for AI clients that cannot retrieve the published STN013411 Markdown modules/references. It contains the LF-normalized UTF-8 text of every stn013411-symbology.requiredPublishedModules document in immutable-manifest order, followed by the STN resource catalogue and the general MicroStation Point/Graphic Cell reference. Each source section declares its own UTF-8 byte length and SHA-256; the payload declares aggregate integrity and the file ends with the exact completionMarker above. Treat the bundle as INCOMPLETE if the terminal marker or declared integrity fails. Project/directive-specific resource contracts still take precedence over this shared set. The immutable manifest remains the canonical release index. # STN013411 / STN013411_plus - overview and provenance releaseId: `20260919-v35` knowledgeVersion: `2026.09.19-v35` branch: `64` track: `stn013411-symbology` ## What this resource set is `STN013411` and `STN013411_plus` are MicroStation resource libraries used in the GRAPHICO/iNGs ecosystem for large-scale map symbology derived from **STN 01 3411 Mapy veľkých mierok** and extended with additional practical symbols outside the standard. The current public iNGs product page describes `iNGs_STN013411_plus` as containing all point symbols (cells) and line symbols (custom line styles) defined by STN 01 3411 plus symbols beyond the standard. It also identifies the four delivered resource files: - `STN013411.cel` - cells in the STN 01 3411 part, - `STN013411.rsc` - line styles in the STN 01 3411 part, - `STN013411_plus.cel` - additional cells beyond STN 01 3411, - `STN013411_plus.rsc` - additional line styles beyond STN 01 3411. Public source: `https://www.ings.sk/produkt/ings_stn013411_plus/` The visual catalogue is published at: `https://www.ings.sk/wp-content/uploads/iNGs_STN013411_plus.pdf` The available PDF identifies itself as **version 5.0, February 2012**. It is therefore used as a semantic/visual baseline, not as proof that its inventory is the newest complete inventory. ## Provenance history relevant to the KB Maintainer evidence supplied to GRAPHICO records that the original MicroStation implementation dates to **1995** and was later jointly maintained/extended in the GRAPHICO/iNGs environment. The `plus` name is intentional: later resources include practical symbols that the STN itself does not define. Do not collapse these provenance layers: 1. **STN 01 3411** - normative semantic origin of standard symbols. 2. **STN013411** - MicroStation implementation of the standard-oriented resource set. 3. **STN013411_plus** - maintained practical extension beyond the standard. 4. **MSet usage** - how a concrete MSet instruction chooses and activates those resources. A `plus` resource must never be presented as if STN 01 3411 itself defined it. ## Current resource snapshot supplied for KB intake GRAPHICO supplied a current four-file resource snapshot for this intake. Archive metadata / file inspection gives: | Resource | Size | Snapshot timestamp | SHA-256 | | --- | ---: | --- | --- | | `STN013411.cel` | 476672 B | 2025-06-23 08:34 | `65D466A0D847E2C8011DBB61F629C0137164ED4BAD29A8BC960F1FD32CE32AE1` | | `STN013411.rsc` | 152808 B | 2021-04-02 18:55 | `85642CE04CB05DCE1E7FDF248243B78744F5278FB2AFA12B18EB0C3D4F46B73D` | | `STN013411_plus.cel` | 258048 B | 2025-06-23 08:53 | `B3A0D715DA045DDF8641983C274D97749399B3CE4595D0069A157B2F1DB957B` | | `STN013411_plus.rsc` | 64240 B | 2019-07-21 21:12 | `0E37F61B69E8CBDAD96BCA60EBF4801ED4479F6858169C7E00E37865C6E7EDAF` | The two CEL files report MicroStation as the creating application and were last saved on 2025-06-23. This is evidence that the physical libraries are newer than the 2012 PDF. Maintainer evidence for this intake says that already defined resources were not redefined incompatibly; later changes were additions. The PDF can therefore be used as a stable semantic baseline for entries that it contains, while the current CEL/RSC snapshot remains stronger evidence for the present resource files themselves. ## Scope of this track This track explains: - the STN versus `plus` boundary, - the `L` / `G` / `B` resource model, - naming conventions, - how MSet instructions normally use the shared set, - precedence of project-specific symbology, - evidence and licensing boundaries. It is not a substitute for the full STN standard or the complete visual catalogue. # 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=` or `lc=` 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. # STN013411 in MSet authoring releaseId: `20260919-v35` knowledgeVersion: `2026.09.19-v35` branch: `64` track: `stn013411-symbology` ## Default shared-set rule The STN013411/STN013411_plus set is a shared practical symbology resource for MSet/iNGs workflows, but it is **not universally mandatory**. Use this precedence rule: 1. **A directive/project-specific symbology set wins.** If the instruction is for a standard that supplies its own cells/line styles, use that explicit resource contract. 2. **Otherwise the shared STN013411/STN013411_plus set is the normal practical default** when its resources are available. 3. If neither a project-specific contract nor this shared resource set is verified, do not invent a cell or custom line-style name. Examples of domains that may prescribe their own resource sets include Jednotná železničná mapa, Digitálna technická mapa Bratislavy and map standards for motorway/road infrastructure. Their dedicated resources take precedence over the generic shared set. GRAPHICO confirms that MSet 2026 examples use the shared set where no special project resource set is required. ## When the user authorizes Starter Standards / STN resources If the user explicitly allows the shared MSet Starter Standards / STN013411 resources, do not remain artificially resource-free when the published catalogue already resolves a suitable symbol or line family. Use the exact semantic mapping from this track/reference. For an **illustrative/demo directive**, the authoring assistant may choose a reasonable concrete semantic subtype itself when that choice is not safety- or project-critical. Example: for a generic `elektrorozvod v obci` demo, choosing the NN family `6.602x` as one representative distribution feature is acceptable when the task does not require engineering completeness. If it chooses an overhead example, the family resolves to `lc=6.6025`; for an underground example, to `lc=6.6026`. It should state the chosen subtype, not ask the user to select every minor resource variant. For a **real project/engineering-specific directive**, the project standard and user-supplied contract still control the required network class and resources; do not invent NN/VN/VVN classification where that distinction materially matters. When a known family uses the catalogue placeholder `x`, resolve the requested/chosen line kind to the concrete suffix (`5`/`6`/`7`/`8`) before emitting `lc=`. Never emit `lc=...x`. ## Prefer line styles for continuous network features Where the catalogue offers both `L x` and `G ` for the same network meaning, current GRAPHICO/iNGs MSet practice strongly prefers the **custom line style** for normal continuous network drawing. Use the Graphic Cell alternative only when a local rotated symbol is intentionally preferable, when the line representation does not meet the task, or when a project-specific convention says so. This is an authoring preference, not a reclassification of the catalogue and not a universal MicroStation rule. ## MSet command relationship MSet instruction commands commonly select these resources through ordinary active-resource setters. Examples: ```text ac=6.120_ ``` selects the Point Cell resource `6.120_`. ```text ac=6.120 ``` selects the Graphic Cell resource `6.120`. A custom line-style resource is selected by its exact line-style name, for example: ```text lc=2.24 ``` The surrounding placement tool is a separate authoring decision. Resource selection does not by itself guarantee that the correct placement tool/state is active; apply the normal Instruction Author semantic/context check. ## Choosing B versus G The semantic symbol may have both Point (`B`) and Graphic (`G`) representations. The directive author chooses the representation according to intended placement behavior. Do not encode a universal rule such as "all utility symbols are Point Cells" or "always use Graphic Cells for map symbols". Relevant factors include: - whether active MSet/MicroStation symbology should be inherited at placement time, - whether the cell should preserve the symbology stored in its library definition, - desired view/orientation behavior, - desired snap behavior, - the professional convention of the particular directive. Load `reference.microstationCells` for the Bentley-documented Point/Graphic behavior before making this choice when the user has not already specified it. ## Example: active symbology matters If the directive intentionally establishes color/line style/weight immediately before a cell placement and expects the symbol to inherit those active attributes, a Point Cell is the relevant representation because Bentley documents its symbology as coming from the active settings at placement time. A Graphic Cell is different: its color, line style and line weight are determined by the cell definition when created. Therefore a sequence such as `co=...;wt=...;ac=` must not be assumed to recolor/reweight the cell merely because those setters precede `ac=`. This is general MicroStation behavior, not a special STN rule. ## Restricted-client retrieval rule For an STN task, retrieval is **progressive**, not all-or-nothing: 1. Prefer the published STN Markdown modules/resource catalogue and the general MicroStation cells reference. 2. If the MicroStation cells Markdown cannot be opened, try the explicit `microstation-cells.txt` transport before calling that host knowledge unavailable. 3. If any required STN Markdown source cannot be opened, use the validated `stn013411-bundle.txt`. That bundle intentionally contains the four STN modules, the STN resource catalogue **and** the general Point/Graphic Cell reference. 4. Once that STN bundle is release/version/integrity validated, do not require a second successful fetch of the same embedded cells reference for the same answer. 5. If the validated catalogue/bundle explicitly resolves the requested symbol, use the exact evidenced resource name. A failed alternate URL is not a reason to hide a resource that has already been authoritatively resolved. 6. Fail closed only for the specific fact that remains absent or unverifiable after the applicable transports have been tried. Example: if the task asks for an above-ground hydrant that should inherit active directive symbology, the validated STN material establishes `Hydrant nadzemný (B) -> ac=6.120_`, while the embedded/general cells reference establishes why `B` / Point Cell is the relevant behavioral choice. The exact resource name may therefore be returned even if the standalone cells Markdown URL itself was unavailable. ## Evidence-aware authoring examples Historical source instructions supplied to the MSet.AI project contain real resource usage such as: - `Hydrant nadzemný (B)` -> `ac=6.120_` - `Hydrant nadzemný (G)` -> `ac=6.120` - `Orná pôda` -> `ac=3.019` in one drawing workflow, - `Plot drevený` -> `lc=2.103`, - `Plot drôtený` -> `lc=2.123`, - `Ohradný múr` -> `lc=2.163`. These examples prove real MSet ecosystem usage and naming. They do not override a newer project-specific instruction or guarantee that every target workspace has the resources attached. ## Resource availability remains explicit Before delivering an instruction that depends on STN013411 resources, establish one of: - the target workspace already includes the shared libraries, - the user/project confirms they are available, - the package/deployment explicitly provisions them. If resource availability is unknown, state the dependency instead of fabricating a fallback name. # STN013411 evidence boundaries and usage-rights context releaseId: `20260919-v35` knowledgeVersion: `2026.09.19-v35` branch: `64` track: `stn013411-symbology` ## Evidence hierarchy Use the strongest available source for the question being answered. ### Semantic meaning / visual symbol For entries present in the published visual catalogue, `iNGs_STN013411_plus.pdf` version 5.0 is a useful reviewed baseline. It distinguishes symbols "v zmysle STN 01 3411" from symbols "nad rámec STN 01 3411". Do not call an entry normative merely because it lives in a similarly named library. `STN013411_plus` explicitly contains non-STN additions. The visual/resource catalogue is sufficient for the published symbol meanings and `L/G/B` resource mappings it actually shows, including the table-6 `x` family rule. It is **not** sufficient evidence for broader STN 01 3411 drawing rules such as color policy; keep those unresolved until the primary standard or explicit project evidence is available. ### Current physical resource files The current CEL/RSC snapshot supplied to GRAPHICO is newer than the 2012 PDF. For questions such as "which four resource files are currently maintained?" or binary identity checks, the supplied snapshot and its hashes are stronger evidence. The KB does not claim that the 2012 PDF is a complete transcription of every current 2025 resource. Maintainer evidence says later evolution was additive and already defined entries were not changed incompatibly; therefore entries documented by the PDF can remain useful, while newly added resources may be absent from that PDF. ### MSet usage An MSet source/example proves that a resource name was actually used by an instruction. It does not by itself prove that the resource belongs to the STN normative layer; classify STN versus `plus` separately. ## No silent semantic promotion Keep these statements distinct: - "STN 01 3411 defines this map symbol." - "The STN013411 MicroStation resource set implements this symbol." - "The plus library adds this practical symbol." - "A particular MSet instruction uses this resource." A correct resource name can still be the wrong professional choice for a project standard. ## Distribution/use context GRAPHICO maintainer evidence records an operational agreement in the MSet/iNGs ecosystem: customers obtaining iNGs_Geo or MSet are granted the right to use this shared symbol resource set as supporting resources for those products. Treat that as product-usage context, not as a general-purpose public redistribution licence. This KB does not grant or define rights to redistribute, resell, modify or relicense the CEL/RSC libraries outside the applicable product/customer arrangement. The AI Hub publishes knowledge about the resources, not the binary CEL/RSC files themselves. ## Personal-name minimization Public MSet KB provenance should avoid unnecessary full personal names. Where a current iNGs vendor contact must be identified for evidence continuity, use the compact form **`PB (iNGs)`**. Multiple modules referring to the same confirmation are cross-references to one provenance item, not multiple independent pieces of evidence. ## Fail-closed rule If an exact symbol meaning, STN/plus classification, current resource name or target-workspace availability is not established by the published track/reference or user-supplied authoritative evidence, do not guess. Ask for the relevant catalogue/resource evidence or leave the item explicitly unresolved. # STN013411 / STN013411_plus resource catalogue - MSet reference releaseId: `20260919-v35` knowledgeVersion: `2026.09.19-v35` branch: `64` status: **canonical-development** ## Purpose This deep reference is a **verified seed catalogue and resource-contract guide** for the shared `STN013411` / `STN013411_plus` MicroStation resources used by MSet. It deliberately does not claim to be a complete transcription of the current binary libraries; the available public visual catalogue is version 5.0 (2012), while the supplied CEL files were last saved in 2025. For a resource not listed here, use the published visual catalogue/current project resources or ask for exact evidence rather than guessing. Public visual catalogue: `https://www.ings.sk/wp-content/uploads/iNGs_STN013411_plus.pdf` Public product description: `https://www.ings.sk/produkt/ings_stn013411_plus/` ## Resource-kind convention | Prefix | Meaning | Naming rule | | --- | --- | --- | | `L` | custom line style | prefix is descriptive only; use the exact following line-style name | | `G` | Graphic Cell | cell resource normally uses the shown name directly | | `B` | Point Cell | paired point form uses a final `_` in the cell name | Examples: `L 2.24 -> lc=2.24`, `G 6.120 -> ac=6.120`, `B 6.120_ -> ac=6.120_`. ## Table-6 line-family rule (`x`) The visual catalogue uses `x` as a placeholder in many utility-network line families. Its note defines the suffix as: | `x` | Catalogue meaning | Concrete-name example from family `6.602x` | | --- | --- | --- | | `5` | nadzemné vedenie | `6.6025` | | `6` | podzemné vedenie | `6.6026` | | `7` | neoverený priebeh | `6.6027` | | `8` | podzemné vedenie - catalogue STN article-114(b) variant | `6.6028` where applicable/available | The family expression itself is semantic catalogue notation. MSet/MicroStation authoring uses the **resolved concrete resource name**. The same suffix convention is used by reviewed `plus` families such as `6_842x` (Vedenie VO / verejné osvetlenie) and `6_852x` (Oznamovacie vedenie OK / optický kábel). The current `STN013411_plus.rsc` snapshot positively exposes `...5`, `...6`, `...7` and `...8` concrete names for both families, so an authorized author may resolve those variants by the same `x` meaning instead of treating the digits as unknown. ### Selected table-6 utility families These meanings are stated directly by the reviewed catalogue v5.0. They are useful semantic mappings, not merely number-pattern inference. | Family | Catalogue meaning | Typical concrete resolution | | --- | --- | --- | | `6.152x` | Vodovodné potrubie (bez rozlíšenia druhu) | `6.1525/6/7/8` as applicable | | `6.162x` | Vodovodné potrubie pitnej vody | `6.1625/6/7/8` as applicable | | `6.172x` | Vodovodné potrubie úžitkovej vody | `6.1725/6/7/8` as applicable | | `6.232x` | Kanalizačná stoka, potrubie (bez rozlíšenia druhu) | `6.2325/6/7/8` as applicable | | `6.322x` | Plynovodné potrubie bez rozlíšenia tlaku | `6.3225/6/7/8` as applicable | | `6.332x` | Plynovodné potrubie nízkotlaké | `6.3325/6/7/8` as applicable | | `6.342x` | Plynovodné potrubie strednotlaké | `6.3425/6/7/8` as applicable | | `6.352x` | Plynovodné potrubie vysokotlaké | `6.3525/6/7/8` as applicable | | `6.512x` | Tepelné potrubie (bez rozlíšenia druhu) | `6.5125/6/7/8` as applicable | | `6.522x` | Primárny teplovodný rozvod | `6.5225/6/7/8` as applicable | | `6.532x` | Primárny horúcovodný rozvod | `6.5325/6/7/8` as applicable | | `6.542x` | Primárne tepelné potrubie parné | `6.5425/6/7/8` as applicable | | `6.552x` | Sekundárny rozvod tepla | `6.5525/6/7/8` as applicable | | `6.592x` | Vonkajšie silové vedenie bez rozlíšenia druhu | `6.5925/6/7/8` as applicable | | `6.602x` | Vonkajšie silové vedenie nízkeho napätia - NN | `6.6025/6/7/8` as applicable | | `6.612x` | Vonkajšie silové vedenie vysokého napätia - VN | `6.6125/6/7/8` as applicable | | `6.622x` | Vonkajšie silové vedenie veľmi vysokého napätia - VVN | `6.6225/6/7/8` as applicable | | `6.632x` | Ochranné vedenie (zemniace) | resolve suffix only when the concrete resource is evidenced/available | | `6.702x` | Oznamovacie vedenie | `6.7025/6/7/8` as applicable | | `6.712x` | Oznamovacie vedenie požiarnej ochrany | resolve suffix as applicable | | `6.722x` | Oznamovacie vedenie hodinových zariadení | resolve suffix as applicable | | `6.732x` | Oznamovacie vedenie pre anténny rozvod | resolve suffix as applicable | | `6.802x` | Potrubie produktovodu | resolve suffix as applicable | The current `STN013411.rsc` snapshot positively exposes the normal electrical `...5`, `...6`, `...7` resources for the `6.592x`, `6.602x`, `6.612x`, `6.622x`, `6.632x` families, and positive evidence also exists for many `...8` variants. Absence from a simple binary-string scan remains non-proof of absence. ### Electrical semantic mappings useful to MSet authoring The catalogue directly identifies these standard-oriented resources: | Meaning | Resource(s) | Note | | --- | --- | --- | | Vonkajšie silové vedenie NN | `L 6.602x`, `G 6.602` | Prefer resolved `L` variant for continuous drawing in current MSet practice | | Vonkajšie silové vedenie VN | `L 6.612x`, `G 6.612` | same relationship | | Vonkajšie silové vedenie VVN | `L 6.622x`, `G 6.622` | same relationship | | Vonkajšie silové vedenie bez rozlíšenia druhu | `L 6.592x`, `G 6.592` | use when the voltage class is intentionally not distinguished | | Ochranné vedenie (zemniace) | `L 6.632x`, `G 6.632` | exact concrete suffix remains availability-evidenced | | Elektráreň / spínacia stanica / meniareň / transformátorovňa | `G 6.650`, `B 6.650_` | point/graphic pair | | Rozdeľovacia skriňa vonkajšieho silového vedenia | `G 6.661` | Graphic Cell in catalogue | | Transformačná stanica | `G 6.671` | Graphic Cell in catalogue | | Deliaci bod verejného osvetlenia | `G 6.681` | Graphic Cell in catalogue | | Zapínací bod verejného osvetlenia | `G 6.691` | Graphic Cell in catalogue | Historical production MSet instructions independently use `6.6025/6/7`, `6.6125/6/7`, `6.6225`, `6.5925/6/7` and related electrical cells. That is production-use provenance, not a claim that the historical directive overrides the catalogue or a newer project contract. ## Verified standard-oriented examples The following names are supported by the visual catalogue, current RSC name evidence and/or real MSet instruction evidence. They are examples, not a complete standard transcription. | Meaning | Resource(s) | Kind / note | | --- | --- | --- | | Orná pôda | `3.019`, point form `3.019_` where supplied/used | G/B cell pair in ecosystem usage | | Hranica vlastnícka | `2.19` | L | | Hranica zhora neviditeľná | `2.20` | L | | Hranica pohyblivá | `2.21` | L | | Hranica neznateľná | `2.22` | L | | Hranica podzemná | `2.26` | L | | Hranica sporná | `2.27` | L | | Plot drevený | `2.103` | L; real MSet usage evidence | | Plot drôtený | `2.123` | L; real MSet usage evidence | | Ohradný múr | `2.163` | L; real MSet usage evidence | | Hydrant nadzemný | `6.120`, `6.120_` | G/B pair; real MSet usage evidence | | Hydrant podzemný | `6.130`, `6.130_` | G/B pair; real MSet usage evidence | ## Verified `plus` examples from visual catalogue v5.0 These are practical additions **beyond STN 01 3411** in the catalogue section explicitly marked `nad rámec STN 01 3411`. | Meaning | Catalogue/resource name | Kind | | --- | --- | --- | | Bod ZBP - kostol | `1_020`, point `1_020_` | G/B | | Šípka na vzdialený bod | `1_031` | G | | Smerová šípka k parcelnému číslu | `1_041` | G | | Hranica intravilánu | `2_072` | L | | Rozhranie presnosti mapovania | `2_082` | L | | Plot bez rozlíšenia s podmúrovkou | `2_093` | L | | Drevený plot s podmúrovkou | `2_103` | L | | Drôtený plot s podmúrovkou | `2_123` | L | | Živý plot s podmúrovkou | `2_143` | L | | Ohradný múr s podmúrovkou | `2_163` | L | | Hranica vlastnícka so zlučkou | `2_19a` | L | | Hranica vlastnícka s malou zlučkou | `2_19b` | L | | Hranica vlastnícka s červenou zlučkou | `2_19c` | L | | Hranica vlastnícka s malou červenou zlučkou | `2_19d` | L | | Hranica vlastnícka zrušená | `2_19e` | L | | Hranica obvodu projektu pozemkových úprav | `2_282` | L | | Tráva | `3_010`, point `3_010_` | G/B | | Cintorín | `3_150`, point `3_150_` | G/B | | Ostatná plocha | `3_160`, point `3_160_` | G/B | | Komunikácia | `3_190`, point `3_190_` | G/B | | Priemet okraja strešného plášťa | `4_019` | L | | Kostol/kaplnka/kríž s vyznačením stredu | `4_090`, point `4_090_` | G/B | | Smer (cesta, železnica) | `5_011` | G | | Chránička | `6_01` | L | | Chránička rozšírená | `6_02` | L | | Chránička rozšírená 2x | `6_03` | L | | Kovový stĺp | `6_010`, point `6_010_` | G/B | | Ochranná skruž | `6_100`, point `6_100_` | G/B | | Signalizačná tyč/stĺpik bez rozlíšenia druhu | `6_120`, point `6_120_` | G/B in plus catalogue numbering | | Signalizačná tyč/stĺpik pre plynovod | `6_130`, point `6_130_` | G/B | | Výstražná tabuľa | `6_150`, point `6_150_` | G/B | | PRIS | `6_300`, point `6_300_` | G/B | | Vedenie VO (verejné osvetlenie) | `6_842x` family | L | | Oznamovacie vedenie OK (optický kábel) | `6_852x` family | L | | Močiar | `8_040`, point `8_040_` | G/B | | Vodotrysk/fontána s vyznačením stredu | `8_170`, point `8_170_` | G/B | ### Important numbering caution Do not infer semantic identity solely from a visually similar number across the standard and `plus` layers. The plus catalogue intentionally contains new naming families. A name must be resolved in the correct resource library/context. ## Current RSC resource-name evidence Binary string inspection of the supplied current `STN013411.rsc` positively exposes 181 unique dot-style numeric tokens matching the resource naming pattern. Examples include: `0.01` ... `0.20`, `2.012`, `2.032`, `2.042`, `2.052`, `2.062`, `2.072`, `2.082`, `2.093`, `2.103`, `2.113`, `2.123`, `2.133`, `2.143`, `2.153`, `2.163`, `2.173`, `2.19` ... `2.27`, `4.019`, `4.201a` ... `4.201e`, `4.223`, `4.23`, `5.01`, `5.02`, `5.032`, `5.042`, `5.052`, `5.062`, `5.212`, `5.223`, `5.293j`, `5.293z`, `5.303`, many `6.*` utility styles, and `9.01`, `9.03`, `9.05`, `9.06`, `9.11`. This is **positive presence evidence only**. The KB must not use absence from a simple binary-string scan as proof that a resource does not exist. The supplied `STN013411_plus.rsc` positively exposes underscore-style extension names including `2_19a` ... `2_19e`, related `2_20*`, `2_21*`, `2_22*`, `2_26*`, `2_27*`, `2_282`, `4_019`, `6_01`, `6_02`, `6_03`, `6_8425` ... `6_8428`, and `6_8525` ... `6_8528`. ## MSet usage examples are evidence, not universal defaults Historical MSet instruction sources supplied to the project use resources such as `ac=6.120_`, `ac=6.120`, `lc=2.103`, `lc=2.123` and `lc=2.163`. These confirm real MSet ecosystem use. A specific project directive may require a different symbol set. Project/JŽM/DTM/road-specific resource contracts take precedence over this shared catalogue. ## Color boundary This resource catalogue establishes symbol/resource identity and the line/cell relationships above. It does **not** establish the broader STN 01 3411 color rules. Do not derive STN colors from this visual/resource catalogue or from generic memory. Add those rules only from the authoritative standard or other explicit project evidence. ## Fail-closed lookup rule If the user requests an exact symbol not covered by a verified row and the current visual/resource evidence is not available, say that the exact resource is not yet established. Do not generate a number by analogy. # MicroStation point cells vs graphic cells - MSet reference releaseId: `20260919-v35` knowledgeVersion: `2026.09.19-v35` branch: `64` status: **canonical-development** ## Purpose This is general MicroStation host knowledge used by MSet when an author must reason about the behavior of a **Point Cell** versus a **Graphic Cell**. It is not specific to STN013411, although the shared STN013411/STN013411_plus resource set deliberately uses both cell types. Primary Bentley provenance: - Bentley KB0112453, **The differences between a graphic and point cell**: `https://bentleysystems.service-now.com/community?id=kb_article&sysparm_article=KB0112453` - Bentley's article states that the distinction applies to MicroStation/PowerDraft and lists the behavior below. ## Bentley-documented behavior ### Point Cell Bentley documents a Point Cell as follows: - it is placed on the **Active Level**, - its color, line style and line weight are determined by the **active settings when the cell is placed**, - it is **view independent**, - its only snappable point is its **origin**. For MSet authoring this means that active symbology established immediately before placement can materially affect the placed cell. If a directive intentionally sets `co=`, `lc=` or `wt=` and then activates/places a Point Cell, those active settings are part of the intended placement contract. ### Graphic Cell Bentley documents a Graphic Cell as follows: - its color, line style and line weight are determined when the cell is **created**, - it is not tied to the Active Level in the same way as a Point Cell, - it **rotates with the view**, - its internal keypoints can be snapped to. For MSet authoring the practical default is therefore that a Graphic Cell preserves the symbology designed into the cell definition instead of taking the current active color/line-style/weight merely because the directive set those values before placement. ## Why this matters to an MSet directive author Do not choose Point versus Graphic by symbol name alone. The authoring decision depends on intended behavior. Typical questions are: - Should the symbol inherit the directive's current color/line style/weight at placement time? A Point Cell is the relevant candidate. - Should the symbol preserve the symbology built into the library definition? A Graphic Cell is the relevant candidate. - Should the symbol remain view independent, or should it rotate with the view? - Is snap behavior to the insertion origin sufficient, or are internal cell keypoints required? The surrounding professional workflow may add further orientation rules. For example, an instruction author may deliberately choose a representation that stays in a fixed map orientation, or a representation intended to be rotated/aligned with a road or other object. The MSet KB must preserve that authorial intent rather than infer a universal choice from the semantic meaning of the symbol. ## Relation to STN013411 The shared `STN013411` / `STN013411_plus` resources use: - `G` for a Graphic Cell, - `B` for a Point Cell. Where both representations exist, the final underscore in the resource name distinguishes the Point Cell form. Example: - `G 6.120` -> Graphic Cell resource `6.120` - `B 6.120_` -> Point Cell resource `6.120_` The two resources represent the same semantic map symbol; the difference is the MicroStation placement behavior described above. The directive author decides which representation is appropriate. ## Restricted-client transport note The preferred source is this reference itself. If its Markdown representation cannot be retrieved, the stable `microstation-cells.txt` endpoint is the byte-equivalent text/plain fallback and should be tried before declaring the knowledge unavailable. For an STN013411 task, a release/version/integrity-validated `stn013411-bundle.txt` also carries this complete reference as one of its authoritative sources. A client does not need to re-fetch the same content successfully through a second URL before using it. ## Evidence boundary This reference records the Bentley-documented cell-type behavior needed by MSet. It is not a complete MicroStation cell manual. Do not infer undocumented behavior about shared cells, annotation cells, nested cells, ByLevel side effects or other specialist cell modes from this short reference.