The layer's data source is imported as a new feature class into the analysis geodatabase for the current analysis (CVAnalysis.mdb, or CVAnalysis.gdb). The original data source is not modified or deleted.
The new feature class is assigned the same spatial reference and projection as was specified for the original layer.
A default spatial index grid size will be calculated for the new feature class. This will be optimized for the spatial reference, average feature size, and number of features in the input shapefile or coverage.
If the original layer is not a geodatabase layer (e.g. shapefile, coverage), an appropriate extent for the new feature class will be determined. The extent will be created by unioning the visible extent and the map's full extent - this equals the full extent if the user is zoomed in or the full visible (zoomed out) extent if the user has zoomed out beyond the full extent. Note: having reference layers with a very large extent loaded while creating a dynamic layer, will result in lower precision for spatial measurements and calculations for the dynamic layer.
Some field names from the original data source may be invalid for a geodatabase feature class. Field names will be modified if necessary. A message will be displayed to inform you of any modifications.
Note: Scenario 360 supports multiple scenarios in each analysis. When creating 3D scenes for multiple scenarios, you need only create the terrain and drapes one time - they can be used in all scenarios. However, the 3D legend for each dynamic layer must be created for EACH scenario. In addition, if you build a layer and later make that layer dynamic, you must rebuild the 3D legend for that layer in the 3D scene. For more information, see Special considerations when working with SiteBuilder 3D and Scenario 360.
