3.1 Coding Activity and How to Start Coding Online
3.2 MINFILE Number
3.3 Name
3.4 Status
3.5 NTS Map
3.6 BC Map
3.7 Mining Division
3.8 Location
    3.8.1 Latitude/Longitude   3.8.2 UTM Zone  3.8.3 UTM Northing  3.8.4 UTM Easting
3.9 Elevation
3.10 Location Certainty
3.11 Canmindex Number
3.12 National Mineral Inventory (NMI) Number
3.13 Date Coded/Coded by
3.14 Date Revised/Revised by
3.15 Field Check
3.16 Comments - Identification

When coding online select the options from the corresponding list boxes.
Online help is also available from the MINFILE/www online coding card.

3.1 CODING ACTIVITY

3.2 MINFILE NUMBER(*) (all relational files)

Each mineral occurrence has a unique 9-character MINFILE number used to identify it within the computer database, in hard-copy printouts and on location maps. This number is assigned by the MINFILE Database Administrator after the record has been submitted and approved.  The MINFILE number number begins with a three-digit NTS (National Topographic System) location number used to identify the appropriate 1:1 000 000 map sheet (from 082 to 114), followed by a single alphabetic character (A to P) used to identify the appropriate 1:250 000 map sheet.

Due to a high density of occurrences, NTS map sheets 082E, F, K, L, 92H and I are plotted at a 1:100 000 scale. In these cases, a two-character (NE, NW, SE, SW) designation identifies the appropriate quadrant on the map sheet. The other map areas are plotted at a 1:250 000 scale and two blank spaces must be input in place of the two-character quadrant designation. An exception is 092IW.

The final three-character segment of the MINFILE number is a sequential three-digit number from 001 to 999, identifying the unique number on the map sheet. For example, 082FSW100 is the 100th occurrence documented in the 082FSW 1:100 000 scale NTS area. If a new occurrence is documented, an occurrence number will be assigned by the MINFILE Team.

3.3 NAME(*) (R08)

This is the most common or historically relevant name for an occurrence.  Names in current use may or may not be the most appropriate for an occurrence in a historical context.  List the most important name first followed by all aliases, in order of importance. Duplication of a first ranked name for different occurrences on the same map sheet is discouraged.  Each occurrence can have up to sixteen names of 30 characters each.  All appropriate names should be included.

3.4 NATIONAL MINERAL INVENTORY (NMI) NUMBER (E01)

This is a cross-reference to the National Mineral Inventory file located at the Mining Sector of Natural Resources Canada in Ottawa. This file is no longer being updated and maintained. Each documented mineral deposit in Canada is assigned a unique National Mineral Inventory Number. The number follows NTS conventions and consists of a 1:1 000 000 scale map designation (e.g., 082, 104, 093), followed by a 1:250 000 scale map designation consisting of an alphabetical character (A to P). This is followed by a 1:50 000-scale map designation consisting of a one or two-digit number (1 to 16), then by a commodity code (e.g., Au, Ag, Zn, etc.) and an occurrence number (e.g., 1, 2, 3, etc.). This field is free form with 18 characters.

Example: 103F9 Au1

3.5 STATUS(*) (R02) (E02)

The STATUS describes the state of development of the occurrence as of the date of coding. Status is assigned by checking the appropriate box listed on the coding form or selecting the appropriate status from the list brought up when anything is entered in this field on the computer. Each occurrence has only one status. Producers and Past Producers must be defined as either underground or open pit operations (select at least one using an X). Underground should be used to indicate existence of an adit on a site.

3.6 REGION

This field describes the part of the world the mineral occurrence is located in.  For online coding it always defaults to "BC: British Columbia" but you must still click "Add" to select.

3.7 LOCATION(*) (E01)

Coordinates for an occurrence may be input in either a latitude-longitude or a Universal Transverse Mercator grid (UTM) format (North American Datum NAD 83 is the default). The MINFILE/pc and MINFILE/www online coding card will automatically convert whichever coordinates you enter to the alternate system. Geodetic (latitude-longitude) designations have an east to west convention while the UTM system has a west to east convention.

