Database Manual

Oak Ridges Moraine Groundwater Program

Section 3.3.1

Section 3.3.1 Naming Conventions

When naming a new location that is being added into the database it is important to consider (other) users of the database finding a well using the names that you assign to any/all of the LOC_NAME, LOC_NAME_ALT1 or LOC_ORIGINAL_NAME fields. In the past it was found that assigned names were too ambiguous (e.g. MW #6) and, as a result, wells were being added to the database on more than one occasion with varying names, thus creating duplicate records in the database. A final naming field, LOC_MAP_NAME, is used primarily for spatial (e.g. map) display purposes where length of name (i.e. as short as possible) is necessary to limit overlapping of text. No other specific guideline is provided.

The LOC_STUDY field can be used to assist in grouping and locating wells that may be tied to a certain study, for example a particular development application. It is recommended that the LOC_STUDY field be populated for any new wells added to the database.

The following should be considered when naming locations in the database:

It is important to note that the status of municipal or consultant drilled wells can change over time. For example, pumping wells can be abandoned or converted to monitoring wells or vice-versa. In such cases the prefix should be changed and the former name (with the earlier prefix designation) can be stored in the D_LOCATION_ALIAS table. Alternatively, to clearly identify that the well was converted, the former prefix can also be saved in parenthesis at the end of the current name. Decommissioned pumping wells should retain the PW prefix indefinitely and the name should not be changed. The LOC_STATUS_CODE (in D_LOCATION) should be changed from ‘Active’ (i.e. a value of ‘1’) to ‘Decommissioned’ (i.e. a value of ‘7’; refer to R_LOC_STATUS_CODE for details).

Examples are provided in the following table (broken into two sections for readability). Refer also to the D_LOCATION table outline in Section 2.1.1.

Table D_LOCATION naming conventions (LOC_NAME and
LOC_NAME_ALT1)Table D_LOCATION naming conventions (LOC_NAME and LOC_NAME_ALT1).