To clarify: holes are supported with following input formats:??? CityEngine 2013.1: gdb??? CityEngine 2014.0: gdb, shpSo if you import footprints with holes into CityEngine 2013.1 we recommend to use the gdb format.
Similarly the offset rule also fills holes in 2014.1 if a negative offset value is used.
Is there a way to procedurally remove this unwanted hole-offset-geometry? comp(f) doesn't seem to have necessary options.
Ha, good catch ..
Matthias Buehler
Head of 3D Technologies
twitter: @MattB3D
-------------------------------
Garsdale Design Limited
matthias.buehler@garsdaledesign.co.uk
www.garsdaledesign.co.uk
I'm on version 2014.1 and have found that the Subdivide tool doesn't work with holes.
See attached - behaviour is the same using shp or gdb.
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?
ThanksN
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?
ThanksNathan
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
I am experiencing the same problem.
Usually i import DXF files and closed polylines are converted to CE shapes. What usualy happens with the holes is that CE reads it as a second shape. What kind of objects should i export from AutoCAD to preserve the holes?
In VecrorWorks, the same thing hapens both when exporting to DXF or to ShapeFiles, the object with a hole is being impoted as two seperate shapes.
Any ideas?
[ATTACH=CONFIG]33161[/ATTACH]
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.