Supported file formats
Bring in exploration tables, reports, maps, surveys, and complete GIS folders.
Formats with automatic processing quotes
Credit-priced uploads currently support the products below. Review and accept the processing quote before paid work starts. Structured drill import follows launch; until then, drill tables are processed as digital tables.
| Product | Formats |
|---|---|
| Report | |
| Digital table | CSV, TSV, XLSX |
| GIS layer | GeoJSON, GeoPackage, Shapefile |
| Raster import | Georeferenced TIFF |
| Georeferenced map image | PNG, JPEG, TIFF without georeferencing |
| Other file formats |
The source-format reference below also covers formats used in managed processing and public datasets. It is broader than automatic upload quoting: other formats can be left out of your quote as unsupported. Contact support before submitting a format outside the table above, including older Excel workbooks, specialist survey files and model bundles. Map vectorization, cross sections and standalone scanned tables are quoted separately. See File processing charges.
Before uploading
Keep the original filenames and upload related files together. A file extension identifies a format; the information inside it determines what Mineflow can extract and display.
Tables, Documents, and Presentations
Mineflow can extract structured exploration data from ordinary tables and from narrative reports, maps, and presentations.
| Format | Files | What to include or check |
|---|---|---|
| CSV and TSV | .csv, .tsv | Useful for collars, assays, lithology, samples, occurrences, and other tabular records. |
| Excel | .xlsx, .xls, .xlsm | Spreadsheets can contain drill tables, geochemistry, geophysics, occurrence records, and metadata. |
| Text and HTML | .txt, .html, .htm | Plain-text and HTML documents are accepted for record and narrative extraction. |
| PDF reports, maps, tables, and disclosure documents are parsed for text, tables, figures, and georeferenceable map content. | ||
| PowerPoint | .ppt, .pptx | Presentation decks are parsed for exploration figures, tables, and project context. |
Raster, Imagery, and Grids
Upload the raster with its coordinate information and companion files.
| Format | Files | What to include or check |
|---|---|---|
| GeoTIFF / Cloud Optimized GeoTIFF | .tif, .tiff | Sidecars such as .tfw, .ovr, .aux.xml, .prj, .wld, .rpb, .rpc, .tab, .ipj, and .rrd are grouped when present. |
| ER Mapper Raster | .ers | Supports ER Mapper and PCI-style raster bundles with .stx, .clr, .ghx, .rrd, .wkt, and related sidecars. |
| ENVI Raster | .bil, .bip, .bsq with .hdr | BIL, BIP, and BSQ rasters are grouped with their required .hdr and optional georeference sidecars. |
| JPEG2000 Raster | .jp2, .j2k | Used for georeference-capable JPEG2000 rasters and associated sidecar files. |
| JPEG and PNG Imagery | .jpg, .jpeg, .png | Standard and georeferenced imagery can be ingested; world files such as .jgw and .pgw are attached when available. |
| ArcGIS Reduced Resolution Dataset | .rrd | Include RRD files with their matching raster. An RRD is a companion file, not a replacement for the original grid. |
| ESRI ASCII Grid | .asc, .ascii | ASCII grid files are handled as standalone raster grids. |
| ESRI GRID / ADF Bundle | .adf folder contents | Directories containing ADF grid files are treated as one raster bundle. |
Vector, CAD, Point Cloud, and 3D Model Files
The contents determine which map layers, geometry, and 3D information can be prepared.
| Format | Files | What to include or check |
|---|---|---|
| ESRI Shapefile | .shp with .shx, .dbf, .prj, .cpg, .sbn, .sbx, .shp.xml | Upload the full sidecar set together so geometry, attributes, and coordinate systems stay attached. |
| ESRI File Geodatabase | .gdb folder | File geodatabase directories are treated as a folder-level bundle. |
| GeoJSON and JSON | .geojson, .json | GeoJSON stores spatial features; structured JSON records are also accepted. |
| KML / KMZ | .kml, .kmz | Google Earth style vectors and packaged KMZ files are supported. |
| MapInfo | .tab with .dat, .map, .id | MapInfo sidecars are grouped with the .tab file. |
| DXF | .dxf | CAD linework and geometry can be ingested from standalone DXF files. |
| LAS Point Cloud | .las | Point cloud files are supported as standalone uploads. |
| GOCAD Surfaces and Solids | .ts, .so | Upload the surface or solid together with any referenced files. |
| Datamine Wireframe / DTM | .dm | Datamine model files are supported, including paired file groups with common suffix patterns. |
| GEOH5 | .geoh5 | Mira Geoscience GEOH5 files are supported. |
| Leapfrog | .lfm, .lfview | Model files and viewer scenes are accepted. Available extracted content depends on the file; uploading a scene does not provide a complete Leapfrog project editor. |
Geophysical and Scientific Data
Include the survey definition, coordinate information, and companion files supplied with the data.
| Format | Files | What to include or check |
|---|---|---|
| Zonge Magnetotellurics | .mtm with .mtd, .avg, .stn | Keep the station and supporting survey files with the MTM file. |
| Zonge IP / TS2DIP | .s2d, .ipm, .ipd with .raw, .stn, .fld, .dat | Pole-dipole and dipole-dipole IP packages are grouped with inversion-related companion files. |
| ASEG-GDF2 | .dat with .dfn, .des, .nit | Include the definition and descriptor files so columns and units can be read. |
| SEG-Y | .segy, .sgy | Seismic data is accepted as standalone SEG-Y files. |
| NetCDF | .nc | NetCDF grids and cubes are supported for scientific raster-style datasets. |
| XYZ Point Data | .xyz | XYZ files are accepted for gridded or point-based scientific data. |
| Generic DAT | .dat | DAT files are accepted as standalone structured data when they are not part of a more specific bundle. |
Database and Folder Bundles
Some formats need a complete folder or a set of companion files. Keep them together when uploading.
| Format | Files | What to include or check |
|---|---|---|
| SQL Server BCP + SQL Bundle | .bcp with .sql | BCP data exports are grouped with their SQL schema files. |
| Folder-Based GIS Bundles | .gdb folders, ADF grid folders | File geodatabases and ESRI GRID directories should be uploaded as folders rather than as isolated child files. |
| Sidecar-Based GIS Bundles | Shapefile, MapInfo, ENVI, GeoTIFF, ERS, and Zonge sidecars | If a format has companion files, upload the whole folder or select all related files together. |
Check the processed result
After uploading, inspect the file status and the extracted categories in Files. A supported format does not guarantee that every page, object, or attribute can become a map layer. Check source coordinates and units when reviewing the result.
See Upload data for the workflow, or Troubleshooting if a file has failed.