Instructions for use
The Map Document Migration function is used to convert ArcGIS map documents (MXD) into the SuperMap workspace (SMWU) format. It consists of two main parts. One is data migration; for details, please refer to Data Migration. The other part is map document migration, which primarily involves creating, writing, and setting corresponding objects like layers, features, and symbols in SuperMap. This is done through the iObjects Java component interfaces provided by SuperMap to handle the information objects such as layers, features, labels, and symbols from the MXD, thereby completing the conversion from ArcGIS MXD to SuperMap SMWU.
The map migration function requires licensing for relevant ArcMap products.
Function Entrance
- Data Migration Tab -> ArcGIS Data Migration -> Migrate MXD.
Parameter description
- Source Dataset: Supports migrating multiple MXD datasets simultaneously. You can use the Add File or Add Folder buttons on the toolbar to select the MXD project files to be converted.
- Import Settings:
- Contains map: This checkbox is selected by default and cannot be changed.
- Containing data: This checkbox is selected by default, which exports the data within the MXD along with the map. If you have already performed data migration, you can uncheck this box.
- 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 data associated with the map (i.e., data used for cartography) will be imported, and other data will not be imported.
- Containing data must be checked to enable this option.
- Supported source data types are FileGDB (*.gdb), ArcGIS Personal GeoDatabase files (*.mdb), and ShapeFile files (*.shp). Support for source data in SDE databases begins with SuperMap iDesktopX 2025 version.
- Callout to CAD: To ensure that labels and text with leader lines are displayed correctly after migration, you can check this option to set them to be converted into a CAD dataset after migration. It is unchecked by default.
- Contains layout: This checkbox is unchecked by default. Checking it will import the layout from the MXD.
- Check data: Performs a data check before migration to determine if the data type, layer structure, etc., meet the migration conditions. After the check, a result information list will be output. You can view errors in detail and handle problematic data based on the provided solutions.
Note:- If Import map-related data only is checked, only data associated with the map will be checked. If unchecked, all data will be checked.
- If multiple MXD files are added, the data inspection operation will not be performed.
- Generate Migration Report: If this checkbox is selected, a migration report (*.xlsx file) will be generated in the same directory as the result data after migration to display the migration status. The report contains five sub-tables: Overview, Data, Map, Symbol, and Data Sampling. You can view information such as the overview of successfully migrated items, comparisons of information before and after migration, and reasons for migration failures in these tables.
Note:
- If the source data is SDE data and you choose to generate a migration report during migration, the report does not support data comparison for SDE.
- License Verification: Data migration requires a license for the relevant ArcMap modules. The program provides a Check button to verify if the currently selected license is valid. If the required license is missing on the computer, the message "ArcGIS license loading failed, please check the license status" will appear. It is recommended to select "Default". The license status for Default is 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 Read Automatically, where the system automatically reads 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 how the migrated result datasource is stored, providing local UDBX and database datasource types:
Note:
If the MXD to be converted contains data from a PostGIS database, it can be read directly without separate migration.
- Text: Stored in a text-based datasource UDBX by default. During migration, the program will create a new UDBX datasource in the result folder to store the migrated data.
- Database: Supports storage in a database datasource. You can choose 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 SuperMap Workspace after migration.
After migration is complete, a pop-up will prompt 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