Feature Description
Map migration consists of two parts. One part is the migration of data, for more details please refer to Data Migration; the other part is the migration of map documents, mainly converting the layers, features, annotations, symbols, and other information objects in MXD files into corresponding objects like layers, features, and symbols in SuperMap via the iObjects Java component interface provided by SuperMap, thus completing the conversion from ArcGIS's MXD to SuperMap's SMWU.
The map migration feature requires a valid license for ArcGIS-related products.
Feature Entry
- Data Migration tab -> Data Migration -> MXD Migration.
Parameter Description
- Source Data: Supports migrating multiple MXD files simultaneously. You can choose MXD project files to be converted using the Add File and Add Folder buttons on the toolbar.
- Import Settings:
- Include Map: This checkbox is checked by default and cannot be modified.
- Include Data: This checkbox is checked by default, exporting the data in the MXD. If data migration has already been performed, you can uncheck this option.
- Import Only Map-Related Data: This checkbox is unchecked by default. It must be checked with Include Data enabled, and if checked, only map-related data used in map production will be imported. Other data will not be imported. Supported source data types include FileGDB (*.gdb), ArcGIS Personal GeoDatabase files (*.mdb), and ShapeFile files (*.shp). Starting from SuperMap iDesktopX (2025), source data from SDE databases is also supported.
- Include Layout: This checkbox is unchecked by default. If checked, the layout in the MXD will be imported.
- Check Data: Before migrating data, the system checks if the data meets the migration conditions based on the data type, layer type, and other information. After the check, a result list will be output where you can view error details and handle data issues based on provided solutions. Data check will not be performed if multiple MXD files are added.
- Generate Migration Report: If checked, a migration report will be generated, including information such as coordinate systems before and after migration, map names, number of datasets, object counts, field information, etc.
- License Verification: Data migration requires a valid ArcGIS module license. The program provides a Check button to verify whether the selected license is valid. If the required license is missing, a message will prompt: “ArcGIS License Load Failed, Please Check License Status.” It is recommended to select Default, and the licensing situation for Default is as follows:
- If the ArcGIS version is 10.4, 10.6, 10.7, or 10.8, Default will use the ArcServer license for verification;
- If the ArcGIS version is 10.2, 10.3, or 10.5, Default will use the Advanced license for verification.
- Character Set: Set the corresponding Character Set type according to the character set of the source data files related to the MXD.
- Result Datasource: Set the method of storing the migrated result data, supporting local UDBX and database datasource types:
Caution:If the MXD to be converted contains data from a PostGIS database, it can be directly read without separate migration.
- Text Type: By default, stored in the text-type datasource UDBX. The program will create a new UDBX datasource in the result folder to store the migrated data.
- Database Type: Supports storing in various database types such as SQLPlus, OraclePlus, MySQL, PostgreSQL, PostGIS, MongoDB, DMPlus, etc. For detailed instructions on creating a new database-type datasource, refer to Create Datasource Page.
- Result Workspace:
- Path: Set the output path for the result data.
- File Name: Set the file name for the SuperMap workspace after migration.
After migration is complete, a pop-up window will prompt you whether to open the migrated workspace, and the migration log file path will be shown in the output window. You can view detailed migration information in this file. The following image shows a comparison before and after migration.
Related Topics