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