"Build Mosaic Dataset" introduces building mosaic datasets and managing images by adding image files in formats such as *.img, *.tif, *.tiff.
The mosaic dataset also supports managing Level 1B sensor-corrected satellite imagery products through metadata management, i.e., by adding satellite image metadata files.
Supported Level 1B Sensor-Corrected Products
Currently, mosaic datasets only support managing Level 1B sensor-corrected products from the following satellite series. The Satellite ID (spacecraftID) field in the table below serves as SuperMap's identifier for satellite types or sensor types.
| Satellite Series | Satellite ID (spacecraftID) | Sensor ID |
| GF Series | GF-1 PMS | PMS |
| GF-1 WFV | WFV | |
| GF-2 | PMS1, PMS2 | |
| GF-6 PMS | PMS | |
| GF-6 WFV | WFV | |
| GF-7 | BWD, DLC | |
| GF-DM | PMS | |
| SuperView Series | SuperView-1 | PAN, MUX |
| SuperView Neo-1 | ||
| ZY Series | ZY1-02C | HRC |
| ZY1-02D (ZY1E) | VNIC | |
| ZY3-03 | DLC, MUX, NAD, PMS, TMS | |
| BJ Series | BJ-2 | MS, PAN |
| BJ-3A | MS, PAN | |
| BJ-3N | MS, PAN | |
| JL Series | JL1-GF | PMS |
| JL1-KF | PMS | |
| JL1-DP | PMS | |
| JL1-GP | PMS | |
| JL1-01A | PMS | |
| TH Series | TH-01 | GFB |
| JB Series | JB-01 | CCD |
| Chengdu Guoxing Aerospace | XSD | |
| PeruSat-1 | PeruSat-1 | MS |
| IKONOS | IKONOS | MUX, PAN |
| WorldView Series | WorldView-1 | MSI, PAN |
| WorldView-2 | ||
| WorldView-3 | ||
| WorldView-4 | ||
| Pleiades-1 | P, MS | |
| GeoEye-1 | MSI, PAN | |
| KOMPSAT Series | KOMPSAT-2 | MSC |
| KOMPSAT-3 | AEISS |
Add Satellite Image Metadata Files
To manage Level 1B sensor-corrected satellite imagery in mosaic datasets, use GPA tools. Both the "Build Mosaic Dataset" tool and "Add Images to Existing Mosaic Dataset" tool under Toolbox/"Image Management"/"Build Mosaic Dataset" can add satellite image metadata files. Refer to tool help for parameters, with emphasis on:
- Grid Type: Specify satellite type/sensor type for proper metadata parsing. Use corresponding "Satellite ID (spacecraftID)" values from the above table.
- Image File: Specify satellite image metadata files with extensions .xml, .dim, .txt, or .eph in "Image Files" or file list parameters.
Note:- Mosaic datasets cannot add satellite imagery without independent RPC files when using satellite type/sensor type metadata.
When adding metadata files, mosaic datasets read and store metadata in attribute tables, creating fields for satellite sensor info, orbit number, sensor azimuth, cloud coverage, solar angles, etc.
Different satellite sensors have varying metadata formats. SuperMap creates unified metadata fields by default, which may not cover all information or match actual metadata fields, causing incomplete extraction. To address this, SuperMap provides configurable metadata extraction through configuration files.
Custom Metadata Configuration File
File Location
Configuration file: CustomizedMetaData.xml (fixed name) at SuperMap iDesktopX installation directory/bin/Resource/RemoteSensing/.
Modify this XML file only when needing custom metadata fields for specific satellite types/sensors.
File Content
CustomizedMetaData.xml contains commented examples. Below shows how to configure custom fields and metadata extraction:
Uncommented example:
(1) Custom Metadata by Sensor Type
Each <Sensor spacecraftID=""> </Sensor> pair defines metadata extraction for one sensor type. Use "Satellite ID (spacecraftID)" values from the support table.
(2) Custom Fields and Metadata Extraction
Each <Sensor> can contain multiple <FieldMetaData> elements defining new metadata fields. Attributes include:
- FieldType: Data type (Text/Int64/Double/DateTime)
- Size: Field length (optional)
- Alias: Field name (defaults to source metadata field name if empty). Matching default field names will overwrite original values.
The element value specifies metadata field path. Below explains path determination for different formats:
XML Metadata
For XML files (e.g., GF-1 WFV .xml), use absolute XPath with "." separators. Example: ProductMetaData.Bands for <Bands> node.
Text Metadata
For text files (e.g., KOMPSAT-2 .eph), use key paths with "." separators. Example: AUX_PROJECTION_PARAMETER for root-level keys.
Note:- When multiple identical metadata fields exist, the last occurrence's value will be extracted.
(3) Save Configuration File
Changes in CustomizedMetaData.xml take effect immediately without restarting SuperMap iDesktopX. The system creates default fields and adds custom fields from the configuration during metadata import.