Latest Contributions by NathanStocker

Hi Matt, I've got CE 2014.0 now, but the setback issue is still there that we discussed in this post. Using the parcels and rule from above, it still gets the results that you attached as '2013.1.jpg' rather than the correct '2014.0.jpg', which maintains the holes in both parcels. Is there something I'm missing? Thanks N ... View more

So the envelope operation uses: envelope(direction, maxHeight, frontBaseHeight, frontAngle, backBaseHeight, backAngle,          rightBaseHeight, rightAngle, leftBaseHeight, leftAngle) Within this, frontBaseHeight and frontAngle apply to the street.front edges if these are defined, otherwise they apply to object.front. I would like them to apply to the northern edge of the parcel, which would be world.north. Hope this helps make sense of it. ... View more

Hi Matt, The problem is effectively the same as for setback operation discussed below and fixed in CE2014.0. As an example, the attached green image is a simple extruded parcel, which includes a hole. However when innerRect() is applied to the parcel, it fills in the hole (resulting in the red image). The red image is the result of this code: Lot --> extrude(world.y,5) innerRect() color(1,0,0) Ideally, it would not fill in the hole. Instead it would find the largest possible rectangle within the remaining space. Nathan ... View more

Hi Matt, Just wondering about the issue with innerRect() not working on polygons with holes. Is this likely to be fixed soon, or is there a workaround until it is? This is quite crucial for what we're wanting to use CityEngine for, which is analysing infill capacity (i.e. whether a house will fit in a back yard). I was hoping to do this by using cadastral parcels with buildings cut out, but my rule requires innerRect to get a normal shaped house. Thanks Nathan ... View more

I thought that might be the case 🙂 Could you also confirm if the update will also fix the similar problem with innerRect() not taking holes into account? Thanks Nate ... View more

Thanks Matt - that's fantastic. I don't suppose you can give any indication of when 2014 will be released? ... View more

The attached .gdb contains the two parcels from the screenshot - the one which works and the other which doesn't. Looking at them, the obvious difference is that the hole in the one which works extends to the edge of the parcel. The zip also contains the CGA code, although it's just what I posted previously. Cheers N ... View more

Hi Matt, Using .gdb did the trick, thanks 🙂 On a related note, I'm having trouble with setback operations on the imported parcels (which have holes from the buildings being cut out). As a simplified example, I've attached a screenshot of the following operation: Lot --> Testing1 Testing2 Testing1 --> color(0,1,0) extrude(6) Testing2 --> setback(3){world.east : NIL | remainder : Testing3} Testing3 --> color(1,0,0) extrude(5) When I do this, many results (Testing3) fill the hole in as part of the remainder. This is shown in the left parcel of the screenshot, where the red portion is a hole in the original parcel and shouldn't be included in the result. The parcel on the right has the same rule applied but correctly still excludes the hole. I'm not sure if this is a remaining issue with holes in imported shapes, or just something with the setback operation. Is there a way to spatially limit a result to the original shape, so that a result doesn't spill over the boundaries? Thanks Nathan ... View more

Hi Matt, That's pretty much what I'm after - to extrude the building footprint to the roof of the larger envelope (which is based on the parcel). Sorry for the confusion, when I wrote 'while the larger transparent one ignores it', I meant this it's based on the original parcel shape, not the building footprint. ... View more

Hi, I'm using CityEngine 2013.1 and holes aren't quite working for me either. I'm importing parcels with the building footprints cut out. For some parcels it works fine (a 'hole' polygon and a surrounding good polygon), but sometimes it doesn't - it creates a hole polygon but the surrounding polygon doesn't have the hole cut out. The screenshot attached should help explain. The proper polygons are selected and some have vertices around the hole showing the excluded empty area, but others unfortunately include the empty area. It tends to be that the inner holes are excluded if they touch a boundary, but not if they are entirely within the larger polygon. Nate ... View more

Hi Matt, the screenshot attached has the process the rule follows, as well as an example of two envelopes. The pink/purple inner envelope is based on the building footprint, while the larger transparent one ignores it. The solution would involve a third envelope which had the xz scope (footprint) of the pink and purple envelope and extruded out to the y scope (i.e. roof) of the outer transparent envelope at all points. Nathan ... View more

It almost does. I was thinking of that, but then they would need to be reconciled, i.e. the envelope would need to be limited to the xz scope or the footprint would need extrapolated to the height of the envelope. I thought that perhaps it required what you suggested but in a linear form, so I tried to: Save the original scope values create the limited footprint save the modified x and z scopes return the shape to the original x and z scope values create the envelop limit the envelope to the modified x and z scope values This almost works, but the shape of the envelope carries through to the shrunken shape - it retains sloped sides where they could be straight up and down without breaching the original envelope. If I extruded the modified flat footprint very high and also created a suitable envelope, is there a way to extract the area which falls inside both shapes? Oh and thanks for the help, it's much appreciated. ... View more