Just a quick post to say something exciting happened whilst I was away at GISWORX last week, DigitalDales (trading/operating as FibreGarden) has started to dig in the ducting that will carry the community Fibre network. This will be great for Garsdale Design as well as residents up Garsdale and Dentdale who will when completed have a word class fibre optic broadband network. This will change everything around here.
Last week Garsdale Design (that is myself and Matthias) attended, exhibited as well as conducted a workshop at the Middle East’s premier annual Esri GIS conference called GISWORX held in Dubai. This is hosted and run by GISTEC an Esri Distributor. Those who follow me know I’ve been before, in fact I was the guest speaker the first time around (The Power of Play).
In celebration of the new release of CityEngine 2015 (click here for release notes) and the announcement of a new feature set called ‘handles’ we’ve produced this AnimatedGIF (next time I might just do a video).
(It’s a 8MB animated GIF so be patient those on a slow connection)
Comments on this post should really only be suggestions as to what these two are saying I think.
It’s that time of year when a new release of CityEngine becomes available (okay we think it maybe the 9th of April)! Yes we would love more bug fixes and features added, but they’re a small development team so we shall forgive them (this time…).
offset, roofGable and roofHip operations: made offset / roof construction more stable on polygons with co-linear vertices and fixed a memory explosion bug.
cleanupGeometry operation: fixed bug which led to illegal material assignements (“filled holes rendering bug”) on edge cleanup for geometries with per-face-materials.
Fixed undefined behaviour if the same name was used for a scalar attr and a map attr.
CGA compiler: Parameteric rules and functions with a large number of parameters do not hang the compiler / CityEngine anymore.
get/setExportDatasetRelationships in FGDBExportModelSettings
get/setExportFeatures in FGDBExportModelSettings
get/setAddObjectAttributes renamed to get/setExportObjectAttributes in FGDBExportModelSettings
Several new methods in FGDBImportSettings
setFloat in ImageExportTerrainSettings
additional argument animate for View3D.restoreBookmark and View3D.setCameraPerspective
Selection behaviour change in UI changes behaviour of ce.selection(), ce.setSelection() in cases where shape has a model. To get the shape from a selection with shape and model, usece.getObjectsFrom(ce.selection, ce.isShape) instead of ce.selection()
Believe it or not, but this whole scenery was created procedurally. In e-on software’s VUE.
This image is the result of an 8 week online (yes, late evenings and weekends!) 3D Workshop I just recently completed (my second already) on CGSociety.
Everything is procedural: The terrain model, the vegetation (each plant plus the distribution), the volumetric clouds and haze. Even the main attraction: The almost too well hidden villa. The villa is a procedurally generated model coming from CityEngine, which was manually placed.
Rendering this single image took about 26 hours on my quite fast hex-core machine. Minimal post work was done in PhotoShop.
Imagination is required to use CityEngine, I’ve said this before and I say it a lot in our 3DPathFinder CityEngine training sessions (shameless plug). The power of the rule file is in it’s ability to be used in other contexts and is often only limited by your imagination. Some of what I think Geodesign is also about this, connecting up other peoples workflows, joining disciplines together to form a coherent team.
Take the humble rule that places a parapet around a roof top and places a satellite dish inside, this is the same rule that I use to make my infamous “procedural sheep”. Get your head around that and the world is yours (in a metaphorical sense).
What do you mean you haven’t heard about my Procedural Sheep??!
This leads me to a little rule file I adapted yesterday, my colleague and friend Matthias had created a couple of rule files for a client (Philadelphia University’s Geodesign course). One rule file coloured a surface depending on the steepness of a slope, which clearly when drawing a path or a road can be useful. The other rule file was one that placed arrows facing down a slope in a grid pattern, think about water run-off and this is cool, useful stuff.
Have a look at what Berlin has done! Releasing 3D textured building data in six different formats! I’m currently downloading some of the CityGML data (there’s a lot), but this along with the Toronto data set should give you some great real world data for playing with in CityEngine! It looks like the data is available in the following formats:
The lack of choice in the textured version is a product I guess of the limitations in the fileformats but also processing time and file size. When we do CityEngine projects we almost always use untextured buildings they are easier to download and view on other peoples PCs, and lets face it textures don’t always add anything to your scene.
Berlin plays a leading role throughout Europe in the digital economy – as of today a 3D city model of the German capital is available to the public as Open Data. Until now Internet users have had the opportunity to explore the city of Berlin online by using the Business Location Center’s realistic model from Berlin Partner for Business and Technology – now they can also use the data. Regardless of whether for scientists, game developers, city planners, architects or graphic designers, the large-scale model of Berlin is available as a free download.