Latest Contributions by CherylLau

You can move the footprint by translating the geometry first using t() and then resizing the geometry afterwards.  When translating, you can use the apostrophe (ex: '1, '0.5) to move it a relative amount, or you can use scope.sx, scope.sy, scope.sz. t Operation  scope Shape Attribute  ... View more

The setback() operation can be used to create a setback of a certain distance from the front of the street (street.front). setback Operation  ... View more

In a dynamic shape, you can access the object attribute streetWidth, which contains a list of street widths, one for each edge of the polygon. https://community.esri.com/message/717270-re-designate-multiple-street-edges#comment-722386  Unfortunately, however, sidewalk widths are not accessible in this manner. Is it possible to add the sidewalkRightWidth and sidewalkLeftWidth from the streetShape to the CGA rule of the adjacent …  ... View more

Maybe the shape that you're trying to put the texture on is in xz instead of xy.  Try this: rotateScope(0, 90, 0) setupProjection(0, scope.zx, '1, '1) texture("builtin:uvtest.png") projectUV(0) ‍‍‍‍ Using scope.zx instead of scope.xy in setupProjection() means that the u direction will correspond to the z axis, and the v direction will correspond to the x axis.  The rotateScope() operation makes it so that u will go along the shape's original x axis, and v will go along the shape's original z axis.  You can take out the rotateScope if you're happy with u corresponding to z and v corresponding to x. To see the shape's scope, use the Model Hierarchy (Window -> Show Model Hierarchy -> Inspect Model -> select shape in viewport). Working with the Model Hierarchy Explorer  ... View more

Unfortunately, this is a limitation with cga.  Once you split a shape into components, edge components in this example, then you can't go back to the parent shape. However, in this case, there might be a workaround using labeled occlusion testing.  In one branch from your Shape rule, you could split your shape into edges, do the test on each edge, and if the edge passes (or doesn't pass) the test, then create a labeled occluder.  Then, in another branch from your Shape rule, before you split the shape into edges, you could do your area check AND check for occlusion with any labeled occluders.  If you see if the shape intersects the labeled occluder, then you'll know if the edge test passed (or failed). The catch is that you'll need to create a 3D closed shape which will be the labeled occluder.  This is necessary because occlusion testing will only work with closed occluder geometries.  From the edge shape (which is not 3D), you'll have to create and position a 3D shape which you can test for intersection with the original parent shape.  This 3D shape must not trigger occlusion for other lots.  For example, you could resize the edge into a 3D volume and fill the scope with a primitive cube.  But, you'll want to make sure that this cube only triggers the occlusion testing for the desired shape and not, for example, the neighboring shape. Here is the help doc page on labeled occlusion: label Operation  ... View more

The Inspect Model button is in more recent versions of CityEngine.  In the older versions, I think you just have to open the model hierarchy and select the shapes you want to inspect in the Viewport.  Maybe you could try deselecting and reselecting your model. It might not help, but here's the current help page for the Model Hierarchy: Working with the Model Hierarchy Explorer  ... View more

I'm not sure I understand what you want to do.  If FAR is calculated for the building as the total floor area divided by the lot area, then there is one value for FAR for the whole building.  How do you want to calculate FAR per floor?  Do you want to consider only the floors up until that floor, meaning that the floors above that floor do not count?  For example, if the building has 5 floors total, would the FAR value for the second floor only consider the areas of the first and second floors, disregarding the third, fourth, and fifth floors?  In that case, you can change your calculation of FAR to use split.index. FAR = geometry.area(bottom)*(split.index+1)/ParcelArea‍ This gives you the floor area of one floor multiplied by the floor number all divided by the parcel area.  Note that split.index starts at 0 for the ground floor, so add one to get the floor number. ... View more

No, sorry, it is not possible to insert an obj at a specific coordinate in a specific coordinate system using the i() operation.  The recommended workflow is to save the building footprints with the georeferenced data in a gdb, shp, or kml file, for example, and import these files into CityEngine, and the shapes will be placed in the appropriate location.  You can import using File -> Import or drag and drop.  These shapes will be imported as initial shapes.  You can then apply cga rules to the building footprints. Importing Data  ... View more

Yes, you can put another check in your recursion to check if the number of floors reached is above the minimum and below the maximum.  But, then if the minimum is set to something impossible for the max FAR, then you'll have to choose which criteria is more important to obey. ... View more

I'm guessing what might be happening is that the shape with the rule has edges that are all classified as something different than what you would expect. For example, the six large shapes in the middle in the Zoning scene in Tutorial 16 have the rule Zoning.cga applied to them.  For each of these shapes, all of its edges are classified as street.front since they are blocks created from the street network.  Each edge of the shape touches a street, so all edges are street.front.  Show the street network by choosing this option from the drop down arrow from an icon in the viewport's toolbar.  This means that only the frontSetback is applicable for these shapes.  Changing the back or side setbacks won't change the result. The setbacks are applied to edges that are classified as street.front, street.back, and street.side.  If a shape doesn't have these selectors (i.e. because it was not created dynamically by a street network), then the shape's object selectors object.front, object.back, and object.side will be used instead.  The shape's first edge (shown in orange when the shape is selected) is classified as object.front. Here is the help doc on setback(): setback Operation  ... View more

You can change the height of imported models or the height of plants in ESRI.lib.  However, setting the leaf area index or transpiration through attributes and having the model change accordingly is probably not possible.  You can see what the tree's shadow would look like in the viewport at a specific time of day by setting the scene light parameters (sun icon in the toolbar), but calculating exactly how much shade it produces is probably not possible. ... View more

Click the Inspect Model button in the Model Hierarchy tab.  Select the desired object in the viewport. ... View more

Yes, the limitation is the textures in the library.  If you have your own set of Vancouver-like textures, you can try to make your own texture library, make a copy of the rule, and modify your version of the rule to point to your own texture library. ... View more

It looks like there might be z fighting between the shapes and the models (roof textures).  This means that a face of the initial shape is on the same plane as the roof texture plane.  Then, they each fight to be visible.  You can hide the shapes (your building masses that you started with), through a drop down menu on the viewport toolbar, and then you'll only see the models (the roof textures).  Show/hide shapes is also accessible through the keyboard shortcut F11. ... View more

What does the elevation delta image file look like?  Can you see the strange spikes or chasms in this image?  It can be found in the data folder in the corresponding scene subfolder, and it starts with "elevation_delta". ... View more