Supported Profiles
Reforge uses two tiers:
- Input Profile — how to interpret the CGM file (Application Structures, hotspots, companion files).
- Output Format — SVG version and structure of the converted file.
Input profiles
Auto-detect
Analyses the CGM file’s metafile descriptor and Application Structure conventions to pick the most appropriate profile. Reliable for clearly-profiled files; specify explicitly for edge cases.
WebCGM 2.1
| Standard | W3C Recommendation, 01 February 2010 |
| CLI flag | --profile webcgm |
Enables APS parsing for hotspots, layers, and metadata; hyperlink resolution; WebView viewContext adoption; XCF companion file merging.
Use when: Web-based tech doc systems; file explicitly identifies itself as WebCGM.
ATA iSpec 2200
| Standard | ATA iSpec 2200 — GREXCHANGE v3, IGEXCHANGE v4 |
| CLI flag | --profile ata |
| Users | Boeing, Airbus, OEMs, airlines, MROs |
Use when: Aircraft maintenance manuals (AMM), illustrated parts catalogs (IPC), component maintenance manuals (CMM).
S1000D
| Standard | S1000D Issues 4–6 |
| CLI flag | --profile s1000d |
| Users | Defence primes, military programmes, international aerospace OEMs |
Enables S1000D APS conventions, ICN Metadata File (IMF) companion merging, data-* attribute emission for IETP viewers.
Use when: File is part of an S1000D data module or defence programme.
CALS (MIL-PRF-28003B)
| Standard | MIL-PRF-28003B |
| CLI flag | --profile cals |
| Users | U.S. DoD, defence contractors |
Use when: DoD deliverable or U.S. military programme; file does not contain ATA or S1000D APS.
CGM+ (Extended WebCGM)
| CLI flag | --profile cgmplus |
| Users | Airbus, BAE Systems, NATO; Arbortext CSDB, PPT Technical Publisher |
Extends WebCGM 2.1 with NURBS curves, additional APS attribute namespaces, binary-only encoding.
Use when: European aerospace or NATO programme; metafile description contains CGM+.
Generic CGM
| Standard | ISO/IEC 8632:1999 |
| CLI flag | --profile generic |
Use when: File origin unknown; no Application Structures present; other profiles produce incorrect output.
Note
Without Application Structures, hotspot and metadata preservation is not possible.
PIP / CGGC (Petroleum Industry Picture)
| CLI flag | --profile pip |
| Users | Landmark, Halliburton, SLB/Schlumberger |
Handles indexed colour, no APS metadata, and very large VDC coordinate ranges (seismic scale).
Use when: Seismic section displays, well log graphics, geophysical visualizations.
Defaults (v0.6.0+): preserveApsScreenTip=true and preserveApsViewContext=true. When PIP source files carry APS screentip or view-context attributes (some modern PIP producers do), they are preserved in the SVG output rather than dropped. Prior releases defaulted both to false.
Recommended combinations
| Source | Input profile | Notes |
|---|---|---|
| S1000D data module | S1000D | Standard defence IETP path |
| ATA AMM / IPC / CMM | ATA iSpec 2200 | Standard aviation path |
| WebCGM publication system | WebCGM 2.1 | |
| DoD / CALS deliverable | CALS | CALS files typically lack APS |
| Legacy or unknown CGM | Auto-detect | Inspect output and refine |
| European aerospace / NATO | CGM+ | Arbortext or CATIA source |
| Petroleum seismic / well log | PIP | Handles large VDC extents |
Companion files
WebCGM XML Companion File (XCF)
Extension .xcf. Adds, overrides, or extends Application Structure attributes without modifying the source CGM. Auto-merged when named identically to the CGM file.
S1000D ICN Metadata File (IMF)
Extension .imf. Carries S1000D-specific metadata including hotspot inventories and security classifications. Auto-merged when co-located with the CGM file.
Companion file handling modes
Configure in Settings > SVG Options or the Convert tab’s per-job sidebar:
| Mode | Behaviour |
|---|---|
| Auto-detect & merge (default) | Finds and merges any XCF or IMF file with a matching name |
| XCF only | Merges XCF only; ignores IMF |
| Ignore | Does not use companion files |