Function Description
ArcGIS Map Documentation MXD
MXD is the map document file of ArcGIS, which can save the configured map and layout information, including layer, symbol, annotation, scale, Visible Bounds and other information. ArcGIS stores a large number of cartographic expression information through MXD files, and uses MXD to manage the configuration information in a unified way. When Publish Map Service is needed, MXD is also needed.
SuperMap Workspace SMWU
The Workspace of SuperMap corresponds to the map document MXD of ArcGIS, and the Workspace will save the user's operation results, including the Datasource opened in the Workspace, the saved map, the layout, and the 3D Scene. When Open Works pace again, you can continue to work on the results of the previous work. SuperMap Workspace is stored in either *.smwu or *.sxwu format. For a Detail Description of Workspace, see the Workspace page.
Map Migration principle
Map document migration includes two parts: one is data migration. For details, see Data Migration ; The other part is the migration of map documents, which mainly completes the creation, writing and setting of corresponding layers, features, labels, symbols and other information objects in MXD through the iObjects Java component interface provided by SuperMap. Thus completing the conversion from MXD of ArcGIS to SMWU of SuperMap.
Elements that support migration
- Symbol: supports the conversion of different types of points, lines and Fill symbols in ArcGIS to the Symbol Type corresponding to SuperMap, and the symbols are consistent in Display Effects; Multiple Convert of symbol library files (*.style format) provided by ArcGIS to symbol library files corresponding to SuperMap is also supported. For detailed description of symbol migration, please refer to Symbol Migration .
- Annotation: Support the restoration of ArcGIS map annotation through SuperMap Thematic Label Map, so that the annotation display style is consistent, and the display priority of annotation is synchronized through capping and avoidance settings. For a detailed description of dimension migration, see Dimension Migration .
- Thematic Map: The thematic map in the ArcGIS map can be converted to the Themtic Type corresponding to the SuperMap, so that the Display Effects of the thematic map are consistent. For the detailed description of thematic map migration, please refer to Thematic Map Migration .
- Raster Image: support the Stretch method of converting image Raster Data in ArcGIS map. Stretch types that can be converted include: Minimum Maximum, Standard Deviation, Histogram Equalization, and Percent Clip. After conversion, the Stretch Display effect of Raster is the same. For a detailed description of matching by Grid Image Stretching, see Grid Image Stretching Matching .
Caution: The Map Migration function requires the Licensing of ArcGIS related products.
Function entrance
- Data Migration tab-> Data Migration-> Migrate MXD.
Parameter Description
- Source data: Support simultaneous migration of multiple MXD data. You can select the MXD project file to be converted through the Add File and Add Folder buttons in the toolbar.
- Import Settings：
- Contains map: This check box is checked by default and cannot be changed.
- Containing Data: This check box is checked by default to export the data in MXD together. If Data Migration has been performed, this check box can be unchecked.
- Only import map Link Dara: This check box is not checked by default. If it is checked, only the data associated with the map, that is, the data used for mapping, will be imported, and the rest of the data will not be imported.
- Contains layout: This check box is not checked by default. If it is checked, the layout in MXD will be imported.
- Check Data: before Data Migration, it is supported to check whether the migration data meets the migration conditions according to the data category, Layer type and other Data Information of the source data; The Result Info list will be output after the check, and the user can view the Errors in detail and process the problem data according to the Solution provided. If more than one MXD file is added, the Check Data operation is not performed.
- Generate Migration Report: Select this check box to Generate Migration Report. Including coordinate system before and after migration, Map Name, number of Dataset, number of objects, Select Fields, etc.
- License Verification: Data Migration requires a license for ArcGIS related modules. The program provides a Check button to verify whether the currently selected license is valid. If the required license is missing in the computer, it will prompt: "ArcGIS License loading failed." Please check the license status. It is recommended to select Default, and the license conditions of Default are as follows:
- If the ArcGIS version on the computer is 10.4, 10.6, 10.7, or 10.8, the Default option is validated with the ArcServer license;
- If the computer is using ArcGIS version 10.2, 10.3, or 10.5, the Default option is validated using Advanced's license.
- Character set: Set the corresponding character set type according to the character set of the MXD associated source data file.
- Result Datasource: Set the way to migrate the Result Datasource storage, and provide the local UDBX and database Datasource Type:
- Text type: stored in the text type 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 the database Datasource, and can select database types such as SQLPlus, OraclePlus, MySQL, PostgreSQL, PostGIS, MongoDB, and DMPlus. See the Create Datasource page for a detailed description of the Create Database Datasource.
Caution: If the MXD to be converted contains data from PostGIS database, direct reading is supported without separate migration.
- Result Workspace：
Path: Set the Export Directory of Result Data.
File Name: Set the File Name of the SuperMap Workspace after migration.
Show Result
After the migration is completed, the program will automatically open the successfully imported Workspace. The following figure shows the comparison of the effects before and after the migration.
Related content