How to Get Rid of Errors in Your Drilling Database in 25 Questions
21 February, 2019 | Blog
The frenetic pace of exploration programs and the tight deadlines between taking measurements and sending data to resource geologists can cause multiple database errors, which result in loss of time and money, and sometimes schedule delays. Most of these errors could have been easily identified and corrected as soon as the project started. Moreover, drilling data is essential for creating a robust geological model and for providing an unbiased estimate of mineral resources. This data must therefore be sufficiently rigorous, reliable and complete to comply with the NI 43-101 standard.
Here are some examples of a few easily achievable steps to help you validate your data.
Take the time to observe your data in 3D
If you have suitable software, the first thing to do is to look at your data in 3D and ask yourself the following questions:
- Is the data all in the same coordinate system?
- Are the drillholes all located on the project?
- Could the X and Y coordinates have been wrongfully reversed?
- Are the drill collar elevations consistent with the topography or with the underground developments?
- Do the drillhole locations match with the access roads or underground developments?
- Are the 3D drillhole pathways realistic (see Figure 1)?
Then every collar, deviation, assay and lithology tables must be validated.
- Do all the azimuth and dip columns have a value?
- Was the magnetic declination applied?
- Are the azimuth and dip values at surface similar to that planned at the collar?
- Is the azimuth between 0 and 360º?
- Does the dip range between -90º and +90º (warning, surface drillholes should all be the same sign [positive or negative, depending on the software])?
- Are there unrealistic differences between two consecutive deviation measurements?
Figure 1 – Example of drillholes with erroneous deviation data
- Are there implicit or explicit intervals missing?
- Are there overlaps between intervals? Some software programs accept them, but it is recommended not to have them in the same lithology table.
- Have the lithology names been standardized? The stage of homogenizing the lithological data between the various periods of exploration/operation, or between the various project owners, for example, can save you a lot of time in terms of interpretation and modelling.
- Are there empty fields in the assay table (except for pending assays)?
- Are there values of 0? If so, confirm that they are not “false” zeros (not sampled, pending assays, etc.).
- Are the highest grades justified by mineralization observation?
- What are the minimum and maximum interval lengths? Confirm that they are not errors.
- Are there overlaps between intervals?
- Is each assay properly identified with a unique sample number?
- If several analysis methods are used, is the final value systematically calculated using the same formula and does it take all methods into consideration?
- Have values below the detection limit received the same treatment? Although there can be exceptions (mainly in the case of historical assays), it is good practice to assign them half the value of the detection limit.
Other questions to ask
- Is the drillhole length consistent with the maximum depths of lithology, deviation and assay?
- Do all drillholes contain the information in the deviation, lithologies and assay tables? It is important to indicate if a drillhole was deliberately not assayed.
If you have other tables in your database, it is important to validate them as well.
Finally, if the deviation measures, coordinates and data were not automatically entered in the database, it is necessary to compare the database with the original data to ensure there are no typing errors.
If you have any questions or want to learn more on the subject, contact us. Our team of experts can support you throughout all your exploration and mining projects, from data acquisition, interpretation and modelling to estimation and optimization of resources and reserves.
This content is for general information purposes only. All rights reserved ©BBA