Well it was bound to happen but I didn’t expect it to happen with the upcoming release of 2013. Not that this effects me, but as you can see from ESRI’s own Deprecation plans now say that :
Esri will end support of the 32-bit version of CityEngine for Windows. City Engine 2012 will be the last 32-bit release. This means that CityEngine 2013 will be only be supported on 64-bit versions of Windows, Mac OS and Linux.
So does this mean ESRI’s plans for CityEngine are looking at even larger datasets and more complicated functionality. Or does it mean they’ve just created a new version to run on the new 64bit iPhone 5s?
A recent webinar has also showed that they have improved street creation you can read about this and all CityEngine 2013 improvements I’ve heard about on a previous post here : “What’s coming in CityEngine 2013”
I’ve gone back to my rule file that tries to create a semi-realistic modern day historic Arabic city core, Yes it does have satellite dishes this is not a historic recreation of a bygone era….
The rule file can take existing GIS data (for example landuses per plot) and colour them based loosely the LBCS Code and colour values . The colours aren’t the greatest for 3D but there’s always a compromise.
Combining data in CityEngine is really easy, take this example I’m working on at the moment:
I’ve taken an old georeferenced map of London and I placed real world current 3D urban data from the nice people at CyberCity3D. I’ve digitized one of the old barracks shown on the old map actually within CityEngine and run one of my generic office block rule files over it. I’ve also run a floor level split rule over some of the CyberCity3D data (in the bright green) this has much more potential than just colouring or texturing buildings and I’ll be looking at this in detail soon…
For landscaping I’ve used a palm grove rule file, obviously I need to model new trees for this model!
This is obviously experimenting with different types of data and different sources of data, I’m toying with the idea of doing a before and after 3D model of this area of London. Then I might use some futuristic models to have some fun with it!
Updated: On the 29/09/20013 – Added info about deprecation plans and CityEngine being 64bit only in 2013 version and screen capture from webinar about improved streets
Updated: On the 16/09/2013 to include information on the SDK, mobile viewers and augmented reality plans
Updated: On the 04/06/2013 I removed some of the title to better reflect my post as well as shorten it for tweeting, I also added the release date/month (click read the rest of this entry below). I also added a new heading at the end on “Future thoughts, who will host those huge 3D cities and how?” as well as general edits…
None of what I write about below has come from a confidential source and no one has told me directly what’s coming to CityEngine or ESRI’s 3D stuff. The analysis bit is my own opinion and what I’ve gathered from a number of sources none of them have been from ESRI.
ESRI staff seem to be a bit cagey about telling me what’s coming in CityEngine 2013, much to my frustration, it’s hard to plan a project when you’re not sure about what features are being improved or even removed in the next release! I worry because CityEngine at present is so versatile I fear that any ‘improvements’ for one industry (like the movie industry) may scupper it’s use in my industry.
Ah well that is a worry with all software, except of course most software has competitors, CityEngine I don’t believe has. Skip to the end for my quick analysis of it all…
I’ve recently been able to get my hands on some beautiful real urban 3D data from the guys at CyberCity3D. These guys can take stereo imagery of any area and work some magic and give you back a 3D model for pretty much any 3D modeller package you need. They’re really keen on CityEngine at the moment and their data works really well with your rule files, so you know why I’m looking at this stuff!
The real skill is merging all this real 3D models, with GIS data and procedural buildings and models generated in CityEngine. This is where you start to realise how amazing CityEngine is purely in terms of the 2D and 3D data formats it handles. Within in 10 minutes I went from raw 3D data and some rule files to something I don’t mind putting onto a webscene.
With all this power comes great responsibility I heard once, well just because I have all this data and the ability to combine it, it doesn’t mean I should combine it all, does it? Obviously we now have to start thinking about 3D cartography (I’m looking at you @PetersonGIS and @kennethfield!) what is the appropriate level of detail for your project, do pastels work in 3D? Was I right? Perhaps less is more?
ArcGIS has a beautiful way with words Error 999999 is my particular favourite message from ArcGIS:
This is a generic error for which the cause does not have a specific error ID.
However a recent error when running a script to import Metadata got me stumped, below is a brief description of the problem and the steps that seem to have fixed it.
Running the Metadata Importer got me this message:
Executing: MetadataImporter “LOCATION\FILE.MXD” “LOCATION\FILE.MXD”
Start Time: Wed Sep 11 14:49:37 2013 Unable to obtain IMetadata from: LOCATION\FILE.MXD ; Invalid character in the given encoding. Line 1, position 1. Unable to obtain IMetadata from: LOCATION\FILE.MXD Failed to execute (MetadataImporter).
Failed at Wed Sep 11 14:49:37 2013 (Elapsed Time: 0.00 seconds)
I couldn’t figure it out as I could see no other posts on the ArcGIS forums that described this problem. Plenty of posts of the same message but no fixes other than through coding. Some of the solutions talked about UNICODEissues, so I typed in “unicode and arcgis”, one of the links brought me to this post and this image caught my eye:
What I did was change in ArcCatalog the table font to “Arial Unicode MS”.
I then went and selected the MXD with metadata I wanted to change and deleted the title and re-typed any text of a small length.
Then I ran the script again and it worked, no error messages and the metadat has now been imported.
Thoughts: Is this a text formatting issue? I haven’t time to muck about looking into this but my hunch is that the metadata editor allows html formatting and somehow some hidden text formatting got in. This would make sense as deleting the old title and retyping it again worked… hmmm