# 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.