Overview
This article outlines the data formats supported by VRIFY Present (Beta) and explains how to structure your files for upload using the Files uploader. Once your files are uploaded, you will validate and publish your data using VRIFY Prepare.
To help you get the most value out of your visual assets, fields across all file specifications are categorized into two tiers:
Required: Core attributes mandatory for VRIFY to validate, transform, and render your data in 3D.
Recommended: While optional, these attributes unlock advanced spatial filtering, richer presentation tools, and automatic compatibility with future platform updates.
Note: This article applies to VRIFY Present Beta, which includes features not available in VRIFY Present Legacy. View legacy instructions at VRIFY Present (Legacy) & VRIFY Predict: Supported File Formats and Upload Requirements.
Why This is Important
VRIFY Present is built around a structured data model. Each asset you upload is validated, projected into the project coordinate system, and stored so it can be visualized in 3D in VRIFY Present and across all VRIFY software. Supplying data in the required formats means more streamlined project setup and consistent results.
What to Upload
VRIFY supports a wide range of file types across all major data categories. The table below summarizes accepted formats at a glance.
Data Type | File Format(s) |
Tabular Data | CSV, Shapefile* (Surface Geochemistry only) |
2D Line & Polygon | Shapefile (SHP, SHX, DBF, PRJ) |
3D Objects | DXF |
2D Images / Data | PNG, JPEG, PDF, GeoTIFF, ERS |
Shapefile packaging
Shapefiles must be uploaded with all four component files together (SHP, SHX, DBF, PRJ). A missing PRJ file means the platform cannot determine your coordinate system and the shapefile cannot be used.
Data Categories and Requirements
The table below lists every asset type supported by the Files Uploader and the format(s) required for each.
Upload a single file per data type (Collar, Survey, Assay, Highlights, or Lithology). Each file should contain your complete dataset for that type — avoid splitting files by campaign or individual hole. For example, your drill assay CSV should contain assay records for all holes in the project, not one CSV per hole.
Data Asset | Applicable Data | Data Requirements |
Property Boundaries |
|
|
Infrastructure |
|
|
Drilling |
| 1 CSV per type — entire database
|
Geology |
|
|
Surface Geochemistry |
|
|
Geophysics |
|
|
Block Models |
|
|
Spectral Data |
|
|
Photos & Graphics |
|
|
PDFs |
|
|
Drilling CSV Field Specifications
Drilling data must be uploaded as one CSV per data type, containing the entire database. Tables are joined on the Hole Name (ID) field. The minimum data required to render drillholes in 3D is the Drill Collar CSV and Drill Survey CSV.
If your Collar table does not include Azimuth and Dip, but your Survey table does, you can upload and process them together. The Collar Azimuth and Dip will be populated using corresponding values from the Survey table.
Process your Drill Collar CSV first, before any other drilling table. Uploading Survey, Assay, Highlights, or Lithology before Collar will cause validation errors, since every other table joins back to Collar on Hole Name (ID).
See Drillholes: Required and Recommended Fields for the full list of accepted fields.
Drilling Photos, PDFs, and Sections
Supporting Files
Supporting files (core photos, scanned logs, vertical sections) are accepted as PNG, JPEG, PDF, or GeoTIFF. As a best practice, we recommend naming each file with the Hole ID it refers to, so it's easier to associate the file with the correct hole. For example: DDH26-001_corephoto.jpg or DDH26-001_Section5.pdf.
Important for Drill Highlights:
If your Drill Highlights include photos, upload and process all Drill Photos first:
Highlights must be processed after photo processing is complete.
The Image File Name must match the Drill Photo file name exactly, and include the extension (e.g. JPEG, PNG).
Surface Geochemistry CSV & Shapefile Field Specification
All six surface sample types (lake sediments, stream sediments, soil, till, water samples, and rock) use the same CSV structure. The Sample Type column distinguishes between them.
See Surface Geochemistry: Required & Recommended Fields for the full list of accepted fields.
Block Model CSV Field Specification
Block Model uploads require two CSVs: one defining the model parameters and one defining the blocks. Both are required.
See Block Models: Required & Recommended Fields for the full list of accepted fields along with file specifications for Grade Shells and other 3D representations of block models.
Before You Upload
Double-check the following before submitting your data to avoid validation errors:
File formats match the asset type
CSVs are encoded with a period (.) as the decimal separator, and use comma, tab, semicolon, or pipe as the column delimiter
Drilling CSVs: every Hole Name in Survey, Assay, Highlights, and Lithology files exists in the Drill Collar CSV
Drilling intervals: every interval has From < To
Surface Geochemistry and Drill Assay: Sample Type column is populated for every row
Drill Images are uploaded and processed before being added to a Drill Highlight CSV.
Coordinates: if multiple coordinate systems are used, separate data into different files and name them accordingly (e.g. DrillCollar_NAD83.csv, DrillCollar_NAD27.csv)
Units: imperial and metric are both accepted for depths; angles should be in degrees
Shapefiles: all four component files (SHP, SHX, DBF, PRJ) are included
Learn More
Still Have Questions?
Reach out to your dedicated VRIFY contact or email support@vrify.com for more information.