3.10 NTS MAP(*) (R10) (E10)

NOTE: When coding online this field is automatically populated from the locational data but you must still click "Add" to select.

This is the National Topographic System map sheet designation for the 1:50 000 map sheet on which the mineral occurrence is located. The NTS map sheet number consists of a three-digit number identifying the 1:1 000 000 map area (082, 083, 092, 093, 094, 102, 103, 104 and 114), followed by one alphabetic character from A to P used to designate the appropriate 1:250 000 map sheet. A two-digit number from 01 to 16 designates the appropriate 1:50 000 map sheet and an alphabetic character (E or W) is used to designate the east or west half of the 1:50 000 map in which the specific occurrence is located. The database will accept up to four 1:50 000 scale map sheet designations for each occurrence in the event an occurrence straddles one or more map sheet boundaries. The geographic location must be in the first ranked NTS map sheet.

3.11 BCGS MAP (R11) (E11)

NOTE: When coding online this field is automatically populated from the locational data but you must still click "Add" to select.

The database will accept up to four, 1:20 000 scale map sheet designations for the BC MAP sheet system. The map sheet designation consists of a three-digit number identifying the 1:1 000 000 scale NTS map area (082, 083, 092, 093, 094, 102, 103, 104, and 114), followed by an alphabetic character (A to P) used to designate the appropriate 1:250 000 NTS map sheet. Then, a three-digit number (001 to 100) is used to designate the appropriate 1:20 000 map within the B.C. map sheet system.

3.12 MINING DIVISION(*) (R09) (E09)

 NOTE: When coding online this field is automatically populated from the locational data but you must still click "Add" to select.

The database will accept up to two Mining Divisions if an occurrence straddles a mining division boundary.

Historically, MINFILE has documented a limited number of occurrences outside the Provincial boundaries, such as in the Alaskan Panhandle, and these have been important in evaluating the metallogeny and economic potential of adjacent areas in British Columbia. The database, therefore, includes pseudo mining divisions for adjacent political jurisdictions and codes for them may be used to identify a selected number of important occurrences.

Refer to Figure 1 for Mining Division boundaries and Figure 2 for general information on Mining Camps in British Columbia.

3.13 ELEVATION(*) (E01)

NOTE: When coding online this field is automatically populated from the locational data but you must still click "Add" to select.

Elevations are to be quoted in metres above mean sea level. The maximum acceptable value is 6000 metres. Values acquired from accurate location plots on 1:50 000 map sheets are acceptable, but actual survey information is preferred. Negative elevations are not accepted in the database. Right justify entries with no zeros to the left.

3.14 FIELD CHECK(*) (E01)

A "Yes" or "No" designation is selected to indicate if this occurrence has been checked in the field, relatively close in time to the research date, by Ministry personnel. A field examination will be more valuable in determining the characteristics of an occurrence rather than a description based only on published data.

3.15 LOCATION CERTAINTY(*) (E01)

The location certainty is either 100 metres, 500 metres, 1 kilometre or 5 kilometres and is used to indicate the relative precision of the location of an occurrence (adit, trench, outcrop, etc.). A well documented, easily located occurrence should have a location certainty of 100 metres, meaning that the occurrence is within 100 metres of the given coordinates. A poorly documented occurrence may be identified by a location accuracy of 1 or 5 kilometres.

3.17 DATE CODED/CODED BY(*) (E01)

This information is automatically tracked when coding on-line.  For manual coding, enter the date on which the occurrence is described for the database and the initials (up to 4 characters) of the person compiling the information. The date is entered in a DD/MM/YY format. If nothing is entered in the Date field when the occurrence is created on the computer, it will automatically be set to the current date. See Appendix XIII for initials/names used to date.

3.18 DATE REVISED/REVISED BY(*) (E01)

This information is automatically tracked when using the MINFILE/www online coding card.  For manual coding, enter the date on which the occurrence was revised and the initials of the person who compiled the data for the revision. The date is entered in a DD/MM/YY format. If the Date field is left blank on the computer, it will automatically be set to the current date. See Appendix XIII for initials/names used to date.