Since the acquisition by Esri, I have been wanting to get my hands dirty with CityEngine. But only recently a good opportunity arose. I was asked to construct a 3D model of the underground for an area in the municipality of Hoogeveen. This also happens to be my last name, so I could this one not let me pass by!
CityEngine is a wonderful piece of software, but to get started with it can be quite a challenge. The learning curve is steep. So I want to share some of the lessons learned. It really helps if you are acquinted with the Eclipse environment, upon which CityEngine is based. Eclipse comes in many guises, Aptana (see also this post) and the Adobe Flash Builder being two that are sometimes used in GIS related activities.
image: courtesy Esri
A colleague of mine (thanks Marc!) came across a very handy mechanism to distribute your ArcGIS Python toolboxes and script tools. You can build your own Python Distribution to encapsulate a custom Python module, accompanying toolboxes and helpfiles and distribute it to your audience, by utilizing the Python Distribution Utilities (Distutils). It also builds an installer (such as “mytool-1.0-win32.exe” for Windows), that will install your module in the site-packages directory.
If you include a subdirectory “esri” in your project (see screenshot), any toolboxes or script tools will appear in the Systems Toolboxes in ArcGIS for Desktop, which is also very convenient.
The mechanism is described in the ArcGIS Python Help (here). The help item neatly describes which steps to take and also which naming conventions apply.