Map Document Migration
Feature Description
The map document migration function is used to convert ArcGIS map documents (MXD) to SuperMap workspace (SMWU) format. It includes two parts: one is data migration, for details please refer to Data Migration; the other is map document migration, which mainly converts information objects such as layers, features, labels, and symbols in the MXD by creating, writing, and setting the corresponding layers, features, symbols, and other objects through the interfaces provided by the SuperMap iObjects Java component, thereby completing the conversion from ArcGIS MXD to SuperMap SMWU.
The map migration function requires licensing for ArcMap related products.
Function Entry
- Data Migration tab ->ArcGISData Migration->Migrate MXD.
Parameter Description
- Source Dataset: Supports migrating multiple MXD data simultaneously. You can use the Add File and Add Folder buttons in the toolbar to select the MXD project files to be converted.
- Import Settings:
- Contains map: This checkbox is checked by default and cannot be changed.
- Containing data: This checkbox is checked by default to export the data in the MXD along with it. If data migration has already been performed, you can uncheck this checkbox.
- Import 3D Dataset: Check this option to import the 3D points, 3D lines, and 3D surfaces from the MXD's associated source data as corresponding 3D datasets; when unchecked, they are imported as corresponding 2D vector datasets. This is unchecked by default.
- Import map-related data only: Used to set whether to import only the data actually used in the map. This checkbox is unchecked by default. If checked, only the data associated with the map (i.e., used for cartography) will be imported, and other data will not be imported.
- Containing data must be checked to enable this option.
- The supported source data types are FileGDB (*.gdb), ArcGIS Personal GeoDatabase files (*.mdb), and ShapeFile files (*.shp). Source data in SDE databases is supported starting from version SuperMap iDesktopX 2025.
- Contains layout: This checkbox is unchecked by default. When checked, the layout in the MXD will be imported. Starting from version SuperMap iDesktopX 2026, the migration of text line spacing in layouts is supported.
- Check data: Checks the data before migration to determine whether its data types, layer structures, etc., meet the migration conditions. After the check, a result information list will be output, allowing you to view the errors in detail and handle problematic data according to the provided solutions.
Notes:- If Import map-related data only is checked, only the data associated with the map will be checked; if not checked, all data will be checked.
- If multiple MXD files are added, the data inspection operation will not be performed.
- Generate Migration Report: Check this checkbox to generate a migration report (*.xlsx file) in the same directory as the result data after migration, which is used to display the migration status. The report contains a total of five sub-sheets: Overview, Data, Map, Symbol, and Data Sampling. You can view the overview of successful migration counts, information comparison before and after migration, and reasons for migration failures in these sheets.
Notes:
- If the source data is SDE data and the Generate Migration Report option is checked during migration, the report does not support data comparison for SDE.
- License Verification: Data migration requires a license for ArcMap related modules. The program provides a Check button to verify whether the currently selected license is valid. If the required license is missing on the computer, a prompt will appear: "ArcGIS license loading failed, please check the license status." It is recommended to select Default. The license situations for Default are as follows:
- If the ArcMap version used on the computer is 10.4, 10.6, 10.7, or 10.8, the Default option will use the ArcServer license for verification;
- If the ArcMap version used on the computer is 10.2, 10.3, or 10.5, the Default option will use the Advanced license for verification.
- Charset: The default option is Automatic reading, where the system will automatically read the character set of the source data files associated with the MXD. If you need to change it, you can select other Charset types from the dropdown list.
- Result Datasource: Sets the storage method for the migration result datasource. It provides local UDBX and database datasource types:
Notes:
If the MXD to be converted contains data from a PostGIS database, it can be read directly without separate migration.
- Text: By default, it is stored in a text-based UDBX datasource. During migration, the program will create a new UDBX datasource in the result folder to store the migrated data;
- Database: Supports storage in database datasources. You can select database types such as SQLPlus, PostgreSQL, KingBase, MySQL, HighGoDB, PostGIS, DMSpatial, and DMPlus. For detailed instructions on creating a new database datasource, please refer to the New Datasource page.
- Result Workspace:
- Path: Sets the export directory for the result data.
- File Name: Sets the file name for the migrated SuperMap Workspace.
After the migration is complete, a pop-up window will ask whether to open the migrated workspace, and the path to the migration log file will be output in the output window. You can view detailed migration information in this file. The figure below shows a comparison of the effects before and after migration.
Related Topics