Esri FileGDB is a file-based database with support for many GIS data types such as points, lines, polygons, 3d geometry (multipatch), raster and more. It is the recommended way to exchange GIS data between Esri applications such as CityEngine and ArcGIS Pro.
CityEngine supports the export of datasets of the types "FeatureClass", "Table" and "Relationship Class".
In addition to the general export options, FileGDB has the following options:
The name of the geodatabase directory. The ".gdb" suffix is mandatory.
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
Any reports generated by the attached CGA rule will be written into feature class fields.
In addition to the global export options, the FileGDB exporter contains an additional export page with the following per-layer settings:
Include or exclude any selected layers from export.
Adjust the name of the selected layers. This will determine the name of the written FileGDB dataset(s).
Choose how existing feature classes are handled:
Geometry Type (for Shapes)
Choose the geometry type for the shapes:
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 you export a shape "wall" of layer "building", you get the following:
- In case of Export Features set to Shapes or Models and Shapes, the shape wall will be directly written to the building feature class.
- If wall has a CGA rule attached which produces polygons, its output will result in a building_ProcedurallyGeneratedMultipatches multipatch feature class.
- If wall has a CGA rule attached which produces points (e.g. by comp(v)), its output will result in the building_ProcedurallyGeneratedPoints or building_ProcedurallyGeneratedMultipoints point/multipoint feature class.
- If wall has a CGA rule attached which produces edges (e.g. by comp(e)), its output will result in the building_ProcedurallyGeneratedLines polyline feature class.