Back to Top

Annotations

In this topic

    Synopsis

    Annotations are used to add additional information to a rule or an attribute. Annotations are optional and do not affect the semantics of a rule and thus have no influence on the model generation. Annotations are mostly used to give additional hints for user interface elements such as the Inspector on how to present attributes or rules.

    Annotations

    • @Angle
    • @Color
    • @Description("description")
    • @Directory
    • @Distance
    • @Enum(value_1, value_2, ..., restricted=true)
    • @File
    • @File("ext_1", ..., "ext_n")
    • @Group("level_1-group", ..., "level_n-group")
    • @Group("level_1-group", ..., "level_n-group", order)
    • @Handle(handle params)
    • @Hidden
    • @In{Line|Mesh|Point|PointCloud|Polygon}
    • @Order
    • @Out(granularity=separatedShapes|combinedShape)
    • @Percent
    • @Range(min=value1, max=value2, stepsize=0, restricted=true)
    • @StartRule

    Examples

    @Angle

    Adds a ° (degree) unit in Inspector and a [0;360] range by default with slider. Use @Range to specify a different range. 

    @Angle
attr angle = 180

    @Color

    Mark an attribute as a color attribute which will present a color picker in the inspector.

    @Color
attr userColor = "#000000"

    @Description("description")

    Adds a description to an attribute or rule which will be displayed as tool tip in the inspector or as description in the start rule chooser or style manager. Use \n for line breaks.

    @Description("The building width")
attr width = 40

    @Directory

    Mark an attribute as a directory name. The inspector will present a directory chooser.

    @Directory
attr assets = "/assets/lod" + lod

    @Distance

    Adds a meter of foot unit (depending on the Coordinate System used by the scene) in Inspector.

    @Distance
attr distance = 1852

    @Enum(value_1, value_2, ..., restricted=true)

    Sets an enum with specific values. Values can be numeric or string. Parameter restricted is optional (default is true). If true no other values can be entered in the inspector or set by a handle. 

    @Enum("low", "mid", "high")
attr lod = "low"
@Enum(10, 20, 30, restricted = false)
attr height = 20

    @File

    Mark an attribute as a file name. The inspector will present a file chooser.

    @File
attr asset = "myfile.obj"

    @File("ext_1", ..., "ext_n")

    Mark an attribute as a file name. The inspector will present a file chooser for the given file extensions ("ext_1", ... , "ext_n")

    @File("tif", "tiff")
attr texture = "tex0.tiff"

    @Group("level_1-group", ..., "level_n-group")

    Set the group of the following attributes (the inspector will group attributes accordingly). The current group is maintained across imports. To leave the current group, use @Group.

    @Group("First", "Second", "Third")
attr grouped = 0

    @Group("level_1-group", ..., "level_n-group", order)

    Set the group and the sort order for groups/subgroups in the inspector (similar to @Order for attributes). Where order is a numeric value.

    @Group("First", "Second", "Third", 1)
attr grouped = 0

    @Handle(handle_params)

    Adds an interactive handle to the following attribute.

    @Handle(shape=Solid, align=right)
attr dimension = 40

    @Hidden

    Mark an attribute or rule as hidden. Hidden attributes won't appear in the CityEngine inspector or start rule chooser, but they will be connected to matching object attributes automatically. @Hidden can also be used to hide a set of attributes (as in its second form with a list of attribute names) before an import statement. Without explicitly naming the attributes, @Hidden before an import statement will hide all imported attributes in the inspector; the hidden annotation will be recursively propagated to the imports of the hidden import. 

    @Hidden
attr hide_me = 0

    @In{Line|Mesh|Point|PointCloud|Polygon}

    These annotations can be used to communicate the expected geometry type of the start shape. While these annotations currently have no effect in CityEngine, ArcGIS Pro expects each start rule (see above) to be annotated with the expected input type (as of ArcGIS Pro 2.4, only @InPolygon, @InMesh, @InLine and @InPoint are supported). If there is none, it defaults to @InPolygon. So if you export a rpk to be used with different geometry types in ArcGIS Pro, make sure you add one of these annotations.

    @Order(order)

    Sets the sort order for an attribute in the inspector. Where order is a numeric value.

    @Order(1)
attr i_m_1st = 0
@Order(2)
attr i_m_2nd = 0
@Order(3)
attr i_m_3rd = 0

    @Out(granularity=separatedShapes|combinedShape)

    This annotation can be used to communicate the suggested granularity of the output geometry. The default is combinedShape. While this annotation currently has no effect in CityEngine, it is essential to trigger leaf shape generation in ArcGIS Pro. Add it to the start rule in that case.

    @Percent

    Adds a % unit in Inspector and a [0;100] range. In the CGA File, the value has to be initialized to the real value (e.g. 0.1 for 10%). The Inspector will display the vale in percent (e.g. 10%). The user has to enter the value in percent in the inspector.

    @Percent
attr inflation = 0.012

    @Range(min=value1, max=value2, stepsize=0, restricted=true)

    Sets the numeric range of an attribute by parameters min and max (inclusive). Parameter stepsize is optional (default is 0). If set to >0 possible values are set in respective steps starting from the minimum value. Both sliders in the inspector and handles respect the step size. Parameter restricted is optional (default is true). If set to true any numerical input value is set to the nearest possible value in the inspector. 

    @Range(min=5, max=50)
attr height = 20
@Range(min=0, max=45, stepsize=15, restricted=false)
attr angle = 30

    @StartRule

    Mark a rule as a start rule for the start rule chooser

    @StartRule
Start-->NIL

    Feedback on this topic?

    In this topic