Update selection and command Python expressions
Expressions written for IronPython-based Digi3D (Digi3D.NET 2022 and earlier) fail in Digi3D.AI if using old names such as digi3DGeometry, g.Codes or Atr, or Python 2's <>. This affects:
- Codes table selections.
- ON_PYTHON_EXPRESSION, OFF_PYTHON_EXPRESSION, ON_ONLY_PYTHON_EXPRESSION and SELECT_PYTHON_EXPRESSION.
Digi3D.AI evaluates expressions using bundled Python. Geometry and property names have changed. Old expressions raise errors or select no geometry.
Digi3D.NET 2023–2025 already used Python 3 and g. Those expressions fail if they use Text, Line, Point, Polygon or Complex without digi3d. and the environment does not import them (NameError), or read codes with g.codes[0].name (AttributeError). See Update a code table's Python quality controls.
Changes
- The evaluated geometry is
g, previouslydigi3DGeometry. - Properties use lowercase Digi3D.AI Python API names.
- No per-attribute variables or
Atrfunction are created. First-code attributes are ing.codes[0].attributes. - One Python 3 expression only: no
import, assignments or blocks. Replace IronPython's<>with!=.
Equivalents
| Earlier versions | Digi3D.AI |
|---|---|
digi3DGeometry |
g |
g.Codes[0].Name |
g.codes[0].code |
g.codes[0].name (Digi3D.NET 2023–2025) |
g.codes[0].code |
type(g) is Text (Digi3D.NET 2023–2025 with from digi3d import *) |
type(g) is digi3d.Text, or type(g) is Text with from digi3d import Text in the environment |
a <> b |
a != b |
g.Points.Count |
len(g) |
Propietario == 'Dylan' (attribute-generated variable) |
g.codes[0].attributes.get('Propietario') == 'Dylan' |
Atr('campo', 'valor') |
g.codes[0].attributes.get('campo') == 'valor' |
g.Area |
g.area |
g.Txt |
g.text |
g.Coordinate |
g[0] |
| Geometry type check | type(g).__name__ == 'Line' |
Notes:
g.codes[0].codeis code text. Test for a code withg.has_code('020400'), supporting*and?.len(g)counts vertices.- Attributes.
g.codes[0].attributesmaps field names to values..get('campo')returnsNonefor a missing field;attributes['campo']raises an error. g.areaexists only on lines and polygons; errors on points, texts or complexes.g.textexists only on texts.g[0]is the first(x, y, z)tuple.g[0][0]is X,g[0][1]Y andg[0][2]Z. PreviouslyCoordinatereturned an object withX,YandZ.g[0]errors on vertexless geometries.- Type. Names are
'Point','Text','Line','Polygon'and'Complex'. Polygons are not'Line'here: accept both withtype(g).__name__ in ('Line', 'Polygon').
Examples
Old expression:
Propietario == 'Dylan' and Plantas > 3 and digi3DGeometry.Codes[0].Name == '010101' and digi3DGeometry.Points.Count == 7
Digi3D.AI expression:
g.codes[0].attributes.get('Propietario') == 'Dylan' and g.codes[0].attributes.get('Plantas') > 3 and g.codes[0].code == '010101' and len(g) == 7
Old expression selecting two-vertex geometries with hazpol equal to SI:
g.Points.Count == 2 and Atr('hazpol','SI')
Digi3D.AI expression:
len(g) == 2 and g.codes[0].attributes.get('hazpol') == 'SI'
attributes.get('Plantas') > 3fails withoutPlantas, becauseNonecannot be compared with a number. Check existence first:g.codes[0].attributes.get('Plantas') is not None and g.codes[0].attributes.get('Plantas') > 3.
Missing equivalents
- Per-attribute variables. No direct equivalent. Read each through
g.codes[0].attributes.get('campo'), using only the geometry's first code. Atrfunction. Unavailable. Replace with.getcomparison as above.
Expression errors
Syntax errors or failures on a geometry display Python error text. Examples:
- Old names such as
digi3DGeometry:NameError. Text,Line,Point,PolygonorComplexwithoutdigi3d.when not imported:NameError.- Old properties such as
g.Codesorg.codes[0].name:AttributeError. g.areaon a point org.texton a line:AttributeError.attributes['campo']for a missing field:KeyError.<>:SyntaxError.- Expressions returning strings, lists or anything except
True,False,Noneor a number.
Commands acting on loaded drawings display one message per failing file; named selections display one per failing selection and file. ON_PYTHON_EXPRESSION and OFF_PYTHON_EXPRESSION leave visibility unchanged for the failed expression, applying other successful named selections. ON_ONLY_PYTHON_EXPRESSION hides all geometries except those passing another successful # selection. See ON_PYTHON_EXPRESSION.
Where to edit expressions
- Edit selections under Expressions in Code table editor. Back up the table before changes if you will still use earlier versions.
- Command expressions follow
=or are entered in Python expression. Update stored command text in menus, command files or buttons.
See also
- ON_PYTHON_EXPRESSION: expression reference, dialog snippets and errors.
- Update a code table's Python quality controls
- Geometry