1Overview
Edit works against the selected parsed asset and maintains an in-memory change set. Clean addresses audit-identified normalisation or clean-up issues. Neither tool replaces the source file until the user exports an output.
An audit identifies supported field corrections or clean-up actions that should be applied in the Map Pro workbench.
2Editing and clean-up boundaries
Map Pro keeps working changes separate from the original source and exposes the export decision.
| Feature or choice | Current behaviour |
|---|---|
| In-memory edits | Nested property paths are changed in the parsed working object and recorded in a per-file change set.The browser does not silently overwrite the user's original file. |
| Global component fields | Recognises common values including Infrastructure Code, Owner, Drawing Number, Construction Date, Status and Data Quality.High-value shared fields are presented consistently. |
| Clean boundary | Clean handles supported audit-targeted normalisation; unsupported semantic corrections remain user decisions.Automation does not invent receiver or project meaning. |
3Correct controlled XML data
Select precisely, stage changes, export a new file and audit the output.
Select an asset or issue
Open Edit directly or route from Audit.
- Choose the uploaded file and asset.
- Review identity, type, status and flattened property paths.
- Confirm the field belongs to the intended asset before changing it.
Stage the correction
Changes remain in the workbench until export.
- Enter the supported value.
- Review the change-set entry and original value.
- Use Clean for issues assigned to normalisation rather than manual field editing.
Export and verify
Create a deliberate output.
- Export the change set when an audit trail is required.
- Export patched XML for the corrected deliverable.
- Upload the output separately and rerun Audit before replacing the controlled source.
4Before you begin
- Sign in with Map Pro access.
- Audit first when correction scope is not already known.
- Retain the original XML as the baseline.
5Product differences
The task is shared where possible, but selection, interface integration and model operations follow the host shown below.
Edit and Clean are authenticated Map Pro XML File Tools. Outputs must be exported and re-audited before controlled use.
6Troubleshooting
The required field is not editable
Confirm the current workbench exposes that property path. Make unsupported structural or schema corrections in the authoring system rather than forcing a text replacement.
The original XML did not change
That is expected. Export patched XML, then open the exported file as a separate review item.
A Clean action changes more than expected
Keep the original file, review the exported change set/diff and accept only an output whose changes are understood.