# MSet 2026 / 64-bit iNGs_Geo integration transport bundle releaseId: `20260919-v35` knowledgeVersion: `2026.09.19-v35` branch: `64` track: `ings-geo-integration` 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/keyins/ings-geo.md` sourceCount: `5` payloadUtf8Bytes: `19677` payloadSha256: `6359900932043851ADDF7F77A83BBAD76494E9D167E4597CDDD2A742E666E17D` completionMarker: `` This file is a deterministic on-demand transport artifact for AI clients that cannot retrieve the published iNGs_Geo Markdown modules/reference, including clients that reject text/markdown. It contains the LF-normalized UTF-8 text of every ings-geo-integration.requiredPublishedModules document in immutable-manifest order followed by the exact published iNGs_Geo key-in 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. The complete bundle UTF-8 byte length and SHA-256 are declared as learningTracks.ings-geo-integration.transportBundle.bundleUtf8Bytes and .bundleSha256 in the current 64-bit manifest. Treat the bundle as INCOMPLETE if the terminal marker is absent or any declared integrity value fails. The immutable manifest remains the canonical release index. # iNGs_Geo integration - overview Status: **published / evidence-aware integration knowledge** ## Purpose This module gives an MSet-aware AI client the minimum product orientation needed for cooperation with iNGs_Geo. It is not a replacement for the iNGs_Geo user manual and does not make iNGs_Geo a mandatory MSet dependency. ## Product identity - Product: **iNGs_Geo** - Vendor: **iNGs spol. s r.o.** - Vendor source used for this integration knowledge: **iNGs_Geo 11.70 - Príručka používateľa**, dated **2025-06-26**. - The manual describes iNGs_Geo as an application for large-scale mapping, planimetry, altimetry and cadastral data, with point/symbol workflows, coordinate-system work, VGI/LandXML import/export and selected geodetic tasks. Source: iNGs_Geo 11.70 User Guide, section 1.1, p. 6. ## MSet relationship For MSet, iNGs_Geo is an **optional cooperating application**. MSet must not assume that every user or computer has iNGs_Geo installed, configured or loaded. The main integration surface is the iNGs_Geo MicroStation key-in interface. The iNGs_Geo 11.70 manual explicitly states that selected tools are parametrized so they can be started from the MicroStation command line when invoked from another application, and gives **MSet** as an example. Source: iNGs_Geo 11.70 User Guide, section 15.4, p. 159. Historical design provenance supplied by GRAPHICO: the MSet/iNGs_Geo command cooperation was created years ago so MSet could invoke selected iNGs_Geo functions. Historical intent is context only; exact current command syntax comes from current vendor documentation and/or current runtime/vendor evidence. ## Current compatibility evidence The published iNGs_Geo 11.70 manual explicitly lists Bentley/MicroStation environments through **MicroStation 2024**. Separate current evidence from **2026-09-06**: PB (iNGs) confirmed to GRAPHICO that **iNGs_Geo 11.70 works with MicroStation 2026** and that he had not encountered a problem with that combination so far. Evidence distinction: - through MicroStation 2024: **published vendor documentation**; - MicroStation 2026: **current vendor operational confirmation**, not an updated compatibility table in the 11.70 manual. Do not infer an explicit MicroStation 2025 confirmation from those two facts. ## Scope boundary This MSet knowledge track contains only: - concise iNGs_Geo orientation relevant to MSet; - availability/startup facts relevant to cooperation with MSet; - the MSet-relevant documented `ig_*` command interface; - current MSet usage and known integration discrepancies; - troubleshooting/compatibility evidence when it directly affects the integration. Unrelated iNGs_Geo product functionality remains outside this track. # iNGs_Geo integration - availability and launch Status: **published / evidence-aware integration knowledge** ## Optional dependency rule iNGs_Geo is an **optional integration dependency** for MSet. An MSet instruction or AI-generated workflow that uses an iNGs_Geo command must not assume that iNGs_Geo is installed, configured or currently loaded. Where availability matters, it should be confirmed by the user, detected by a supported mechanism, or treated as an explicit prerequisite. The current evidence does **not** define a supported MSet-side detection API. Do not invent one. ## 64-bit installation orientation The iNGs_Geo 11.70 manual documents a 64-bit installer named: ```text iNGs_Geo_11.70_64_setup.exe ``` For the CONNECT/2023/2024 environments documented by that manual, installation typically provides configuration, application binaries and workspace/workset resources including `iNGs_Geo_CONNECT.cfg`, `iNGs_Geo.ma`, `iNGs_Geo.dll`, an `iNGs` workspace and an `iNGs_Geo` workset. Exact physical paths depend on the Bentley product and environment. Do not hard-code a CONNECT-era path as a universal MicroStation 2025/2026 location without current evidence. Source: iNGs_Geo 11.70 User Guide, section 2.2, pp. 8-9. ## Launch command For the documented 64-bit Bentley environments, iNGs_Geo can be started from the MicroStation command line with: ```text mdl load ings_geo ``` The manual also describes launching `iNGs_Geo.ma` from the MicroStation MDL Applications dialog. When the documented `iNGs` workspace and `iNGs_Geo` workset are selected, required resources can be made available and the application can also be launched from the iNGs ribbon. Source: iNGs_Geo 11.70 User Guide, section 3, pp. 11-12. ## Autoload caution The vendor manual explicitly says that starting iNGs_Geo together with MicroStation as a design-file application by setting `MS_DGNAPPS` is **not recommended**. Therefore an MSet/iNGs_Geo workflow must not turn iNGs_Geo into an automatic `MS_DGNAPPS` dependency without a separate design decision and verification. Source: iNGs_Geo 11.70 User Guide, section 3, p. 12. ## MicroStation 2026 evidence The 11.70 manual's written compatibility list ends at MicroStation 2024. On **2026-09-06**, PB (iNGs) confirmed to GRAPHICO that **iNGs_Geo 11.70 works with MicroStation 2026** and that he had not encountered a problem with that combination so far. Classify this as **current vendor operational confirmation**. It does not mean that every individual key-in and parameter combination has been separately runtime-tested under MicroStation 2026. ## Unknown / do not infer The current evidence does not establish: - a supported MSet-side method for detecting whether iNGs_Geo is installed; - a supported MSet-side method for detecting whether iNGs_Geo is already loaded; - exact MicroStation 2025/2026 installation paths or configuration differences; - explicit written MicroStation 2025 compatibility confirmation; - exact failure text/behavior when an `ig_*` command is issued while iNGs_Geo is unavailable. # iNGs_Geo integration - current MSet usage Status: **published / evidence-aware integration knowledge** ## Purpose This module compares current MSet 2026 instruction usage with the iNGs_Geo 11.70 vendor documentation. It preserves discrepancies instead of silently normalizing them. Current MSet 2026 source inspected on **2026-09-06** contains these six unique `ig_*` command names in the relevant instruction sources: ```text ig_svah ig_vlozznacku ig_hektsiet ig_preber ig_legenda ig_import ``` ## Current aligned forms ### `ig_svah` Current MSet example: ```text co=166;ig_svah $S(1000) 2 1.5 1 0 ``` Vendor 11.70 documents: ```text ig_svah mierka vzor rozostup kolmosť smer ``` Status: **aligned command name and parameter count**. The `$S(1000)` expression is MSet substitution syntax and is governed by the MSet Instruction Author contract, not by iNGs_Geo. ### `ig_vlozznacku` Current MSet examples include: ```text ig_vlozznacku $S(1000) 8.021 1 1 0 ig_vlozznacku $S(1000) 7.061 1 1 0 ``` Vendor 11.70 documents: ```text ig_vlozznacku mierka značka interaktívne atribúty grafická ``` Status: **aligned command name and parameter count**. ### `ig_import` Current MSet uses: ```text ig_import ``` Vendor 11.70 documents `ig_import` and permits trailing parameters to be omitted, leaving corresponding dialog values unchanged. Status: **documented command; the current parameterless MSet form is compatible with the documented trailing-omission convention**. ### `ig_hektsiet` Current MSet uses: ```text ig_hektsiet ``` The 11.70 manual explicitly documents `ig_hektsiet` as the MicroStation command-line launch command for **Hektárová sieť**. It is not one of the 12 parametrized tools in section 15.4. Status: **documented launch key-in**. Do not infer parameters. ### `ig_legenda` Current MSet uses: ```text ig_legenda ``` The 11.70 manual explicitly documents `ig_legenda` as the command-line launch command for **Legenda**. It is not one of the 12 parametrized tools in section 15.4. Status: **documented launch key-in**. Do not infer parameters. ## Open discrepancy: `ig_preber` Current MSet instructions contain multiple uses of: ```text ig_preber 1 1 1 ``` The iNGs_Geo 11.70 manual instead documents **Prebratie prvku** as: ```text ig_preberprvok ``` with parametrized syntax: ```text ig_preberprvok aktívne_atribúty aktívny_textový_štýl aktívny_uhol hodnota_uhla ``` The current manual does not separately document `ig_preber`. Status: **pending vendor clarification / non-blocking**. Do not automatically rewrite current MSet instructions and do not claim that `ig_preber` is a supported alias. Equally, do not claim that current MSet is definitely wrong until vendor clarification or current runtime evidence resolves the discrepancy. ## Evidence summary | MSet command | iNGs_Geo 11.70 evidence | Current result | |---|---|---| | `ig_svah` | documented + parametrized | aligned | | `ig_vlozznacku` | documented + parametrized | aligned | | `ig_import` | documented + parametrized | aligned; trailing parameters omitted | | `ig_hektsiet` | documented launch key-in | aligned; no parameters documented | | `ig_legenda` | documented launch key-in | aligned; no parameters documented | | `ig_preber` | not documented as such; manual uses `ig_preberprvok` | **verification required** | The unresolved alias question does not block the rest of this integration track. Correct only the affected claim when new evidence arrives. # iNGs_Geo integration - known limitations and evidence gaps Status: **published / evidence-aware integration knowledge** ## Compatibility boundary - **MicroStation through 2024**: explicitly covered by the published iNGs_Geo 11.70 manual. - **MicroStation 2026**: current vendor operational confirmation from PB (iNGs), 2026-09-06; not an updated compatibility table in the 11.70 manual. - **MicroStation 2025**: no explicit written confirmation in the current evidence set. Do not infer it solely from 2024 and 2026 evidence. ## `ig_preber` versus `ig_preberprvok` Current MSet source uses: ```text ig_preber 1 1 1 ``` The current vendor manual documents: ```text ig_preberprvok 1 1 1 ``` and the full parametrized form of `ig_preberprvok`. The manual does not document `ig_preber` as a separate alias. A historical/backward-compatible alias is plausible but **not proven**. Current rule: - keep the discrepancy visible; - do not promote `ig_preber` as a documented alias; - do not declare current MSet wrong until vendor clarification or current runtime evidence exists; - keep this one point non-blocking for the rest of the integration track. ## Parametrized versus launch-only commands Section 15.4 defines exactly 12 parametrized tools. Do not generalize that every `ig_*` launch command accepts parameters. Current MSet also uses `ig_hektsiet` and `ig_legenda`. The manual documents them as command-line launch commands, but not as section-15.4 parametrized tools. Treat them as launch-only evidence and do not invent parameters. ## Availability / detection gaps The current evidence does not define a supported MSet-side API/key-in for reliably detecting whether iNGs_Geo is installed, configured for the active Bentley environment or already loaded. It also does not establish exact failure behavior when an `ig_*` command is issued while unavailable. Do not invent detection logic. If MSet later implements a supported detection mechanism, document it from current MSet source/spec/runtime evidence. ## Installation-path boundary The 11.70 manual gives typical 64-bit paths for the Bentley environments documented at the time. Do not treat those paths as universal MicroStation 2025/2026 installation locations without separate current evidence. ## Runtime-verification boundary The 2026 vendor confirmation establishes successful current operation of iNGs_Geo 11.70 with MicroStation 2026 as a product combination. It does **not** prove separate runtime testing of every documented `ig_*` command and parameter combination. Keep evidence classes distinct: - vendor-documented syntax = **documented**; - overall 11.70 + MicroStation 2026 combination = **vendor operationally confirmed**; - individual 2026 command/runtime claims = only when actually tested or explicitly confirmed. When new evidence arrives, correct the smallest affected claim rather than widening or redesigning the whole track. # iNGs_Geo key-in reference for MSet cooperation Status: **published / vendor-documented reference** Primary source: **iNGs_Geo 11.70 - Príručka používateľa**, section **15.4 Parametrizácia príkazov**, pp. 159-166, © 2025 iNGs spol. s r.o., dated 2025-06-26. This reference contains only the command-line interface explicitly documented by iNGs for tools relevant to application-to-application invocation. The vendor manual explicitly names **MSet** as an example of an application that can invoke these parametrized tools. ## Common parameter conventions For section-15.4 parametrized commands: - `*` - leave the parameter unchanged; use the current value from the tool dialog. - `§` - use the current active MicroStation value where the manual supports it; this is explicitly documented for text height/width. - `0` - checkbox/state off. - `1` - checkbox/state on. - One or more **trailing parameters may be omitted**; omitted trailing values remain at their current dialog values. Do not generalize `§` to parameters for which the vendor documentation does not define it. ## Documented parametrized tools ### `ig_import` - Import bodov ```text ig_import súbor.imp súbor.dat ``` - `súbor.imp` is resolved using `INGS_GEO_IMPORT_NASTAV`. - `súbor.dat` is resolved using `INGS_GEO_TABULKA_KODY`. Vendor example: ```text ig_import priklad_2.imp priklad_tabulka_kodov.dat ``` ### `ig_vlozbod` - Vloženie bodu ```text ig_vlozbod súbor.imp číslo_bodu zobr_čb výška_bodu zobr_vb iný_údaj zobr_iu poznámka zobr_pz značka prírastok ``` The manual says to use `-` for the `značka` parameter when inserting without a symbol value. Vendor example: ```text ig_vlozbod elektrika.imp 500 1 123.45 1 (-2.45) 1 * 0 6.081 1 ``` ### `ig_vlozznacku` - Vloženie značky ```text ig_vlozznacku mierka značka interaktívne atribúty grafická ``` Vendor example: ```text ig_vlozznacku 500 4.170 1 1 0 ``` ### `ig_zmenakodu` - Zámena podľa kódov ```text ig_zmenakodu tabuľka_kódov pôvodný_kód nový_kód aktualizuj ``` `tabuľka_kódov` is resolved using `INGS_GEO_TABULKA_KODY`. Vendor example: ```text ig_zmenakodu priklad_tabulka_kodov.dat js Vrt 1 ``` ### `ig_rovnobezky` - Rovnobežky ```text ig_rovnobezky mierka rozostup rovnobežka vrstva farba typ hrúbka ``` `rovnobežka`: `1` = left, `0` = symmetric, `-1` = right. Vendor examples: ```text ig_rovnobezky 500 1 0 ig_rovnobezky 1000 0.5 1 58 6 2.123 2 ``` The manual also documents layer-name handling: spaces cannot be entered literally as parameter separators; layer number is preferred, or spaces may be replaced with `+` when needed. Missing referenced levels may be created by iNGs_Geo; if a referenced line style does not exist, line style `0` is used. ### `ig_ciaraspopisom` - Lomená čiara s popisom ```text ig_ciaraspopisom popis mierka výška šírka rozostup ``` For multi-word `popis`, the manual uses `_` in place of spaces; iNGs_Geo converts `_` back to spaces. Vendor examples: ```text ig_ciaraspopisom 22_kV 500 3 2 50 ig_ciaraspopisom * * § § * ``` ### `ig_popisciaru` - Popisovanie čiar ```text ig_popisciaru popis mierka výška šírka rozostup ``` Parameter meanings/input conventions follow `ig_ciaraspopisom`. ### `ig_omerka1` - Omerná miera prvku ```text ig_omerka1 mierka výška šírka formát pomlčky priemet interaktivita text ``` `formát` accepts `0`, `1`, `2`, `3` for decimal-place count. Replacement text containing spaces uses `_`. Vendor example: ```text ig_omerka1 500 3 2 2 1 1 0 2.1_m ``` ### `ig_omerka2` - Omerná miera medzi bodmi ```text ig_omerka2 mierka výška šírka formát pomlčky čiara z1bodu priemet text ``` `formát` accepts `0`, `1`, `2`, `3`. Replacement text containing spaces uses `_`. Vendor example: ```text ig_omerka2 250 2.5 1.5 2 0 1 0 1 3.66_m ``` ### `ig_schody` - Schody ```text ig_schody X obvod 3body mierka priemer rameno ``` For `X`, an integer means number of steps; a decimal value means one-step width in metres. The manual notes that when more than three parameters are supplied, the output line is also drawn. Vendor examples: ```text ig_schody 7 0 1 ig_schody 0.35 0 1 500 1 1 ``` ### `ig_preberprvok` - Prebratie prvku ```text ig_preberprvok aktívne_atribúty aktívny_textový_štýl aktívny_uhol hodnota_uhla ``` Vendor example: ```text ig_preberprvok 1 1 1 ``` Current MSet source uses `ig_preber 1 1 1`. The current vendor manual does not document `ig_preber` as a separate alias. Treat that discrepancy as **pending vendor clarification**; do not silently substitute one form for the other. ### `ig_svah` - Svahové čiary ```text ig_svah mierka vzor rozostup kolmosť smer ``` `vzor`: `1` = `1/1`, `2` = `1/2`, `3` = `1/3`, `4` = `2/3`, `5`-`8` = vendor-defined patterns 5-8. `kolmosť`: `0` = top, `1` = axis, `2` = bottom. Vendor example: ```text ig_svah 500 2 5 0 1 ``` ## Additional launch key-ins used by current MSet The current MSet source also uses these vendor-documented command-line launch forms: ```text ig_hektsiet ig_legenda ``` They are **not** part of the section-15.4 parametrized list. Treat them as documented launch key-ins only and do not invent parameters. ## Authoring boundary When an MSet instruction invokes iNGs_Geo: 1. Treat iNGs_Geo as optional; do not assume installation/load state. 2. Preserve documented parameter order and documented `*`, `§`, `0`, `1`, trailing-omission semantics. 3. Do not invent quoting rules; for the documented text parameters the vendor manual explicitly describes `_` as the replacement for spaces. 4. Do not infer that every iNGs_Geo tool has a parametrized key-in. 5. Keep MSet substitution semantics such as `$S(...)` under the MSet Instruction Author contract; they are not iNGs_Geo parameter syntax. 6. Keep compatibility evidence separate from syntax evidence.