To set up spatial data in XPAC, you usually import data from a third party mining data source (for example, Vulcan, Datamine, Surpac, AutoCAD) or from a CSV or TXT file. So that XPAC does not encounter any errors during the import process, you will need to make sure that the file that you are importing is in the correct format and/or has been adequately exported from the source program before starting the import into XPAC.
Exporting spatial data from Vulcan
You can either import 00T files that already exist in your project directory, or export Vulcan data as DXF files.
|
You will only be able to import 00T files into XPAC if you are using Vulcan 8.0.3 or below. If you are using Vulcan 8.1.2, you can either:
| • | contact Vulcan support for a triangulation conversion utility. |
With Vulcan 8.1.3, you can work with 'uncompressed' triangulations (that you can import into XPAC) by selecting .
|
Exporting DXF files from Vulcan
| 1. | Select File > Export. The Export window displays. |
| 2. | In the File Format pane, select AutoCAD (dwg,dxf,dxb). |
| 3. | In the File Type pane, select Design Strings/Grids/Triangulations (dwg,dxf,dxb). |
| 4. | Click OK. The Export to AutoCAD window displays. |
| 5. | Select DXF in the Select AutoCAD File Type To Create field. |
| 6. | Select Version 14 in the Select AutoCAD File Version To Create field. |
| 7. | Complete the remaining settings in the Export to AutoCAD window as required. |
| 8. | In the Grids and Triangulations section, click Browse. A Windows Explorer window displays. |
| 9. | Locate and select the files that you want to use. |
| 10. | Click OK. The Export to AutoCAD window redisplays. |
| 11. | Click OK. The Select By pop-up menu displays. |
| 12. | Click Cancel to stop Vulcan from looking for extra design data to include in the export. |
Vulcan exports the DXF file to the location that you specified in the Name of new AutoCAD file field.
|
The record PIL and/or name (or the activity number or name) are mapped by the user from the filenames.
|
Exporting DXF files
Several mining data source programs are capable of exporting spatial data as DXF files.
|
The record PIL and/or name (or the activity number or name) are mapped by the user from the filenames and DXF layer names.
|
Preparing polygon files for import
When you import polygon data from CSV or TXT files, you will need to follow certain format rules so that XPAC does not encounter any errors during the import process.
|
If the polygon file that you are importing does not adhere to the rules outlined below, you can still import the data into XPAC, however you must use an XCM. Contact RPMGlobal for more information.
|
General rules
When importing fixed width or delimited files, ensure that:
| • | you import data using a text file. |
| • | record identifiers are present in the file for each polygon (a record identifier must exist for each level of the database, including the level that you are importing the polygon to. This can be an upper or lower level record). |
| • | polygon data is in a regular pattern in the file. This pattern varies according to whether the file is a fixed width or a delimited file. |
| • | each polygon point has corresponding record identifiers in the file. |
| • | all points in a single polygon occur consecutively in the file (consecutive points are assigned to the same polygon if their record identifiers and activity are the same). |
|
| • | Each polygon can have any number of points. |
| • | Polygons do not need to be 'closed'. If the first and last points of the polygon are not identical, then XPAC automatically joins these points to close the polygon. |
| • | Record identifiers can either be the position in level number, record name at the level or both. If a level has a defined position table and the position in level number and the record name are imported from the file, then XPAC ignores the imported position in level number and uses the position table numbers instead. |
| • | If the activity name or number are not imported from the file, then XPAC assigns the polygon data to the default activity. |
|
Fixed width file rules
When importing a fixed width file, ensure that:
| • | each polygon point must occupies a single line in the file. |
| • | each item of common data is in the same range of columns for each line. XPAC uses the Start and Finish column values to locate polygon data. |
Delimited file rules
When importing a delimited file, ensure that:
| • | there are the same number of data items or fields for each polygon point represented in the file, even if their value is (0) (you can use up to 255 fields). |
| • | each data item or field is separated by delimiter/s. You can use multiple characters to separate data items, however XPAC treats every occurrence of the specified character/s as a delimiter (typically, delimited files only use one delimiting character). |
|
| • | XPAC reads adjacent delimiters as two fields. |
| • | XPAC treats carriage returns as delimiters. |
|
