Downloading and Editing a Data Import Configuration File
You can define a data import configuration as a CSV config file, and reuse it for other data imports of the same format. The data import configuration file has an extension of .Config.csv.
You can either define the configuration in Horizons (see Configuring Data Import Fields), then download it, edit it in Microsoft Excel, and upload it back into the data import. Or you can download the configuration file from Horizons and edit it solely in Excel, and then upload with your data file.
Save the configuration file and import it into other configurations, if the columns and format are the same.
To download and define a data import configuration file in Excel
- In the Management module Data Import drop-down, do one of the following:
- Select an existing unprocessed data import item to configure.
- Click Add import and import a new data file (see Uploading a Data File).
The Configure Data Import window opens.
Click the spanner icon beside the uploaded data files, if you wish to configure any fields prior to downloading the config file.
- Click the Download icon.
This downloads a file with extension .Config.csv. The data import configuration file takes the form of a matrix that defines the mapping from column headings (fields) in the data import file(s) to the fields within Horizons. You can edit this using Excel. For full details of the fields and how to map them to your data, see Configuring Data Import Fields. An example data import configuration file is shown below:
| File Column Headings | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Horizons Fields | X_1_Test | Y_1_Test | section | start_chn | end_chn | xsp | net_seclen | feature | X2 | Y2 |
| Desc | - | - | Section Label | - | - | - | - | - | - | - |
| Type | - | - | - | - | - | - | - | - | - | - |
| Units | - | - | - | M | M | - | - | - | - | - |
| NumDP | - | - | - | 2 | 2 | - | - | - | - | - |
| IsSectionLabel | - | - | 1 | - | - | - | - | - | - | - |
| IsStartChain | - | - | - | 1 | - | - | - | - | - | - |
| IsEndChain | - | - | - | - | 1 | - | - | - | - | - |
| IsUkpmsXSP | - | - | - | - | - | 1 | - | - | - | - |
| IsUkpmsFeatureCode | - | - | - | - | - | - | - | 1 | - | - |
| SeverityAsc | - | - | - | - | - | - | - | - | - | - |
| csvX1 | 1 | - | - | - | - | - | - | - | - | - |
| csvY1 | - | 1 | - | - | - | - | - | - | - | - |
| csvX2 | - | - | - | - | - | - | - | - | 1 | - |
| csvY2 | - | - | - | - | - | - | - | - | - | 1 |
| csvWKT | - | - | - | - | - | - | - | - | - | - |
When you have updated the configuration file, upload it back into your data item by selecting the data item from the Management > Data Import drop-down again, clicking Add File(s), and selecting your edited .Config.csv file. Horizons recognises this as a configuration file rather than a data file by the .Config.csv extension.