Terrestrial Ecosystem Mapping (TEM) Project Boundaries

759 views (18 recent)

Published by the Ministry of Environment and Climate Change Strategy - Knowledge Management
Licensed under Open Government Licence - British Columbia

Terrestrial Ecosystem Mapping (TEM) project boundaries contains (study areas) and attributes describing each project (project level metadata), plus links to the locations of other data associated with the project (e.g., reports, polygon datasets, plotfiles, field data, legends).TEM divides the landscape into units according to a variety of ecological features including climate, physiography, surficial material, bedrock geology, soils and vegetation. This layer is derived from the STE_TEI_PROJECT_BOUNDARIES_SP layer by filtering on the PROJECT_TYPE attribute.

Data and Resources

Dataset Extent

Latitude: 48.0° to 60.0°
Longitude: -139.5° to -113.5°

Additional Information

Purpose

To provide a spatial index to Terrestrial Ecosystem Mapping projects and to facilitate appropriate use of Terrestrial Ecosystem Mapping for resource management, planning and decision making.

Lineage Statement

Varies between projects. Data is from individual inventories conducted across the province from the 1980s to present. Some projects have undergone several phases of data conversion including different data formats (e.g., ArcInfo to Geodatabase) and different vintages of inventory standards.

Contact Information

NameTony Button (pointOfContact)
EmailTony.Button@gov.bc.ca
OrganizationMinistry of Environment and Climate Change Strategy
Sub-OrganizationKnowledge Management
NameTerrestrial Ecosystem Information (TEI) Mailbox (pointOfContact)
EmailTEI_Mail@gov.bc.ca
OrganizationMinistry of Environment and Climate Change Strategy
Sub-OrganizationKnowledge Management

Access & Security

Who can view this dataset? Public
Who can download this dataset?Public

Metadata Information

Record Published 2011-03-09
Record Last Modified 2019-09-05
Resource Status onGoing

Object Description

Object Name: WHSE_TERRESTRIAL_ECOLOGY.STE_TEM_PROJECT_BOUNDARIES_SVW

Short Name: STTMPRJCTB
Comments: STE_TEM_PROJECT_BOUNDARIES_SVW contains Terrestrial Ecosystem Mapping (TEM) project boundaries (study areas) and attributes describing each project (project level metadata), plus links to the locations of other data associated with the project (e.g., reports, polygon datasets, plotfiles, field data, legends).TEM divides the landscape into units according to a variety of ecological features including climate, physiography, surficial material, bedrock geology, soils and vegetation. This layer is derived from the STE_TEI_PROJECT_BOUNDARIES_SP layer by filtering on the PROJECT_TYPE attribute.

