Latest Contributions by CherylLau

First, attributes should be set on shape objects (instead of models): objects = ce.getObjectsFrom(ce.selection, ce.isShape) Second, the rule attribute name should be preceded by "/ce/rule/": h = ce.getAttribute(o, '/ce/rule/height') Lastly, rule attributes only appear in the list returned by ce.getAttributeList() if they are user set.  This means we can only set them in Python if we first make them user-set attributes.  There are two options for this.  The first option (a simple workaround) is good if this is just a one time operation that you'd like to do because it involves manually setting the attribute.  The second option is more complicated but will work if you'd like everything to work within the python script without having to set anything manually.  In this case, we make the attributes user-set by way of an extra python script that is run from your first python script. Option 1: 1) Select your shapes. 2) Set the height attribute in the Inspector to 10.  This is the value it already was set to by the rules, but by resetting it through the Inspector we are making a user-set attribute instead of a rule-set attribute.  The number now appears bold indicating that it is a user set attribute. 3) Now you can run the python script (with the two changes above). Option 2: 1) Create an export python script.  Right click on the scripts folder -> New -> Python Module -> Select Module:Export (Reporting) and choose a name (e.g. coexport.py). 2) In the finishModel() function, add the following code to make the attribute a user set attribute: ce.setAttributeSource(shape, "/ce/rule/height", "USER") 3) In your first python script, add some lines (after you get the objects but before the for loop) to run the export script you just created: expSettings = ScriptExportModelSettings() expSettings.setScript("coexportscript.py") ce.export(objects, expSettings) 4) Now you can run the first python script (with the two changes above). ... View more

No, sorry, it is currently not possible to call CE python scripts from outside of the GUI/externally.  It's good to know that there's a demand for this though, so we appreciate your post. ... View more

I assume you want to set the attributes in the Plant Loader based on values you already have somewhere else.  Perhaps you have a set of shapes with object attributes that contain this info.  Yes, the names of your object attributes have to be the same as the attribute names in the rules. According to the rules, the attribute Name will be set to "Orange Tree" by default.  This is a rule set attribute (because its value is determined by the rules). This can be changed by manually setting the value for this attribute in the Inspector.  Then, the attribute becomes a user set value (indicated by bold font for the value of the attribute in the Inspector). Or, another way to set the value of this attribute is to link it to an object attribute so that it gets its value from the object attribute of the same name.  I assume this is the option that you are looking for.  To do this, select your shapes, click on the icon (square with arrow) between the attribute name and the value field in the Inspector, select "Object Attribute".  This will make the attribute get its value from the object attribute of the same name.  Note that for this to work, the rule attribute has to have the same exact name as the object attribute. ... View more

Ok, so I was under the assumption that you had one shape with multiple faces.  In this case, the split operation would work, but if you had multiple initial shapes, there's no way to combine them in the rules.  I would suggest combining all the shapes into a single shape either in CE or in the software you are using to generate the shapefile. You could combine all the shapes into one shape in CityEngine by selecting them -> Shapes -> Combine Shapes.  This will give you a single shape with multiple faces.  Then you can apply a rule to the single shape. Or, you could combine all the shapes into a single shape before you export your shapefile.  It should be a similar procedure as in CityEngine (select all the polygons, then find the menu item to combine the polygons). ... View more