The world's topographic data used by more than 30 member nations has been produced against a single, stable specification for years. This specification is now modernizing and ArcGIS Topographic Mapping is ready for it.
The Multinational Geospatial Co-production Program (MGCP) is an international collaboration focused on producing and sharing authoritative geospatial data. For more than a decade, nations have used the MGCP Technical Reference Documentation (TRD) 4.x specification as the common framework for data production. As production requirements and technology have evolved, the MGCP community is now developing TRD 5.0, the next generation of the specification designed to support modern geospatial workflows.
The move to MGCP TRD 5.0 will modernize that foundation, but modernization only helps if organizations can bring their existing data with them. While the full TRD 5.0 specification and its extraction guide are still being finalized, ArcGIS Topographic Mapping now provides early support for TRD 5.0 at the ArcGIS Pro 3.8 release. It delivers the geodatabases, migration resources, GeoPackage templates, and automated generalization tools that member nations, defense and civilian mapping authorities, and their contractors, need to migrate TRD 4.x and MGCP Urban Vector Data (MUVD) data to TRD 5.0 and prepare for multi-scale production.
Why this matters now
Demand has been growing. Moving TRD 4.x data to TRD 5.0 is the first capability the MGCP community asked Esri for, and interest in TRD 5.0 generalization was a recurring theme in recent customer conversations. Collecting new data to TRD 5.0 will follow once the extraction guide is complete. TRD 4.6 has been the standard for years. TRD 5.0 is the first structural change to the MGCP data model in a long time and it is a significant one.
The tools ship where customers work. These resources are delivered in the ArcGIS Topographic Mapping product files, ready to drop into existing production environments.
Why the flat model helps
A one-feature-class-per-FCODE structure is easier to understand, load, and exchange. It also maps cleanly to delivery formats such as shapefiles and GeoPackage, where each layer already represents a single feature type. This is the same modernization approach Esri applied to the Topographic Data Store (TDS) 7.1 Flat model.
A note on GeoPackage
Several deliverables center on GeoPackage. A GeoPackage (.gpkg) is an open, non-proprietary Open Geospatial Consortium (OGC) standard that stores geospatial data—vector features, raster tiles, and attribute tables—inside a single, self-contained SQLite database file.
- Portable and self-describing—One file carries everything, making it well-suited to the disconnected, cross-organization exchange that defines MGCP's mission.
- A modern successor to the shapefile—GeoPackage avoids the fragility of the multi-file shapefile format and was designed with U.S. military backing precisely for this kind of standards-based sharing.
- A natural fit for the coalition—Platform-independent delivery aligns with sharing data across the 30+ nations through the International Geospatial Warehouse (IGW).
At the ArcGIS Pro 3.8 release, the TRD 5.0 GeoPackage templates are available for the MGCP community to load data into. A tool for exporting data to GeoPackage is planned for a later release.
What's included
TRD 5.0 Geodatabases
- MGCP_TRD5_5K
- MGCP_TRD5_50K
- MGCP_TRD5_250K
- MGCP_TRD5_Generalization geodatabase
Data migration resources
- MGCP_TRD4 Geodatabase → MGCP_TRD5 mapping files
- MGCP_TRD4 Shapefile → MGCP_TRD5 mapping files
- MUVD → MGCP_TRD5 5K mapping file
- MGCP_TRD5 All Extended → MGCP_TRD5 50K mapping files
- MGCP_TRD5 Geodatabase → GeoPackage mapping files
How migration works: Migration runs in two stages. First, TRD4.x shapefiles or geodatabase data are migrated into a TRD5 geodatabase; target geodatabases are provided for each scale—1:5,000, 1:50,000, and 1:250,000. MUVD data maps to the TRD5 1;5,000 geodatabase. The migration model applies the schema mappings and handles features affected by geometry changes between TRD4.x and TRD5. Second, the TRD5 geodatabase can optionally be loaded into a TRD5 GeoPackage template.
What you need: ArcGIS Pro, an ArcGIS Topographic Mapping extension license, and the installed ArcGIS Topographic Mapping product files.
Where to find it: The TRD5 migration resources are installed with the product files in the Product Files\Mgcp\DataConversion\TRD5 folder. Always work on copies of the target geodatabases and templates—never the installed originals.
Visit Migrate MGCP TRD4.x data to TRD5 for guidance that uses the 1:50,000 map scale as an example.
Geometry migration tools
The included MGCP TRD4x to TRD5 Migration Tools toolbox (.atbx) supports migration of geometry changes introduced in TRD 5.0, helping preserve TRD 4.x feature content during conversion and loading workflows.
GeoPackage support
- MGCP_TRD5 GeoPackage templates (5K, 50K, and 250K)
- GeoPackage implementation resources
- Standardized structure for loading TRD 5.0 data into GeoPackage.
Automated generalization
- Preconfigured TRD 5.0 50K to 250K generalization rule file
- Derive 250K products from authoritative 50K source data
- Supports repeatable, standardized multi-scale production workflows
Benefits
- Streamlines migration from existing TRD 4.x and MUVD data holdings
- Provides standards-based GeoPackage templates for TRD 5.0 data
- Preserves geometry complexity during migration
- Accelerates implementation of TRD 5.0 production environments
- Enables automated derivation of 250K data from 50K source content
- Provides a standardized foundation for future MGCP production and maintenance workflows
At a glance: Included deliverables
# | Deliverable | Category |
|---|
1 | MGCP_TRD5 5K geodatabase | Geodatabases |
2 | MGCP_TRD5 50K geodatabase | Geodatabases |
3 | MGCP_TRD5 250K geodatabase | Geodatabases |
4 | MGCP_TRD5 Generalization geodatabase | Geodatabases |
5 | MGCP_TRD4 Geodatabase → MGCP_TRD5 mapping files | Migration |
6 | MGCP_TRD4 Shapefile → MGCP_TRD5 mapping files | Migration |
7 | MUVD → MGCP_TRD5 5K mapping file | Migration |
8 | MGCP_TRD5 All Extended → MGCP_TRD5 50K mapping files | Migration |
9 | MGCP_TRD5 GeoPackage templates (5K, 50K, and 250K) | GeoPackage |
10 | MGCP_TRD5 Geodatabase → GeoPackage mapping files | GeoPackage |
11 | MGCP TRD4x to TRD5 Migration Tools toolbox | Migration tools |
12 | 50K → 250K generalization rule files | Generalization |
Abbreviations and more
Item | Details |
|---|
MGCP | Multinational Geospatial Co-production Program |
TRD | Technical Reference Document |
MUVD | MGCP Urban Vector Data |
TDS | Topographic Data Store |
FCODE | Feature code |
OGC | Open Geospatial Consortium |
GeoPackage (.gpkg) | OGC official open standard file format |
NGA | National Geospatial-Intelligence Agency |
IGW | International Geospatial Warehouse |