ArcGIS Geodesigner or Planning Engine? What’s in a name?

UPDATED on the 16/05/2012 – I’ve updated this article as I got it completely wrong, scroll to the bottom to find out more…

I’ve been thinking about how ESRI will integrate CityEngine with ArcGIS… either they are going to embed CityEngine functions within the core product, not ArcGIS basic but maybe standard or pro versions.  Perhaps as a procedural modeller toolbox?   Alternatively they are going to produce an industry specific product.

Personally I hate products being chopped up for different industries (I’m looking at you Autodesk and Adobe), but in some cases it can make sense.  For example urban designers have different requirements to geologists, so why would they want the same tools or have to pay for them?    Of course  I would point point out that limiting features based on profession can mean we won’t be able to learn from others!

Personally I think the name CityEngine is limiting your product, this is a procedural modeller which can just as easily do trees and agriculture as houses and skyscrapers.  So what will it be ESRI?

 

My choice?  ArcGIS Planning Engine…. what’s yours?


UPDATE 

Okay I got it completely wrong if anything it won’t be ArcGIS Planning Engine, it will be ArcGIS Geodesigner and here are a few reasons why:

So will it be this?

Will you SketchUp your CityEngine, please?


You’ll see my recent blog posts have been mainly about CityEngine and more recently Lumion3D.   Exciting stuff is being done by the people at Digital Urban (UCL) as well!   Both have been talked about as being ‘game changers’ but why?

  • Is it there advanced capabilities?
  • Or is it because of their 3D visualisation possibilities?
  • Perhaps it’s because they work nicely with other file formats?

The answer is in part yes to all of the above, but there is something more fundamental going on and it is in part due to a tool called SketchUp.

When you work in three dimensions everything becomes a little more complicated, yes you can visualise your buildings nicely and see what you are designing, but there is an added layer of complication, for myself it is viewpoints.


I know what a building should look like and all its component parts but you have to be able to view how everything interacts behind other features.   Understanding how a building will look from a 3D model is easier, but understanding how all the component parts fit together (services, floor levels etc..) can be harder to understand.

Working in an architectural practice two dimensional black and white drawings provide a good snapshot of how things fit together and work.   Now that virtually every client wants a 3D model and to walk around it like a computer game, has given us a problematic transition.   UK planning departments still want properly measured 2D black and white drawings, whereas clients would often prefer 3D models.

Historically we have worked with AutoCAD LT, as we’re too small to require AutoCAD (and wouldn’t use many of the advanced features) as well as the various Building Information Modelling (BIM) solutions.   However our clients do want 3D models so we have been creating models for a while now using SketchUp (even prior to it being purchased by Google and now Trimble).

SketchUp is amazing, no that’s not correct, it’s an incredible piece of software.    In fact I regard its development as being one of the most important things to have ever happened to our industry (architecture and urban design).    There are two main reasons for me giving such importance:

  • It fits into our existing software/workflows nicely
  • It is easy to use

That’s it, no really!   The learning curve as anyone who has used SketchUp will know, is very small.   I can guarantee most first time computer literate professional users (with no reading of a manual) can produce a good looking useful 3D model with ease.

Lumion3D is also not the most powerful of visualisation packages but after a couple of minutes of using it I realised I could with relative ease create beautifully rendered models and all within my existing workflows. Like SketchUp the real utility of this tool is how easy it is to create a good looking useful product with minimal training.

But what about CityEngine? It certainly is very powerful and the learning curve is quite steep for anyone without a background in programming.    However it does fit in with my existing workflows just like SketchUp and Lumion3D.   I’m certain that the ESRI CityEngine team is working on usability so I’m asking nicely ESRI, will you please SketchUp your software too?