1.Overview
This guide describes how to migrate Multinational Geospatial Co-production Program (MGCP) Technical Reference Document (TRD) 4.x data to an MGCP TRD5 1:50,000 geodatabase and, optionally, load the migrated data into a TRD5 1:50,000 GeoPackage.
The workflow has two stages:
- Migrate source MGCP TRD4.x shapefiles or geodatabase data into an MGCP TRD5 1:50,000 geodatabase.
- Optionally, load the resulting TRD5 geodatabase into a TRD5 GeoPackage template.
The migration model applies the appropriate schema mappings and handles features affected by geometry changes between TRD4.x and TRD5. The Load Data tool applies the dataset, field, and value rules defined in the chosen cross-reference geodatabase.
Note: Perform the migration on working copies of the target databases and GeoPackage template. Do not load data directly into the installed product-file templates.
2.Prerequisites
Before starting, confirm the following:
• You installed ArcGIS Pro.
• You have a license for the ArcGIS Topographic Mapping extension.
• You installed the ArcGIS Topographic Mapping product files.
• The source MGCP TRD4.x data is available as either a directory containing MGCP
shapefiles or an MGCP TRD4.x geodatabase.
• The processing location has sufficient storage and write access.
• The correct cross-reference database is available for the source format.
2.1 Location paths:
The default MGCP product-files location is:
C:\Users\Public\Documents\ArcGIS Topographic Mapping\Product Files\Mgcp
The TRD5 migration resources are in:
C:\Users\Public\Documents\ArcGIS Topographic Mapping\Product
Files\Mgcp\DataConversion\TRD5
3.Required files
3.1 Source data
Use MGCP TRD4.x shapefiles or an MGCP TRD4.x geodatabase.
3.2 Target schemas and processing databases
Copy the following databases from the installed product files to the processing folder:
• MGCP_TRD5_50K.gdb
• MGCP_TRD5_Generalization.gdb
3.3 TRD4.x-to-TRD5 cross-reference databases
Choose the cross-reference database that matches the source format:
• Shapefile source: MGCP_TRD4_x_SHP_to_MGCP_TRD5_All_ext_GDB.gdb
• Geodatabase source: MGCP_TRD4_x_GDB_to_MGCP_TRD5_All_ext_GDB.gdb
Migration also requires the cross-reference database used to load the intermediate TRD5 schema into the TRD5 1:50,000 schema:
MGCP_TRD5_50K_GDB_to_MGCP_TRD5_50K_GDB.gdb
Verify the installed filename before running the migration because product filenames can vary by release.
3.4 Optional GeoPackage resources
To create a GeoPackage deliverable, copy the following files to the processing folder:
• MGCP_TRD5_50K_GDB_to_MGCP_TRD5_50K_Geopackage.gdb
• TRD5-50k_GPKG_Template_v1.0.5.gpkg
Verify the GeoPackage template version and cross-reference database names against the installed product files.
4.Prepare the processing workspace
Caution: Keep the original TRD4.x source data unchanged
- Create a dedicated processing folder.
- Copy MGCP_TRD5_50K.gdb, MGCP_TRD5_Generalization.gdb, the applicable TRD4.x-to-TRD5 cross-reference database, and the TRD5 1:50,000 cross-reference database into that folder. If a GeoPackage deliverable is required, also copy its cross-reference database and template.
- Confirm that none of the copied target workspaces are read-only.
- Preserve an unchanged backup of each empty target database and template.
5.Migrate MGCP TRD4.x data to the TRD5 1:50,000 geodatabase
5.1 Open the migration toolbox
- Start ArcGIS Pro and open or create a project.
- Add a folder connection to the processing folder.
- Add a folder connection to the installed MGCP product-files directory.
- Browse to
C:\Users\Public\Documents\ArcGIS Topographic Mapping\Product
Files\Mgcp\DataConversion\TRD5. - Open the MGCP TRD4.x-to-TRD5 migration toolbox.
- Open the Load MGCP TRD4x to TRD5 model.
5.2 Configure the migration parameters
- Input TRD4.x source data: For shapefiles, choose the folder containing the extracted MGCP shapefiles. For a geodatabase, choose the MGCP TRD4.x geodatabase.
- Generalization database: Choose the MGCP_TRD5_Generalization.gdb working copy.
- TRD4.x-to-TRD5 All Extended mapping: Choose the shapefile or geodatabase cross-reference database that matches the source format.
- TRD5 All Extended-to-TRD5 1:50,000 mapping: Choose the cross-reference database provided for loading the intermediate TRD5 schema into the TRD5 1:50,000 schema.
- Target TRD5 1:50,000 geodatabase: Choose the MGCP_TRD5_50K.gdb working copy.
- Review the parameter values and confirm that the source type matches the chosen cross-reference database.
5.3 Run the migration
- Run the model.
- Monitor the geoprocessing messages for warnings and errors.
- Save or export the processing messages for the migration record.
The model maps TRD4.x datasets, fields, and values into the TRD5 schemas. It also processes features whose geometry representation changed between TRD4.x and TRD5.
6.Validate the TRD5 geodatabase
Complete these checks before creating a GeoPackage or using the data in production:
- Confirm that the expected TRD5 feature classes exist.
- Compare source and target feature counts by thematic group or feature code.
- Review warnings for missing or inaccessible source datasets.
- Review warnings for missing target datasets.
- Inspect features affected by geometry changes.
- Confirm that required identifiers and attribution are populated.
- Check coded values and mapped attributes for unexpected null or default values.
- Inspect representative point, line, and polygon features.
- Run the applicable TRD5 validation rules or organizational quality-control checks.
- Record all unmapped, skipped, or failed features for follow-up.
Note: A difference between source and target feature counts does not automatically indicate data loss. A single TRD4.x source class may map to multiple TRD5 target classes, and geometry migration can change the number or representation of output features.
7.Load the TRD5 geodatabase into a TRD5 GeoPackage
Complete this section only when a GeoPackage deliverable is required.
7.1 Open the Load Data tool
- In ArcGIS Pro, open the Geoprocessing pane.
- Browse to Topographic Production Tools.
- Open Data Management.
- Open Geodatabase.
- Open Load Data.
7.2 Configure the parameters
- Input Cross-reference Database: Choose MGCP_TRD5_50K_GDB_to_MGCP_TRD5_50K_Geopackage.gdb
- Input Sources: Choose the validated MGCP TRD5 1:50,000 geodatabase produced by the migration.
- Input Target Workspace: Choose the TRD5-50k_GPKG_Template_v1.0.5.gpkg working copy.
7.3 Run the load
- Confirm that the target GeoPackage is not open in another app.
- Run the Load Data tool.
- Review all geoprocessing messages.
- Save or export the messages with the migration record.
The tool applies the mappings in the cross-reference database and loads the TRD5 geodatabase features into the corresponding layers in the TRD5 GeoPackage.
8.Validate the GeoPackage
Complete these checks before you deliver the GeoPackage:
- Add the GeoPackage layers to a new map.
- Confirm that all expected layers are present.
- Compare feature counts between the TRD5 geodatabase and GeoPackage.
- Review representative point, line, and polygon features.
- Confirm that required attributes and identifiers are retained.
- Check for null values, truncated text, invalid geometries, or unexpected defaults.
- Confirm that the GeoPackage opens successfully outside the migration project, if required by the delivery workflow.
- Preserve the processing messages and validation results with the final deliverable.
9.Migration record
Record the following information for traceability:
• Source data location and TRD version
• Versions of ArcGIS Pro and ArcGIS Topographic Mapping product files
• Chosen cross-reference databases
• Migration run date and operator
• Processing warnings and errors
• Validation result and unresolved exceptions
10.Troubleshooting
10.1 Source dataset not found or inaccessible
• Confirm that the input workspace points to the directory containing the shapefiles or to the correct geodatabase.
• Confirm that the expected source datasets exist.
• Verify that dataset names match the cross-reference database.
• For shapefiles, confirm that all component files are present.
10.2 Target dataset not found or inaccessible
• Confirm that you copied the correct TRD5 target schema from the product files.
• Confirm that the target workspace has not been renamed or structurally modified.
• Verify that the chosen cross-reference database matches the target schema and release.
10.3 Features are missing after migration
• Review the geoprocessing warnings.
• Confirm that you chose the correct shapefile or geodatabase cross-reference database.
• Check whether the source dataset is represented in the cross-reference database.
• Check for mapping conditions that exclude source features.
• Review geometry-migration outputs for features whose representation changed.
10.4 Attributes are null or mapped incorrectly
• Confirm that the source schema matches the chosen cross-reference database.
• Review the field and value mappings.
• Check whether required source values are null, invalid, or outside the mapped value set.
• Verify exact dataset and field names where custom mapping files are used.
10.5 GeoPackage is locked or cannot be written
• Close maps, catalog views, and external applications using the GeoPackage.
• Confirm that the file is not read-only.
• Create a fresh working copy of the template and rerun the load.
11.Migration completion criteria
The migration is complete when:
• The TRD5 1:50,000 geodatabase contains the TRD4.x source data.
• You reviewed all processing warnings and errors.
• You validated the expected datasets, attributes, and geometry changes.
• You documented unmapped or failed features and resolved or accepted them.
• You populated and validated the optional GeoPackage, if required.
• You retained the original source data, working outputs, processing messages, and validation results.