Load data into a geodatabase

Disponible avec une licence Production Mapping.

With ArcGIS Production Mapping, you can load data into a geodatabase using a template that corresponds to the data model or product specification you are using. This template is a cross-reference geodatabase and contains mapping information between the data being loaded from the source workspace and the target database. The cross-reference geodatabase contains information that controls mapping information between the source workspace and target database. This includes the source features that need to be loaded into a target database with WHERE clauses and, if applicable, the appropriate subtype. It also contains tables that define field mapping and value substitution.

Using the Load Data tool, you can load data from one geodatabase, coverages, or set of shapefiles into another geodatabase that may or may not have the same schema. This can append data to existing databases or load it into an empty schema. At a minimum, the target database must contain the schema referenced in the cross-reference geodatabase.

1. Browse to all of the following:
   • Cross-reference geodatabase
   • Source workspace
   • Target database
   • Output location for the log file created

   Providing this information sets up the mapping information between the data that is going to be loaded and the database into which the data is going to be loaded. The log file is generated as a text file that contains the results of the loading process for each subtype.

2. Choose the feature classes to load into the target database.

   You can load some or all of the features from the source workspace.

3. Perform the dataset mappings in the cross-reference geodatabase.

   You can choose to perform all of the dataset mappings in the cross-reference geodatabase or a subset.

   Remarque :

   When the schema of the source workspace and the target database don't match, a mapping file template included in the Production Mapping product files is used rather than the actual feature classes contained in the source or target.

   After the data is loaded, a log file of the results is generated that allows you to review the number of features that have been loaded.

4. Verify that the datasets listed in the mapping file template match the feature classes in the source workspace and target database.
5. Verify that the fields listed in the mapping file match the fields in the source workspace and target database.