Skip to main content

Upload Your Data [Beta]

Learn how to prepare and upload your data using the Files Uploader in VRIFY.

Overview

This article covers what data you can upload to VRIFY, the required format for each data type, and how to use the Files Uploader. It applies to all VRIFY file uploads across all VRIFY products.

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 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

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.

For a complete breakdown of every supported asset type, the applicable data items within each, and the exact file format required for each, see:

If you're unsure which files to start with, reach out to your VRIFY contact to help you identify the right ones.


Data Categories and Requirements

The table below lists every asset type supported by the Files Uploader and the format(s) required for each.

For optimal processing, upload your complete dataset in a single file per table. For each CSV-based asset type, this means one CSV containing all your records for that data type. 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

  • Claim Boundaries

  • Shapefile

3D Infrastructure

  • Processing Plant

  • Infrastructure

  • Pits

  • Underground Files

  • DXF

  • Shapefile

Drilling

  • Drillholes

  • Proposed Drillholes

  • Highlights

  • Photos, PDFs & Sections

1 CSV per table — entire database

  • Drill Collar (CSV)

  • Drill Survey (CSV)

  • Drill Assay (CSV)

  • Drill Highlights (CSV)

  • Drill Lithology (CSV)

  • Photos/PDFs/

Sections: PNG, JPEG, PDF, GeoTIFF

Geology

  • 3D Objects

  • Geological Structures

  • Photos, PDFs & Sections

  • DXF

  • Shapefile

  • PNG, JPEG, PDF, GeoTIFF

Surface Geochemistry

  • Lake Sediments

  • Stream Sediments

  • Soil

  • Till

  • Water Samples

  • Rock

  • Geochemistry (CSV)

Geophysics

  • Magneto Tellurics

  • Magnetic

  • Gravity

  • Electromagnetic

  • IP / DCIP

  • Radiometrics

  • PDFs & Sections

  • ERS, GeoTIFF

  • PNG, JPEG, PDF, GeoTIFF

Block Models

  • Resources

  • Reserves

  • Block Model Parameters (CSV)

  • Block Model Data (CSV)

3D Models

  • 3D Models

  • DXF

Spectral Data

  • Remote sensing

  • ERS, GeoTIFF

Photos & Graphics

  • Drone 360s

  • Logos & Legends

  • Scale Objects & Bar

  • Icons

  • PNG, JPEG, GeoTIFF

PDFs

  • PDF

  • PDF

Drilling CSVs

