City Engine 2013 is Out

Really cant wait on my birthday too.  Especially looking forward to the ability to do more sophisticated street cross sections and the urban planning and design toolkit.

Redlands, California—Esri has released CityEngine 2013, the latest version of its 3D urban design software. A new software developer kit (SDK) enables CityEngine procedural modeling technology to be used in popular 3D software such as Autodesk Maya, 3ds Max, and SketchUp.

CityEngine improves urban planning, architecture, and the modeling of urban environments, helping you make quality decisions while saving time and money. “CityEngine 2013 brings powerful procedural modeling technology in your favorite applications such as Autodesk Maya,” says Pascal Mueller, director of Esri R&D Center in Zurich, Switzerland. “We are excited about enabling our third-party developer community with our long-awaited CityEngine SDK, which provides developers with a rich set of tools to create smart 3D city applications.”

Importing OpenStreetMap streets into a project can jump-start your smart 3D city model. The new CityEngine OpenStreetMap importer improves the speed of that operation by converting free OpenStreetMap data in just a few mouse clicks. Esri also enhanced CityEngine content with e-on software’s prestigious plant library for exceptionally rich and realistic digital nature environments. E-on software is world renowned and has been used to create realistic vegetation and 3D visualizations in movies such as Avatar and The Hunger Games.

An exciting feature in the new CityEngine release is the ability to create rule packages to help you promote and share your work. Rule packages allow you to write and package procedural rule files for 3D models and other assets in CityEngine and share them with ArcGIS users.

Esri CityEngine is among the first 3D urban design software applications to include seamless export to the web via CityEngine web scenes. CityEngine 2013 continues that browser-based sharing experience. Once content has been exported to a web scene, it can be uploaded directly to ArcGIS Online or to your own server.

For more information and a free 30-day trial with full export capabilities, visit

# # #

Tattenhall – How Not to Write a Neighbourhood Plan Policy

The forthcoming JR of the Tattenhall NP will establish one hopes to what extent allocations in them are covered by the SEA directive.

But what an appallingly worded policy that is causing all the fuss.

“large scale, inappropriate development along existing village boundaries will not be supported by the community”.

Did not the examiner (not a planner) or Chester West and Cheshire’s planners not think this wording is a pile of doggy do do.

Three things:

-‘Innappropriate development’ not defined is a technical term that applies only to Green Belt.

-‘Along existing village boundaries’  you would meet the policy by leaving the narrowest of gaps.

-‘will not be supported by the  community’ – not an issue for a plan but another material consideration.  An agreed NP is part of the development plan, so all it needs to say is whether it would or would not be approved.  This says neither and is ambiguous.