Column Name Short Name Data Type Data Precision Comments
BUSINESS_AREA_PROJECT_ID BSNSSRPRJC NUMBER 5 BUSINESS AREA PROJECT ID (aka BAPID) contains a numeric project identifier assigned by the Ministry of Environment, Ecosystem Information Section. The project BAPID is used to identify all information relating to a project and is the unique identifier (PK) for the project and is the linking key used to join or relate other TEIS data sets such as the TEIS Polygon Attribute. For example: 1234.
PROJECT_TYPE PRJCTTP VARCHAR2 9 PROJECT TYPE (aka PROJ_TYPE) contains a 3-9 letter code indicating the specific type of mapping and attributes gathered for the project. For example: TEM, PEM, SEI, TIM, TSM, TBT, TEMSEI, TEMNSS and PRETEM.
PROJECT_NAME PRJCTNM VARCHAR2 100 PROJECT NAME (aka PROJ_NAME) contains the common name of the project, usually a well known local place or feature. For example: Penticton Cr, and Kelowna South Slopes.
PROJECT_MAP_SCALE PRJCTMPSCL NUMBER 10 PROJECT MAP SCALE (aka PROJ_SCALE) contains the scale of the project maps produced. For example: 10000, 20000, 50000, and 100000.
MODIFICATION_DATE MDFCTNDT DATE 7 MODIFICATION DATE (aka MOD_DATE) contains the year, month and day that the attribute data or the corresponding spatial data (i.e. polygon boundaries) for the given data record was last altered in any way. For example: 3/28/2001.
GEOGRAPHIC_LOCATION_NAME GGRPHCLCTN VARCHAR2 254 GEOGRAPHIC LOCATION NAME (aka GEOG_LOC) contains a text string indicating the geographic location of the mapping project. This is a gazetted name taken from published map; for example, a town, lake, or watershed.
PROJECT_COMPLETION_DATE PRJCTCMPLT VARCHAR2 20 PROJECT COMPLETION DATE (aka COMPL_DATE) contains the date on which the project was completed. For example: 2007, 2007-04-14, or March 1999.
SURVEYED_DATES SRVDDTS VARCHAR2 254 SURVEYED DATES (aka SURV_DATE) contains the date or dates of field inventories. For example: June-July 2001, March 7 to 12, 1999.
ECOSYSTEM_SURVEY_INTENSITY_LVL CSSTMSRVNT VARCHAR2 1 ECOSYSTEM SURVEY INTENSITY LVL (aka ESIL) contains a numeric or character code representing the sampling intensity characterized according to percentage of polygons that have been field inspected or density of inspections by area. For example: 1, 2, 3, 4, 5 or R.
TERRAIN_SURVEY_INTENSITY_LVL TRRNSRVNTN VARCHAR2 1 TERRAIN SURVEY INTENSITY LVL (aka TSIL) contains a character code representing the extent to which the terrain mapping for the current project has been checked on the ground. For example: A, B, C, D or E.
ACCURACY_ASSESSMENT_LVL CCRCSSSSM1 NUMBER 2 ACCURACY ASSESSMENT LVL (aka ACCURACY) contains a number from 1-6 based on the level of accuracy assessment used. For example: 1, 2, 3, 4, 5, or 6.
ACCURACY_ASSESSMENT_COMMENTS CCRCSSSSMN VARCHAR2 254 ACCURACY ASSESSMENT COMMENTS (aka AA_COM) contains information about the accuracy assessment methodology, assessment type or other information relating to the accuracy assessment. For example: ""The assessment tested the accuracy of the PEM product for its utility for wildlife habitat rating"".
RESPONSIBLE_ORGANIZATION_NAME RSPNSBLRGN VARCHAR2 80 RESPONSIBLE ORGANIZATION NAME (aka ORG_NAME) contains the name of the public or private-sector organization responsible for the mapping project. For example: MOE Wildlife Habitat Section and Timberline Natural Resource Group Ltd.
PROJECT_SUPERVISOR_NAME PRJCTSPRVS VARCHAR2 80 PROJECT SUPERVISOR NAME (aka PROJ_SUP) contains the name of the professional responsible for project sign off. For example: Deepa Filatow, P.Geo.
ECOSYSTEM_MAPPER_NAME CSSTMMPPRN VARCHAR2 80 ECOSYSTEM MAPPER NAME (aka ECO_MAP) contains the name of the person who delineated and pre-typed/typed the Ecosystem polygons; or in the case of SEI, the person who developed the ratings tables (logic) to theme the sensitive ecosystems from other ecosystem data; or in the case of PEM, the ecologist who structured the knowledge base for the project area. For example: Corey Erwin, R.P.Bio.
TERRAIN_MAPPER_NAME TRRNMPPRNM VARCHAR2 80 TERRAIN MAPPER NAME (aka TER_MAP) contains the name of the licensed professional who has done the terrain mapping (polygon delineation and pre-typing/typing). Where there is more than one mapper on a project, this is the name of the project leader. For example: Sid Tsang, P.Geo.
SOIL_MAPPER_NAME SLMPPRNM VARCHAR2 80 SOIL MAPPER NAME (aka SOIL_MAP) contains the name of the person who completed the soil survey, including delineating the soil polygons, conducting field work and describing the soils in a project area. Where there is more than one mapper on the project, this is the name of the project leader. For example: Robert Maxwell, P.Ag..
WILDLIFE_MAPPER_NAME WLDLFMPPRN VARCHAR2 80 WILDLIFE MAPPER NAME (aka WILD_MAP) contains the name of the wildlife biologist responsible for the development or revision of the species-habitat models, all related field activities, and final wildlife habitat mapping or species distribution mapping products. For example: Calvin Tolkamp, R.P.Bio.
DIGITAL_DATA_CAPTURE_NAME DGTLDTCPTR VARCHAR2 125 DIGITAL DATA CAPTURE_NAME (aka DIG_CAP) contains the name of the individual or organization responsible for digital capture of spatial data. For example: Chartwell Consultants Ltd.
GIS_SUPERVISOR_NAME GSSPRVSRNM VARCHAR2 80 GIS SUPERVISOR NAME (aka GIS_SUP) contains the name of the individual responsible for sign-off on the spatial digital data. For example: Jason Kubian.
RECORDER_NAME RCRDRNM VARCHAR2 254 RECORDER NAME (aka REC_NAME) contains the name(s) of the person(s) who entered the project and polygon attribute data into a database. For example: Tony Button, Jo-Anne Stacey and Maija Finvers.
PROJECT_CLIENT_NAME PRJCTCLNTN VARCHAR2 80 PROJECT CLIENT NAME (aka CLIENT) contains the name of the client for whom the project was completed. For example: Tolko Industries LTD.
TRIM_VERSION_NUMBER TRMVRSNNMB VARCHAR2 1 TRIM VERSION NUMBER (aka TRIM_NBR) contains a one-digit integer representing the version of TRIM mapping used for the project. For example: 1 or 2.
IMAGE_TYPE IMAGE_TYPE VARCHAR2 1 IMAGE TYPE (aka PHO_TYPE) contains a one-character code indicating specific details about the image type from which the mapped information was interpreted. For example: 1 (colour airphoto), 2 (black and white airphoto), 3 (digital colour airphoto), 4 (digital black and white airphoto), 5 (orthophoto), or 6 (landsat).
IMAGE_SCALE MGSCL NUMBER 10 IMAGE SCALE (aka PHO_SC) contains the scale of air photos/images used for polygon delineation and pre-typing. For example: 20000, 50000 or 100000.
IMAGE_YEAR IMAGE_YEAR NUMBER 4 IMAGE YEAR (aka PHO_YR) contains the year of air photo(s) or images (yyyy) used for polygon delineation and pre-typing. In the case where several vintages of air photos/images were used, the year applicable to the majority. For example: 1996.
TERRAIN_LEGEND_SOURCE TRRNLGNDSR VARCHAR2 50 TERRAIN LEGEND SOURCE (aka TER_LEG_SC) contains a reference to the origin of a customized legend, if utilizing a legend developed for another project. For example: D. Filatow, 1999, Boundary Forest District Recon TSM Project, Appendix 2.
TERRAIN_LEGEND_TYPE TRRNLGNDTP VARCHAR2 3 TERRAIN LEGEND TYPE (aka TER_LEG_TP) contains a 1-3 letter code indicating the type of legend associated with the map. For example: G (general), S (short), TS (terrain stability), O (other) or C (custom).
VERSION_OF_PACKAGE_USED VRSNFPCKGS VARCHAR2 2 VERSION OF PACKAGE USED (aka PACK_NBR) contains a 1-2 character code indicating the version of standards used for project mapping. As codes have changed over time, indicates the versions of manuals used for the project. For example: 1 (Standard for Terrestrial Ecosystem Mapping in British Columbia (1995); and Addenda to Terrestrial Ecosystems Mapping Standards, (1996)), 2 (Standard for Terrestrial Ecosystem Mapping in British Columbia (RIC, 1998)).
STABILITY_CLASSIFICATION_TYPE STBLTCLSSF VARCHAR2 1 STABILITY CLASSIFICATION TYPE (aka STBCLS_TP) contains a one character code indicating the classification system used to classify slope stability for the current project. For example: R (Reconnaissance), D (Detailed), or E (Es).
SLOPE_UNIT SLOPE_UNIT VARCHAR2 1 SLOPE UNIT (aka SLP_UNIT) contains a one character code indicating the type of slope units used. For example: P (Percent) or D (Degree).
PROJECT_COMMENTS PRJCTCMMNT VARCHAR2 254 PROJECT COMMENTS (aka PROJ_COM) contains text to provide any other pertinent information regarding the project. At all times attempt to use referenced classifications which are well defined and understood in the science, or provide thorough definitions for the user. This field may also be used to reference associated project files. For example: Drainage classes were recorded by decile. This project is related to BAPID=1234 which used polygon and attribute data from this dataset to generate environmental sensitivity ratings.
PROJECT_IDENTIFICATION PRJCTDNTFC VARCHAR2 5 PROJECT IDENTIFICATION (aka PROJ_ID) contains a unique five-character identifier (project short name) for each project being delivered. For example: WILLW.
MAP_LEGEND_DESCRIPTION MPLGNDDSCR VARCHAR2 140 MAP LEGEND DESCRIPTION (aka LEGEND_COM) contains a description of the generic map legend found at MAP LEGEND DATA DOWNLOAD LINK (MAP_LEG). For example: Information on how to interpret terrain labels is available at the following site.
MAP_LEGEND_DATA_DOWNLOAD_LINK MPLGNDDTDW VARCHAR2 100 MAP LEGEND DATA DOWNLOAD LINK (aka LEGEND_URL) contains the URL for the website or FTP site where the generic map legend is available. For example: http://a100.gov.bc.ca/pub/acat/public/viewReport.do?reportId=1531.
ECOCAT_DATA_DESCRIPTION CCTDTDSCRP VARCHAR2 200 ECOCAT DATA DESCRIPTION (aka ECOCAT_COM) contains a description of the Ecological Reports Catalogue (EcoCat) link found at ECOCAT URL DATA DOWNLOAD LINK (ECOCAT_URL). For example: Project related data is available from the EcoCat site.
ECOCAT_URL_DATA_DOWNLOAD_LINK CCTRLDTDWN VARCHAR2 100 ECOCAT URL DATA DOWNLOAD LINK (aka ECOCAT_URL) contains the URL for the specific project within EcoCat where the project files (not on LRDW) are available. Spatial data available via the LRDW should be considered more current than data found on EcoCat. For example: http://a100.gov.bc.ca/pub/acat/public/viewReport.do?reportId=13625, and http://a100.gov.bc.ca/pub/acat/public/viewReport.do?reportId=13350.
REFERENCE_1_DATA_DESCRIPTION RFRNC1DTDS VARCHAR2 100 REFERENCE 1 DATA_DESCRIPTION (aka REF_1_COM) contains a description of the link found at REFERENCE 1 DATA DOWNLOAD LINK (REF_1_URL). For example: Project report is available from the Ministry library, or Raster and/or PDF maps are available from the following FTP site.
REFERENCE_1_DATA_DOWNLOAD_LINK RFRNC1DTDW VARCHAR2 100 REFERENCE 1 DATA DOWNLOAD LINK (aka REF_1_URL) contains a URL to additional project information and/or files (not in the LRDW or EcoCat). For example: http://www.for.gov.bc.ca/hfd/library/index.htm, and ftp://fshftp.env.gov.bc.ca/pub/outgoing/Terrain_Data/Terrain_Soils_Maps_Raster/.
REFERENCE_2_DATA_DESCRIPTION RFRNC2DTDS VARCHAR2 100 REFERENCE 2 DATA_DESCRIPTION (aka REF_2_COM) contains a description of the link found at REFERENCE 2 DATA DOWNLOAD LINK (REF_2_URL). For example: Project report is available from the Ministry library, or Raster and/or PDF maps are available from the following FTP site.
REFERENCE_2_DATA_DOWNLOAD_LINK RFRNC2DTDW VARCHAR2 100 REFERENCE 2 DATA DOWNLOAD LINK (aka REF_2_URL) contains a URL to additional project information and/or files (not in the LRDW or EcoCat). For example: http://www.for.gov.bc.ca/hfd/library/index.htm, and ftp://fshftp.env.gov.bc.ca/pub/outgoing/Terrain_Data/Terrain_Soils_Maps_Raster/.
REFERENCE_3_DATA_DESCRIPTION RFRNC3DTDS VARCHAR2 100 REFERENCE 3 DATA_DESCRIPTION (aka REF_3_COM) contains a description of the link found at REFERENCE 3 DATA DOWNLOAD LINK (REF_3_URL). For example: Project report is available from the Ministry library, or Raster and/or PDF maps are available from the following FTP site.
REFERENCE_3_DATA_DOWNLOAD_LINK RFRNC3DTDW VARCHAR2 100 REFERENCE 3 DATA DOWNLOAD LINK (aka REF_3_URL) contains a URL to additional project information and/or files (not in the LRDW or EcoCat). For example: http://www.for.gov.bc.ca/hfd/library/index.htm, and ftp://fshftp.env.gov.bc.ca/pub/outgoing/Terrain_Data/Terrain_Soils_Maps_Raster/.
REFERENCE_4_DATA_DESCRIPTION RFRNC4DTDS VARCHAR2 100 REFERENCE 4 DATA DESCRIPTION (aka REF_4_COM) contains a description of the link found at REFERENCE 4 DATA DOWNLOAD LINK (REF_4_URL). For example: Project report is available from the Ministry library, or Raster and/or PDF maps are available from the following FTP site.
REFERENCE_4_DATA_DOWNLOAD_LINK RFRNC4DTDW VARCHAR2 100 REFERENCE 4 DATA DOWNLOAD LINK (aka REF_4_URL) contains a URL to additional project information and/or files (not in the LRDW or EcoCat). For example: http://www.for.gov.bc.ca/hfd/library/index.htm, and ftp://fshftp.env.gov.bc.ca/pub/outgoing/Terrain_Data/Terrain_Soils_Maps_Raster/.
BOUNDARY_ONLY_FLAG BNDRNLFLG VARCHAR2 1 BOUNDARY ONLY FLAG (aka BDRY_ONLY) contains a Y/N to indicate there is only a project boundary and no detailed polygon data in the LRDW. For example: Y, N.
REVIEW_COMMENTS RVWCMMNTS VARCHAR2 254 REVIEW COMMENTS (aka REVW_COM) contains a summary description of data issues such as coding errors, problems with geometry, identified during a TEIS_ENVIRONEMENT review of the data. For example: Several invalid codes were identified.
FEATURE_CODE FTRCD VARCHAR2 10 FEATURE CODE contains a value based on the Canadian Council of Surveys and mapping's (CCSM) system for classification of geographic features.
FEATURE_AREA_SQM FEAT_AREA NUMBER 19
FEATURE_LENGTH_M FEAT_LEN NUMBER 19
GEOMETRY GEOMETRY SDO_GEOMETRY 64 GEOMETRY is the column used to reference the spatial coordinates defining the feature.
OBJECTID OBJECTID NUMBER 38 OBJECTID is a required attribute of feature classes and object classes in a geodatabase.
SE_ANNO_CAD_DATA BLOB 4000 SE_ANNO_CAD_DATA is a binary column used by spatial tools to store annotation, curve features and CAD data when using the SDO_GEOMETRY storage data type.