KGA Schema Toolsដំណើរការជាបាច់
Generate Field Mapping
កំណត់ថា field ប្រភពណាត្រូវទៅ field គោលដៅណា រួចសរសេរលទ្ធផលជាឯកសារ JSON mapping។
- រកឃើញនៅឯណា
- Processing ▸ Toolbox ▸ KGA Toolbox ▸ KGA Schema Tools ▸ Generate Field Mapping
- លេខសម្គាល់ algorithm
- kga:generate_field_mapping
- ប្រភេទឧបករណ៍
- Batch algorithm
ទិដ្ឋភាពទូទៅ
The file is in exactly the format Append with Field Mapping takes, so a mapping between two schemas can be saved once, kept in version control, reviewed in a diff and reused. That reuse is the part that actually saves time when the same two schemas come round every month.
ប៉ារ៉ាម៉ែត្រ
| ឈ្មោះ | ប្រភេទ | តម្លៃលំនាំដើម | ការពិពណ៌នា |
|---|---|---|---|
| Source layer | Vector layer | — | The layer whose fields are being mapped from. |
| Target layer | Vector layer | — | The layer whose fields are being mapped to. |
| Match field names by | Enum | Fuzzy (ignore case, spaces and underscores) | Exact name, Case-insensitive name, Fuzzy (ignore case, spaces and underscores). Fuzzy lowercases names and strips spaces and underscores, so Parcel_ID finds parcelid. |
| Field mapping | File destination (*.json) | — | Where the mapping is written. |
| Change report | File destination (HTML), optional | not created | The match report as a file. |
របៀបប្រើ
- Load both layers in QGIS.
- Open KGA Schema Tools > Generate Field Mapping.
- Set Source layer and Target layer, and pick a matching strategy — start with the Fuzzy default.
- Choose where the Field mapping JSON goes. Somewhere you keep, not a temp folder: the point is to reuse it.
- Press Run and read the report. The unmatched fields on either side are the ones to fix by hand.
- Edit the JSON if needed, then feed it to Append with Field Mapping through its …or a saved mapping file parameter.
លទ្ធផល
លទ្ធផលដែលប្រកាស
| ឈ្មោះ | ប្រភេទ | ការពិពណ៌នា |
|---|---|---|
| Number of matched fields | Number | How many source→target pairs were found. |
អ្វីដែលអ្នកទទួលបាន
- A JSON mapping file, ready for Append with Field Mapping.
- A report — in the Processing log, and as HTML when you ask for the file — listing the matched pairs, the unmatched source fields and the unmatched target fields.
- The Number of matched fields count in the Processing results panel.
កំណត់សម្គាល់ និងដែនកំណត់
- Each target field is claimed at most once, so two source fields can never collapse onto one column.
- Nothing is written to either layer. This tool only inspects schemas.
- Unmatched fields are not an error — they are the output you care about. A field that appears in the unmatched lists needs a human decision, which is why the JSON is meant to be edited before use.
- The mapping matches names, not types. A pair whose types do not fit shows up later, as a lossy conversion in the append tool's report.