Supported File Formats
Mineflow's ingestion system accepts raw exploration folders, tables, reports, rasters, vectors, geophysics, and model files.
Format Support Overview
You do not need to reshape a project into one rigid template before uploading it. Mineflow routes each recognized file or bundle to the parser that matches its format, keeps known sidecars attached, and then classifies the geological data inside the file separately.
For bundled formats, upload the folder or all related sidecars together. A lone .shp, .tab, .bil, or .mtm file is often missing the metadata needed to parse the dataset correctly.
Raster, Imagery, and Grids
Raster uploads can be single georeferenced files or bundles with sidecar metadata. Mineflow keeps known auxiliary files with the primary raster when they are present.
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
RRD files are routed with matching raster targets such as TIFF, ENVI, JPEG2000, JPEG, PNG, and ERS files.
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
Spatial vector and model formats are parsed into map layers, geometry, or model artifacts depending on the file contents.
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 is routed as vector data; JSON records are accepted for structured record parsing.
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
TSurf and solid files are routed through the GOCAD parser.
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
Leapfrog model files and viewer scenes are accepted as scientific/model artifacts.
Geophysical and Scientific Data
Geophysical formats are routed by survey family when the file extension and companion files identify the instrument or interchange standard.
Zonge Magnetotellurics
.mtm with .mtd, .avg, .stn
MTM bundles are grouped for magnetotelluric parsing.
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
ASEG bundles are grouped by their definition and descriptor sidecars.
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.
Tables, Documents, and Presentations
Mineflow can extract structured exploration data from ordinary tables and from narrative reports, maps, and presentations.
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.
Database and Folder Bundles
Some formats are not meaningful as a single file. Keep the folder or companion files together so Mineflow can route the bundle correctly.
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.