Exporting to Esri File Geodatabase (FileGDB)

Format Description

The ESRI File Geodatabase (FileGDB) is a file-based database for vector and raster data. It can be identified as folder with the suffix .gdb. For example, myDatabase.gdb.

CityEngine supports the export of datasets of the types "FeatureClass", "Table" and "Relationship Class".

Export Options for FileGDB

The export wizard for FileGDB consists of two pages, the first one contains general settings for all exported layers. The second page contains per-layer settings.

FileGDB Export Settings
The first page of the FileGDB export wizard contains settings relevant to all exported layers.

Option Description
Output Path The parent path of the exported geodatabase directory.
Geodatabase Name The name of the geodatabase directory. The ".gdb" suffix is mandatory.
Export Features Controls what is exported per selected scene shape. Available values are:
  • Models: Only the output of an attached CGA rule is exported.
  • Shapes: Only the geometry of the shapes is exported, any CGA rules will be ignored.
  • Models and Shapes: Both the shapes and the generated models will be exported. This usually results in more than one feature class.
Export object attributes Exports all object attributes as feature class fields. Information about data types and domains will be re-used, if available from an earlier FileGDB import. Array values will be ignored if the next option "Export dataset relationships" is not selected and the attribute is not part of an actual relationship.
Export dataset relationships All (array) attributes which result from an earlier FileGDB import with relationship import will be exported to the corresponding related tables.
Due to a limitation in the underlying FileGDB API, relationship classes cannot be generated by CityEngine directly. Instead, an ArcGIS workspace xml file is generated. Consult the ArcGIS Online Help about how to use it to generate Relationship Classes.
Emit Reports Any reports generated by the attached CGA rule will be written into feature class fields.

For any other options, please refer to the general export documentation.

FileGDB Layer Export Settings
The second page of the FileGDB export wizard contains the per-layer settings.

In addition to the global export options, the FileGeodatabase exporter contains an additional export page with the following per-layer settings:

Option Description
Export Layer Include or exclude any selected layers from export.
Layer Name Adjust the name of the selected layers. This will determine the name of the written FileGDB dataset(s).
Write Strategy Choose how existing feature classes are handled.
  • Replace Feature Class: deletes the current Feature Class and creates a new one.
  • Update Feature Class: if objects (based on OBJECTID) exist in the feature class, geometry and attributes are updated on export. If the object does not exist, it is appended to the feature class.
  • Update Feature Class Geometry: only the geometry of the existing feature is updated.
Geometry Type (for Shapes) Choose the geometry type for the shapes.
  • Polygon
  • Multipatch
Feature Granularity (for Models) Choose the number of features which are procedurally generated from a single CityEngine model.
  • One Feature Per Shape: All geometry, attributes and reports generated for a single start shape are merged and written into a single feature.
  • One Feature Per Leaf Shape: The geometry, attributes and reports of each leaf shape are written to a separate feature.

About the naming of exported feature classes

The FileGDB exporter may output multiple feature classes based on a single CityEngine scene layer. For example if we export a shape "foo" of layer "bar":

Further Reading


Copyright ©2008-2016 Esri R&D Center Zurich. All rights reserved.