1Overview
Compare selects a base and target file, matching recognised assets by identity and reporting attribute or presence changes. Merge/Split combines selected compatible working files or partitions one file into exported subsets.
Reviewing revisions, assembling compatible deliveries or creating smaller controlled files.
2File identity and compatibility
Multi-file tools rely on stable asset identity and compatible project/schema context.
| Feature or choice | Current behaviour |
|---|---|
| Identity comparison | Matches recognised assets by ADAC identity and reports attribute and file-presence changes.Revision review is based on asset records, not line order in the XML. |
| Merge compatibility | Requires compatible source context and preserves a deliberate selected-file set.Unrelated submissions are not safe to concatenate. |
| Split output | Partitions a selected register into new exported files while preserving source control.Large reviews can be divided without altering the original upload. |
3Control multi-file operations
Compare first, combine or partition deliberately, then audit every exported result.
Compare two files
Choose base and target deliberately.
- Open Compare.
- Select the earlier/baseline file and the target file.
- Review matched assets, source-only/target-only assets and changed attributes.
Prepare merge or split
Choose only files or groups that belong together.
- Open Merge/Split.
- For merge, select compatible files and review project/schema context.
- For split, select the source file and intended partition criteria.
Export and audit
Treat every result as a new deliverable.
- Export the comparison or resulting XML files.
- Open each result separately.
- Run Audit and confirm counts, identity and project metadata before distribution.
4Before you begin
- Sign in with Map Pro access.
- Upload every source file and keep originals.
- Confirm files belong to compatible schemas, projects and coordinate contexts before merging.
5Product differences
The task is shared where possible, but selection, interface integration and model operations follow the host shown below.
Compare and Merge/Split are authenticated Map Pro tools. Exported results should always be opened and audited as new files.
6Troubleshooting
Compare reports many source-only assets
Confirm base and target are the intended revisions and that stable ADAC identities were preserved. Regenerated IDs make record matching impossible.
Files cannot be merged
Compare schema version, project identity, coordinate information and duplicate ADACIds. Resolve incompatibilities before combining.
A split output is missing project context
Open the exported file and review project metadata. Use the authoring system when the requested partition cannot preserve a valid submission structure.