Exporting to Esri File Geodatabase (FileGDB)
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.
|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:
|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.
In addition to the global export options, the FileGeodatabase exporter contains an additional export page with the following per-layer settings:
|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.
|Geometry Type (for Shapes)||Choose the geometry type for the shapes.
|Feature Granularity (for Models)||Choose the number of features which are procedurally generated from a single CityEngine model.
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":
- In case of "Export Features" set to "Shapes" or "Models and Shapes", the shape "foo" will be directly written to feature class named "bar".
- If "foo" has a CGA rule attached which produces polygons, its output will result in a multipatch feature class called "bar_ProcedurallyGeneratedMultipatches".
- If "foo" has a CGA rule attached which produces points (e.g. by comp(v)), its output will result in a point/multipoint feature class called "bar_ProcedurallyGeneratedPoints" or "bar_ProcedurallyGeneratedMultipoints".
- If "foo" has a CGA rule attached which produces edges (e.g. by comp(e)), its output will result in a polyline feature class called "bar_ProcedurallyGeneratedLines".
Copyright ©2008-2017 Esri R&D Center Zurich. All rights reserved.