Select to view content in your preferred language

Best Practice for converting 2D to 3D for a File Geodatabase

311
0
10-21-2024 06:54 AM
sondickerson
Occasional Contributor

I'm looking for best practices for converting a 2D file geodatabase to 3D.  The file geodatabase contains 40 point, line and polygon feature classes and related table data.  Some of the feature classes have attachments and most of the feature classes and tables have a domains.  

Here's what has worked for us, but would like to see improvements if possible:

1) Create new mobile file geodatabase (the mobile fgdb will allow the preservation of the globalids when migrating the data).  Set up feature datasets to make it easier to assign globalids and editor tracking.  Datasets need to be set up with the correct coordinate system and vertical coordinate system.

2) Using a python script with arcpy.management.CreateFeatureclass, create the new feature classes from the 2D database, importing the fields from the original feature classes.  In the script assign the Coordinate System and Vertical Coordinate system.  Set the 'has_z' to ENABLED

3) Using a python script, copy the related tables (filter out the data)

4) Turn on the globalids and editor tracking at the dataset 

5) Using a python script, rebuild relationship classes

6) Using a python script, enable attachments for all of the feature classes that originally required them.

7) Using Arcgis Pro, Set up Domains – Copy the domains from the 2d database – paste into the 3D

😎 Using Arcgis Pro - Match up every FC and Table Columns with their domains and match the domain split policy from the original 2D

9) Using a python script - Delete any existing data in the 3D mobile database.  This is done to make it easier to test the migration process, verify the migration, and remove any test data for the actual run.

10) Migrate Data - Using Python script with arcpy.management.Append and arcpy.ddd.UpdateFeatureZ.  For each feature class and table append data from original to new database with Preserve globalids set to true.  Update the Feature Z using a 3D surface.

 

Please let me know how this can be improved.  Steps 7 and 8 are manual - I didn't see a way to script the transfer of feature class domain properties.  If you know of a way, that would be helpful.

Thanks in advance.

 

 

 

 

 

Tags (2)
0 Kudos
0 Replies