Drilling data must be uploaded as one CSV per table, containing the entire database. Tables are joined on the Hole Name (ID) field. The minimum required to render drillholes in 3D is the Drill Collar CSV and Drill Survey CSV (if azimuth and dip aren't already in the Collar table).

Drill Collar (CSV)

Field

Notes

Project Name

Project this hole belongs to.

Hole Name (ID)

Unique hole identifier. Joins this CSV to all other drilling CSVs.

Final Depth (m or ft)

End-of-hole depth.

X / Easting / Longitude

Collar easting (or longitude if geographic CRS).

Y / Northing / Latitude

Collar northing (or latitude if geographic CRS).

Z / Elevation (m or ft)

Collar elevation.

Azimuth

Collar azimuth, degrees from north.

Dip

Collar dip, degrees.

Drill Survey (CSV)

Field

Notes

Hole Name

Must match a Hole Name (ID) in the Drill Collar CSV.

Depth (m or ft)

Downhole depth of the survey reading.

Dip

Dip at this depth, degrees.

Azimuth

Azimuth at this depth, degrees from North.

Drill Assay (CSV)

Field

Notes

Hole Name

Must match a Hole Name (ID) in the Drill Collar CSV.

Sample ID

Lab sample identifier.

From (m or ft)

Start depth of the sampled interval, in metres or feet.

To (m or ft)

End depth of the sampled interval, in metres or feet.

Sample Type

Drilling sample type

Drill Highlights (CSV)

Field

Notes

Hole Name

Must match a Hole Name (ID) in the Drill Collar CSV.

Interval (m or ft)

Length of the highlighted interval, in metres or feet.

Label

Highlight label / annotation to display in Present.

Drill Lithology (CSV)

Field

Notes

Hole Name

Must match a Hole Name (ID) in the Drill Collar CSV.

From (m or ft)

Start depth of the lithology interval, in metres or feet.

To (m or ft)

End depth of the lithology interval, in metres or feet.

Primary Lithology

Lithology code or label for the interval.

Photos, PDFs, and Sections

Drilling-related supporting files (core photos, scanned logs, vertical sections) are accepted as PNG, JPEG, PDF, or GeoTIFF. Associate each file to a hole using the Hole Name in the file name or via the metadata fields in the uploader.


Surface Geochemistry CSV

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.

Field

Notes

Project Name

Project this sample belongs to.

X / Easting / Longitude

Sample easting (or longitude if geographic CRS).

Y / Northing / Latitude

Sample northing (or latitude if geographic CRS).

Sample ID

Unique sample identifier.

Sample Type

Surface sample type.

Analytical results (e.g. Au_ppm, Cu_pct) are added as additional columns alongside the required fields — one column per element or measurement.


Block Model CSVs

Block model uploads require two CSVs: one defining the model parameters and one defining the blocks. Both are required.

Block Model Parameters

Field

Notes

Start at block corner (T/F)

Indicates whether the origin of the model is the corner of the first block (TRUE) or the center of the first block (False).

Parent Block Size X (m or ft)

Parent block dimension in X, in metres or feet.

Parent Block Size Y (m or ft)

Parent block dimension in Y, in metres or feet.

Parent Block Size Z (m or ft)

Parent block dimension in Z, in metres or feet.

Rotation (Azimuth)

Rotation of the block model grid, in degrees azimuth.

Block Model Name (file name)

Name of the block model — use file name if no block model name present.

Block Model Data

Field

Notes

Block Type (Parent or Subcell)

Whether the block is a parent block or a subcell.

X / Easting / Longitude

Block centroid easting (or longitude if geographic CRS).

Y / Northing / Latitude

Block centroid northing (or latitude if geographic CRS).

Z / Elevation (m)

Block centroid elevation in metres.

[optional] Block Size X (m or ft)

Block dimension in X, in metres or feet.

[optional] Block Size Y (m or ft)

Block dimension in Y, in metres or feet.

[optional] Block Size Z (m or ft)

Block dimension in Z, in metres or feet.

Attribute columns (grade, tonnage, classification, etc.) are added alongside the required fields. Include as many as needed.


Before You Upload

Double-check the following before submitting your data to avoid validation errors:

  • File formats match the asset type (see tables above)

  • 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

  • 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


How to Use the Files Uploader

The Files Uploader is built into the VRIFY platform, so no external tools or file sharing is required. You can upload directly from your computer, Google Drive, or Dropbox.

  1. Open Files.

    • In the left-hand menu, click Files under the Data category. This takes you to the All Data Files page.​

  2. Click Upload Files.

    • This opens the file uploader.

  3. Choose your upload method.

    • Click Browse Files to upload from your computer, or select Google Drive or Dropbox to upload from the cloud. You'll be prompted to log in and select your files.

  4. Select a folder.

    • Assign each file to the appropriate folder and subfolder based on data type. Some examples:

      • Drill collar files → Drilling > Drillholes

      • Claim boundary shapefiles → Property Boundaries

      • Block model CSVs → Block Models > Resources or Block Models > Reserves

      • Geophysical grids → Geophysics (e.g. Magnetic, Gravity, EM)

      • Geology solids → Geology > 3D Objects

  5. If you're uploading from within a folder, these fields will be pre-filled.

  6. Upload.

    • Click Upload File. A progress bar will appear in the top-right corner. For large files, stay on the page until the upload completes. Navigating away will cause it to fail.​

  7. Confirm.

    • Once complete, your files will appear in All Data Files and in the folder you selected.

Uploaded files go through a review workflow before they become available in VRIFY Present. Files will only appear as asset objects in your 3D and 360 slides once their status shows Accepted. For a full breakdown of each status, see Understanding File Statuses.

Note: You'll need the Data user permission enabled on your account to see Files in the sidebar. If you don't see it, contact your VRIFY account admin.


Need Help?

If your data doesn't fit cleanly into the categories above, or if a file fails validation, get in touch before reformatting anything. VRIFY has ingested data from every major mining software ecosystem and can usually offer a direct path.

Reach out to your dedicated VRIFY contact or email support@vrify.com. The team can review your raw exports and confirm the best way to package them for upload.

Did this answer your question?