Kirra supports a wide range of export formats beyond CSV, DXF, GLTF, and GeoTIFF.
Export drill plans to IREDES XML format for transfer to Epiroc drill rigs. Includes hole geometry, pattern definitions, and machine settings.
Coordinate Note: IREDES uses X for Northing and Y for Easting. Kirra handles the swap automatically on export.
Export blast hole data to Cat MineStar Activity Queue Manager CSV format. Supports dynamic column ordering – you specify which columns to include and their order in the export dialog.
Export blast hole data in CBLAST format with 4 records per hole (HOLE, PRODUCT, DETONATOR, STRATA) for Orica systems.
Export blast holes and CAD linework to a Vulcan design archive (.arch_d).
Vulcan creates real blast holes from the file – load it with
Load Archive, tick Only list BLAST layers, and pick the layer.
Each hole carries its ID, collar, grade and toe, sub-drill, dip, bearing, burden and spacing. Holes with sub-drill export with three points (collar, grade, toe); holes without export with two.
Three things the file does not carry. Each is quick to set right, and knowing when saves re-exporting:
| What to do | |
|---|---|
| Burden & spacing | Check and correct these in Kirra, before exporting. They come from Kirra’s row detection and can be wrong on a curved or irregular pattern. |
| Drill rig | None is assigned. Assign one in Vulcan, after Load Archive. |
| Colours | Palette indices, and every Vulcan project can define its own palette. |
Why no drill rig? Vulcan stores no hole diameter – it stores a rig name, and resolves that against the receiving project’s
specifications.dab. A name invented by Kirra would resolve to nothing, so none is written. Maptek’s own BlastLogic leaves a placeholder for the same reason.
Default appearance. Holes arrive as a filled red circle (palette index 33) with the hole ID above in light grey (243) and the hole length below in dark grey (229), at 0.8 cm on a 1:100 map scale. CAD linework maps its Kirra colour to the nearest index in Vulcan’s standard palette. If your project uses a different palette, recolour in Vulcan after loading.
Multiple hole intervals. A Vulcan hole can carry several intervals – one per row of its Hole Intervals grid. Kirra’s model is collar, grade and end, so a hole imported with more than one interval keeps the last (the bench floor) and the others are discarded. Re-exporting such a hole will not restore them.
Export surfaces to Surpac format (paired .dtm and .str files). Kirra automatically deduplicates shared vertices and writes both files with matching base filenames.
Export blast patterns and geometry to Google Earth format. Holes are exported as placemarks with their details in the description, along with polylines and polygons.
Export blast data to ESRI Shapefile format. Produces a ZIP archive containing .shp, .shx, .dbf, and .prj files.
Export point data in various text formats:
| Format | Extension | Description |
|---|---|---|
| XYZ | .xyz |
Space-separated X Y Z with optional R G B |
| CSV | .csv |
Comma-separated X,Y,Z with optional R,G,B |
| PTS | .pts |
Count header + X Y Z I R G B |
| PTX | .ptx |
Leica scanner format |
Export point data to ASPRS LAS format, or to compressed LAZ: the points of visible surfaces, visible drawings and visible point clouds (hidden ones are left out), written as LAS 1.2, point format 0. A LAZ file holds exactly the same points as the LAS, compressed with LASzip, so it is much smaller and opens in software that reads LAZ.
.las or .laz to match the drop-down. If you type .las or .laz yourself, Kirra
writes that format; a name with no extension gets the one the drop-down chose.What a point cloud writes. Every point of every visible cloud, at exactly the coordinates the cloud holds, except the points of any class you unticked in Cloud Properties under Classes: the file matches what the screen and print show. Classification, intensity, return number and number of returns are written from the cloud; a cloud that does not have one of them writes classification 1 (Unclassified), return 1 of 1 and intensity 0.
What point format 0 cannot hold. Point format 0 stores no colour and no GPS time, so a cloud’s colour and GPS time are not written. Kirra says so: for a cloud that has colour, Export Complete adds The LAS point format used does not store colour, so the point cloud colour was not written. and, for a cloud that kept GPS time, The LAS point format used does not store GPS time, so the point cloud GPS time was not written.
A cloud of tens of millions of points takes a while to write; Kirra shows Exporting LAS… (Exporting LAZ… for a LAZ file) while it works. Compressing takes longer than a plain LAS write, but uses your computer’s processor cores in parallel.
Save a complete Kirra project as a .kap file. A KAP carries everything: the blast
(holes, groups, trunks, timing, charging), drawings, surfaces and imagery, every library
(explosive products, charge rules, pattern and print templates, measured seeds, PPV
monitors, block-model colour schemas) and your work settings. Use it for full project
backup and for sharing — the person who opens it can work exactly as you did.
Settings that belong to your computer — theme, language, toolbar and panel layout — are not included.
Point clouds. A KAP carries your point clouds with their colouring settings. They can be large, so when your workspace has any, saving a KAP first asks Point Clouds — Point clouds add (size) to this project. Include them? — and shows the size they will add:
| Button | Result |
|---|---|
| Include | The KAP carries the clouds, then asks where to save |
| Leave out | The KAP is saved without them. The clouds stay in your workspace |
| Cancel | No file is saved. Closing the dialog cancels as well |
The clouds are stored in the file as they are, not compressed, so the file grows by about the size shown.
Save your site setup as a .kat file: everything a KAP carries except the blast.
It holds your explosive products, charge rules, pattern and print templates, measured
seeds, PPV monitors and parameters, the CRS Library, colour
settings and work settings — no holes,
drawings, surfaces, images, point clouds, groups, trunks or timing.
Use a KAT to set up a new machine or a new site with the same catalogue and layouts, to hand a contractor your products and charge rules without a blast, or to keep your site standard separate from any one shot.
Export KAD drawing entities (points, lines, polygons, circles, text) to Kirra’s native .kad format.
Export to Wenco NAV ASCII format for fleet management integration.
Legacy format. SHOTPlan v3.0 is no longer in use. The export exists so a plan can be handed back to someone still running it.
Export ▸ Legacy ▸ ShotPlan 3 writes the visible blast holes and their ties to one .xel file.
BLAST123.XEL). Keep it that way.Export coordinate files in Epiroc Surface Manager format (.geofence, .hazard, .sockets).