FAQ: Does Esri CityEngine have a spatial data extent limit?
Does Esri CityEngine have a spatial data extent limit?
Yes, Esri CityEngine has a spatial data extent limit. A single Esri CityEngine scene has a data extent limit within the range of hundreds of kilometres. A dataset cannot be imported to an Esri CityEngine scene if its spatial data extent is higher than the scene's data extent limit. A new dataset, although diminutive, cannot be imported to an Esri CityEngine scene if the data extent of the existing dataset in the scene is close to the scene's data extent limit.
Attempting to import a file geodatabase with a large data extent to an Esri CityEngine scene may return the following errors:
Error: The data extent is too large. Reduce the extent of the data.
Error: The combined extent of the existing scene and the selected layers is too large: [x,y,z]
To avoid this, split the data from the single file geodatabase into multiple file geodatabases in ArcMap or ArcGIS Pro, and import the file geodatabases to multiple Esri CityEngine scenes. To do so, follow the instructions described below.
In ArcMap or ArcGIS Pro
- Create multiple empty file geodatabases. To do so, refer to ArcMap: Create a file geodatabase or ArcGIS Pro: Create a file geodatabase.
- Export the feature classes into the file geodatabases. Refer to ArcMap: Exporting feature datasets, classes and tables or ArcGIS Pro: Export data in a geodatabase for more information.
In Esri CityEngine
- Create multiple scenes in Esri CityEngine.
- Import each new file geodatabases to each scene.
Note: If the dataset in a single file geodatabase exceeds the Esri CityEngine's spatial data extent limit, clip the dataset to smaller extents, and export each clipped data to a new file geodatabase. Refer to ArcMap: Clip or ArcGIS Pro: Clip for more information.
- Esri CityEngine Resources: Tutorials overview
- Esri CityEngine Resources: Tips and shortcuts
- ArcGIS Blog: CityEngine 2019.1 Release Highlights