Report Creator Version Beta
For details visit the Terrain web site or email the developer.
2015-02-03 16:52:00 on BOOLEAN
Script: D:\MoE\TEIS_environment_v7_20150109\Scripts\CreateAllTemplatesAndMetadataReports.py
Input Location: D:\MoE\TEIS_environment_v7_20150109\Tools_and_Templates.gdb
TEI_Project_Boundaries contains Terrestrial Ecosystem Information (TEI) 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, plot files, legends). This feature class is derived from TEI_Long_Tbl and TEIS_Project_Details. TEI inventories describe the physical and biological attributes of ecosystems. COMMENTS: Renamed from STE_TEI_PROJECT_BOUNDARIES_SP for distribution via TEI_Share and the TEI_Data_GDB.zip file on Distribution, and for info requests.
Table created 3/21/2011.This feature class is of type POLYGON, and is projected to NAD_1983_BC_Environment_Albers.
There are 4117 FGDB bytes, and 4113 SDE Bytes per row.
Item MetaData ID 18 (Report Item 1)
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. Examples include: 1234.
It is unknown when this item was added. This item should be INDEXED, and is MANDATORY. COMMENTS: must correspond with Project boundary feature class
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | BAPID | Business Area Project ID |
ArcSDE (BCGW) | BUSINESS_AREA_PROJECT_ID | BUSINESS_AREA_PROJECT_ID |
Oracle (BCGW) | BAPID | BUSINESS_AREA_PROJECT_ID |
E00 (Coverage) | BAPID | None |
RISC Standard | BAPID | Business Area Project ID |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | Integer | 4 | 0 | 0 |
ArcSDE (BCGW) | Integer | 4 | 0 | 0 |
Oracle (BCGW) | NUMBER | 5 | ||
E00 (Coverage) | I | 5 | 5 |
Item Definition (Operational Metadata) |
---|
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. |
FGDB (Operational) |
This field contains a unique project identifier. The project BAPID is used in all .e00 files. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
This field contains a unique project identifier. The project BAPID is used in all spatial files. |
RISC Standard Instructions |
If not already done, request a project BAPID from Soilterrain@victoria1.gov.bc.ca |
Item MetaData ID 3 (Report Item 2)
contains a 3-9 letter code indicating the specific type of mapping and attributes gathered for the project. Examples include: TEM, PEM, SEI, TIM, TSM, TBT, TEMSEI, TEMNSS and PRETEM.
This item was added on 7/1/2008. This item should be INDEXED, and is MANDATORY. This item is restricted to the Project_Type DOMAIN. COMMENTS: Width was changed from 6 to 9 based on e-mail/feedback Oct, 2009.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | PROJ_TYPE | Project Type |
ArcSDE (BCGW) | PROJECT_TYPE | PROJECT_TYPE |
Oracle (BCGW) | PROJ_TYPE | PROJECT_TYPE |
E00 (Coverage) | PROJ_TYPE | None |
RISC Standard | PROJ_TYPE | Project Type |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 9 | 0 | 0 |
ArcSDE (BCGW) | String | 9 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 9 | ||
E00 (Coverage) | C | 9 | 9 |
Item Definition (Operational Metadata) |
---|
contains a 3-9 letter code indicating the specific type of mapping and attributes gathered for the project. |
FGDB (Operational) |
A nine letter code indicating the type of mapping project. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
A nine letter code indicating the type of mapping project. |
RISC Standard Instructions |
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. |
Item MetaData ID 20 (Report Item 3)
contains the common name of the project, usually a well known local place or feature. Examples include: Penticton Cr, and Kelowna South Slopes.
It is unknown when this item was added. This item should not be indexed, and is MANDATORY.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | PROJ_NAME | Project Name |
ArcSDE (BCGW) | PROJECT_NAME | PROJECT_NAME |
Oracle (BCGW) | PROJ_NAME | PROJECT_NAME |
E00 (Coverage) | PROJ_NAME | None |
RISC Standard | PROJ_NAME | Project Name |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 100 | 0 | 0 |
ArcSDE (BCGW) | String | 100 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 100 | ||
E00 (Coverage) | C | 100 | 100 |
Item Definition (Operational Metadata) |
---|
contains the common name of the project, usually a well known local place or feature. |
FGDB (Operational) |
The common name of the project, usually a well known local place of feature. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
The common name of the project, usually a well known local place of feature. |
RISC Standard Instructions |
N/A |
Item MetaData ID 21 (Report Item 4)
contains the scale of the project maps produced. Examples include: 10000, 20000, 50000, and 100000.
This item was added on 1/1/2008. This item should be INDEXED, and is MANDATORY. This item has a minimum RANGE of 5000.0 and a maximum of 250000.0. 5000 to 250000 (Values outside of this scale range may be valid.)
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | PROJ_SCALE | Project Map Scale |
ArcSDE (BCGW) | PROJECT_MAP_SCALE | PROJECT_MAP_SCALE |
Oracle (BCGW) | PROJ_SCALE | PROJECT_MAP_SCALE |
E00 (Coverage) | PROJ_SCALE | None |
RISC Standard | PROJ_SCALE | Project Map Scale |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | Integer | 4 | 0 | 0 |
ArcSDE (BCGW) | Integer | 4 | 0 | 0 |
Oracle (BCGW) | NUMBER | 10 | ||
E00 (Coverage) | I | 8 | 8 |
Item Definition (Operational Metadata) |
---|
contains the scale of the project maps produced. |
FGDB (Operational) |
The scale of the project maps produced. For example, use 20000, not 1:20000 |
Oracle (BCGW) Metadata Description |
PROJECT_MAP_SCALE (aka PROJ_SCALE) contains the scale of the project maps produced. For example: 10000, 20000, 50000, and 100000. |
RISC Standard Description |
The scale of the project maps produced. For example, use 20000, not 1:20000 |
RISC Standard Instructions |
Renamed from 'Scale' |
Item MetaData ID 19 (Report Item 5)
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. Examples include: 3/28/2001.
It is unknown when this item was added. This item should not be indexed, and is not mandatory. COMMENTS: was called LOAD_DATE at one point; to be populated with the date last modified. The E00 date was set to 10 C (no reference found)
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | MOD_DATE | Modification Date |
ArcSDE (BCGW) | MODIFICATION_DATE | MODIFICATION_DATE |
Oracle (BCGW) | MOD_DATE | MODIFICATION_DATE |
E00 (Coverage) | MOD_DATE | None |
RISC Standard | MOD_DATE | Modification Date |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | Date | 8 | 0 | 0 |
ArcSDE (BCGW) | Date | 8 | 0 | 0 |
Oracle (BCGW) | DATE | 7 | ||
E00 (Coverage) | C | 10 | 10 |
Item Definition (Operational Metadata) |
---|
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. |
FGDB (Operational) |
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. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
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. |
RISC Standard Instructions |
N/A |
Item MetaData ID 423 (Report Item 6)
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. Examples are not available.
It is unknown when this item was added. This item should not be indexed, and is MANDATORY. COMMENTS: Duplicate GEOG_LOC/POLY_LOC (GEOG_LOC is preferred).
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | GEOG_LOC | Geographic Location |
ArcSDE (BCGW) | GEOGRAPHIC_LOCATION_NAME | GEOGRAPHIC_LOCATION_NAME |
Oracle (BCGW) | GEOG_LOC | GEOGRAPHIC_LOCATION_NAME |
E00 (Coverage) | GEOG_LOC | None |
RISC Standard | GEOG_LOC | Geographic Location |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 254 | 0 | 0 |
ArcSDE (BCGW) | String | 254 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 254 | ||
E00 (Coverage) | C | 254 | 254 |
Item Definition (Operational Metadata) |
---|
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. |
FGDB (Operational) |
The geographic location of the mapping project. This is a gazetted name taken from published map; for example, a town, lake, or watershed. |
Oracle (BCGW) Metadata Description |
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. For example: . |
RISC Standard Description |
The geographic location of the mapping project. This is a gazetted name taken from published map; for example, a town, lake, or watershed. |
RISC Standard Instructions |
N/A |
Item MetaData ID 319 (Report Item 7)
contains the date on which the project was completed. Examples include: 2007, 2007-04-14, or March 1999.
This item was added on 1/1/2008. This item should not be indexed, and is not mandatory. COMMENTS: The data type was string 10 at one point, should eventually become a DateTime when time and resources allow.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | COMPL_DATE | Project Completion Date |
ArcSDE (BCGW) | PROJECT_COMPLETION_DATE | PROJECT_COMPLETION_DATE |
Oracle (BCGW) | COMPL_DATE | PROJECT_COMPLETION_DATE |
E00 (Coverage) | COMPL_DATE | None |
RISC Standard | COMPL_DATE | Project Completion Date |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 20 | 0 | 0 |
ArcSDE (BCGW) | String | 20 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 20 | ||
E00 (Coverage) | C | 10 | 10 |
WIDTH WARNING: String items do not all have the same width.
Item Definition (Operational Metadata) |
---|
contains the date on which the project was completed. |
FGDB (Operational) |
The date on which the project was completed, Format: yyyy-mm-dd |
Oracle (BCGW) Metadata Description |
PROJECT_COMPLETION_DATE (aka COMPL_DATE) contains the date on which the project was completed. For example: 2007, 2007-04-14, or March 1999. |
RISC Standard Description |
The date on which the project was completed, Format: yyyy-mm-dd |
RISC Standard Instructions |
Renamed from 'Rec_date' |
Item MetaData ID 320 (Report Item 8)
contains the date or dates of field inventories. Examples include: June-July 2001, March 7 to 12, 1999.
It is unknown when this item was added. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | SURV_DATE | Date Surveyed |
ArcSDE (BCGW) | SURVEYED_DATES | SURVEYED_DATES |
Oracle (BCGW) | SURV_DATE | SURVEYED_DATES |
E00 (Coverage) | SURV_DATE | None |
RISC Standard | SURV_DATE | Date Surveyed |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 254 | 0 | 0 |
ArcSDE (BCGW) | String | 254 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 254 | ||
E00 (Coverage) | C | 254 | 254 |
Item Definition (Operational Metadata) |
---|
contains the date or dates of field inventories. |
FGDB (Operational) |
Date(s) of field inventory(s) |
Oracle (BCGW) Metadata Description |
SURVEYED_DATES (aka SURV_DATE) contains the date or dates of field inventories. For example: June-July 2001, March 7 to 12, 1999. |
RISC Standard Description |
Date(s) of field inventory(s) |
RISC Standard Instructions |
Include information about the months and years during which field surveys were conducted. |
Item MetaData ID 321 (Report Item 9)
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. Examples include: 1, 2, 3, 4, 5 or R.
This item was added on 7/1/2008. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | ESIL | Ecosystem Survey Intensity Level |
ArcSDE (BCGW) | ECOSYSTEM_SURVEY_INTENSITY_LVL | ECOSYSTEM_SURVEY_INTENSITY_LVL |
Oracle (BCGW) | ESIL | ECOSYSTEM_SURVEY_INTENSITY_LVL |
E00 (Coverage) | ESIL | None |
RISC Standard | ESIL | Ecosystem Survey Intensity Level |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 1 | 0 | 0 |
ArcSDE (BCGW) | String | 1 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 1 | ||
E00 (Coverage) | C | 1 | 1 |
Item Definition (Operational Metadata) |
---|
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. |
FGDB (Operational) |
The sampling intensity characterized according to percentage of polygons that have been field inspected or density of inspections by area. Coding must follow Table 6-3 in the Standard for Terrestrial Ecosystem Mapping in British Columbia. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
The sampling intensity characterized according to percentage of polygons that have been field inspected or density of inspections by area. Coding must follow Table 6-3 in the Standard for Terrestrial Ecosystem Mapping in British Columbia. |
RISC Standard Instructions |
N/A |
Item MetaData ID 322 (Report Item 10)
contains a character code representing the extent to which the terrain mapping for the current project has been checked on the ground. Examples include: A, B, C, D or E.
It is unknown when this item was added. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | TSIL | Terrain Survey Intensity Level |
ArcSDE (BCGW) | TERRAIN_SURVEY_INTENSITY_LVL | TERRAIN_SURVEY_INTENSITY_LVL |
Oracle (BCGW) | TSIL | TERRAIN_SURVEY_INTENSITY_LVL |
E00 (Coverage) | TSIL | None |
RISC Standard | TSIL | Terrain Survey Intensity Level |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 1 | 0 | 0 |
ArcSDE (BCGW) | String | 1 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 1 | ||
E00 (Coverage) | C | 1 | 1 |
Item Definition (Operational Metadata) |
---|
contains a character code representing the extent to which the terrain mapping for the current project has been checked on the ground. |
FGDB (Operational) |
The extent to which the terrain mapping for the current project has been checked on the ground. See Table: Terrain Survey Intensity Level. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
The extent to which the terrain mapping for the current project has been checked on the ground. See Table: Terrain Survey Intensity Level. |
RISC Standard Instructions |
If project has more than one TSIL then indicate the lowest TSIL and not in Proj_Com. |
Item MetaData ID 525 (Report Item 11)
contains a number from 1-6 based on the level of accuracy assessment used. Examples include: 1, 2, 3, 4, 5, or 6.
This item was added on 12/12/2012. This item should not be indexed, and is not mandatory. This item is restricted to the Accuracy_Assessment_Level DOMAIN. COMMENTS: Replaces the ACCURACY field.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | AA_LEVEL | Accuracy Assessment Level |
ArcSDE (BCGW) | ACCURACY_ASSESSMENT_LVL | ACCURACY_ASSESSMENT_LVL |
Oracle (BCGW) | ACCURACY | ACCURACY_ASSESSMENT_LVL |
E00 (Coverage) | ACCURACY | None |
RISC Standard | ACCURACY | Accuracy Assessment Level |
SHORT NAME WARNING: The FGDB_Name and RISC_Short_Name do not match.
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | SmallInteger | 2 | 0 | 0 |
ArcSDE (BCGW) | SmallInteger | 2 | 0 | 0 |
Oracle (BCGW) | NUMBER | 1 | ||
E00 (Coverage) | I | 1 | 1 |
Item Definition (Operational Metadata) |
---|
contains a number from 1-6 based on the level of accuracy assessment used. |
FGDB (Operational) |
A number from 1-6 based level of accuracy assessment used. See Protocol fro quality assurance and accuracy assessment of ecosystem maps. Draft. On (Meidinger, 1999). |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
A number from 1-6 based level of accuracy assessment used. See Protocol for quality assurance and accuracy assessment of ecosystem maps. Draft. On (Meidinger, 1999). |
RISC Standard Instructions |
New field for Terrain. |
Item MetaData ID 323 (Report Item 12)
contains information about the accuracy assessment methodology, assessment type or other information relating to the accuracy assessment. Examples include: ""The assessment tested the accuracy of the PEM product for its utility for wildlife habitat rating"".
It is unknown when this item was added. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | AA_COM | Accuracy Assessment Comments |
ArcSDE (BCGW) | ACCURACY_ASSESSMENT_COMMENTS | ACCURACY_ASSESSMENT_COMMENTS |
Oracle (BCGW) | AA_COM | ACCURACY_ASSESSMENT_COMMENTS |
E00 (Coverage) | AA_COM | None |
RISC Standard | AA_COM | Accuracy Assessment Comments |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 254 | 0 | 0 |
ArcSDE (BCGW) | String | 254 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 254 | ||
E00 (Coverage) | C | 254 | 254 |
Item Definition (Operational Metadata) |
---|
contains information about the accuracy assessment methodology, assessment type or other information relating to the accuracy assessment. |
FGDB (Operational) |
Contains information about the accuracy assessment methodology, assessment type or other information relating to the accuracy assessment. |
Oracle (BCGW) Metadata Description |
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"". |
RISC Standard Description |
contains information about the accuracy assessment methodology, assessment type or other information relating to the accuracy assessment. |
RISC Standard Instructions |
N/A |
Item MetaData ID 324 (Report Item 13)
Examples include: 103A096 103H006, 93G001-023 or 93A061-62-71.
This item was added on 1/1/2006. This item should not be indexed, and is not mandatory. COMMENTS: This was removed from the LRDW data to accomodate the 4096 export limit for coverages. It is also a field that is expected to be removed once all data cleanup is complete (replaced by spatial query).
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | MAPSH_LST | Mapsheet List |
ArcSDE (BCGW) | MAPSHEET_LIST | MAPSHEET_LIST |
Oracle (BCGW) | MAPSH_LST | MAPSHEET_LIST |
E00 (Coverage) | MAPSH_LST | None |
RISC Standard | MAPSH_LST | Mapsheet List |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 254 | 0 | 0 |
ArcSDE (BCGW) | String | 254 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 254 | ||
E00 (Coverage) | C | 254 | 254 |
Item Definition (Operational Metadata) |
---|
N/A |
FGDB (Operational) |
The mapsheet(s) in the project. See Table: Map Number Recording Convention. |
Oracle (BCGW) Metadata Description |
MAPSHEET_LIST (aka MAPSH_LST) For example: 103A096 103H006, 93G001-023 or 93A061-62-71. |
RISC Standard Description |
The mapsheet(s) in the project. See Table: Map Number Recording Convention. |
RISC Standard Instructions |
A leading zero is required for mapsheets not starting with 1. Left justified with no decimal or / separator. E.g., 083E073. Caution: ensure this is a character field if data is first captured in Excel, as mapsheet. |
Item MetaData ID 325 (Report Item 14)
contains the name of the public or private-sector organization responsible for the mapping project. Examples include: MOE Wildlife Habitat Section and Timberline Natural Resource Group Ltd..
It is unknown when this item was added. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | ORG_NAME | Consultant or Organization |
ArcSDE (BCGW) | RESPONSIBLE_ORGANIZATION_NAME | RESPONSIBLE_ORGANIZATION_NAME |
Oracle (BCGW) | ORG_NAME | RESPONSIBLE_ORGANIZATION_NAME |
E00 (Coverage) | ORG_NAME | None |
RISC Standard | ORG_NAME | Consultant or Organization |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 80 | 0 | 0 |
ArcSDE (BCGW) | String | 80 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 80 | ||
E00 (Coverage) | C | 80 | 80 |
Item Definition (Operational Metadata) |
---|
contains the name of the public or private-sector organization responsible for the mapping project. |
FGDB (Operational) |
The public or private-sector organization responsible for the mapping project. |
Oracle (BCGW) Metadata Description |
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.. |
RISC Standard Description |
The public or private-sector organization responsible for the mapping project. |
RISC Standard Instructions |
N/A |
Item MetaData ID 326 (Report Item 15)
contains the name of the professional responsible for project sign off. Examples include: Deepa Filatow, P.Geo..
This item was added on 7/1/2008. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | PROJ_SUP | Project Supervisor |
ArcSDE (BCGW) | PROJECT_SUPERVISOR_NAME | PROJECT_SUPERVISOR_NAME |
Oracle (BCGW) | PROJ_SUP | PROJECT_SUPERVISOR_NAME |
E00 (Coverage) | PROJ_SUP | None |
RISC Standard | PROJ_SUP | Project Supervisor |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 80 | 0 | 0 |
ArcSDE (BCGW) | String | 80 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 80 | ||
E00 (Coverage) | C | 80 | 80 |
Item Definition (Operational Metadata) |
---|
contains the name of the professional responsible for project sign off. |
FGDB (Operational) |
The professional responsible for project signoff. |
Oracle (BCGW) Metadata Description |
PROJECT_SUPERVISOR_NAME (aka PROJ_SUP) contains the name of the professional responsible for project sign off. For example: Deepa Filatow, P.Geo.. |
RISC Standard Description |
The projessional responsible for project signoff. |
RISC Standard Instructions |
New field for Terrain. |
Item MetaData ID 327 (Report Item 16)
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. Examples include: Corey Erwin, R.P.Bio..
It is unknown when this item was added. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | ECO_MAP | Ecosystem Mapper or Modeller |
ArcSDE (BCGW) | ECOSYSTEM_MAPPER_NAME | ECOSYSTEM_MAPPER_NAME |
Oracle (BCGW) | ECO_MAP | ECOSYSTEM_MAPPER_NAME |
E00 (Coverage) | ECO_MAP | None |
RISC Standard | ECO_MAP | Ecosystem Mapper or Modeller |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 80 | 0 | 0 |
ArcSDE (BCGW) | String | 80 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 80 | ||
E00 (Coverage) | C | 80 | 80 |
Item Definition (Operational Metadata) |
---|
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. |
FGDB (Operational) |
The person who originally captured the Terrestrial Ecosystem Mapping data. |
Oracle (BCGW) Metadata Description |
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.. |
RISC Standard Description |
The person who originally captured the Terrestrial Ecosystem Mapping data. |
RISC Standard Instructions |
N/A |
Item MetaData ID 328 (Report Item 17)
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. Examples include: Sid Tsang, P.Geo..
This item was added on 1/1/2008. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | TER_MAP | Terrain Mapper |
ArcSDE (BCGW) | TERRAIN_MAPPER_NAME | TERRAIN_MAPPER_NAME |
Oracle (BCGW) | TER_MAP | TERRAIN_MAPPER_NAME |
E00 (Coverage) | TER_MAP | None |
RISC Standard | TER_MAP | Terrain Mapper |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 80 | 0 | 0 |
ArcSDE (BCGW) | String | 80 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 80 | ||
E00 (Coverage) | C | 80 | 80 |
Item Definition (Operational Metadata) |
---|
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. |
FGDB (Operational) |
The licenced professional who has done the terrain mapping (polygon delineation and pretyping/typing). Where there is more than one mapper on a project, this is the name of the project leader. |
Oracle (BCGW) Metadata Description |
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.. |
RISC Standard Description |
The licenced professional who has done the terrain mapping (polygon delineation and pretyping/typing). Where there is more than one mapper on a project, this is the name of the project leader. |
RISC Standard Instructions |
N/A |
Item MetaData ID 418 (Report Item 18)
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. Examples include: Robert Maxwell, P.Ag..
This item was added on 10/6/2009. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | SOIL_MAP | Soil Mapper Name |
ArcSDE (BCGW) | SOIL_MAPPER_NAME | SOIL_MAPPER_NAME |
Oracle (BCGW) | SOIL_MAP | SOIL_MAPPER_NAME |
E00 (Coverage) | SOIL_MAP | None |
RISC Standard | SOIL_MAP | Soil Mapper Name |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 80 | 0 | 0 |
ArcSDE (BCGW) | String | 80 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 80 | ||
E00 (Coverage) | C | 80 | 80 |
Item Definition (Operational Metadata) |
---|
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. |
FGDB (Operational) |
Soil Surveyor or Mapper: 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. |
Oracle (BCGW) Metadata Description |
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.. |
RISC Standard Description |
The licenced professional who has done the soil mapping (polygon delineation and pretyping/typing). Where there is more than one mapper on a project, this is the name of the project leader. |
RISC Standard Instructions |
N/A |
Item MetaData ID 419 (Report Item 19)
contains the licenced professional who has done the wildlife mapping (species account, wildlife habitat ratings, wildlife report, rating models). Where there is more than one mapper on a project, this is the name of the project leader. Examples include: Calvin Tolkamp, R.P.Bio.
This item was added on 10/6/2009. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | WILD_MAP | Wildlife Mapper Name |
ArcSDE (BCGW) | WILDLIFE_MAPPER_NAME | WILDLIFE_MAPPER_NAME |
Oracle (BCGW) | WILD_MAP | WILDLIFE_MAPPER_NAME |
E00 (Coverage) | WILD_MAP | None |
RISC Standard | WILD_MAP | Wildlife Mapper Name |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 80 | 0 | 0 |
ArcSDE (BCGW) | String | 80 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 80 | ||
E00 (Coverage) | C | 80 | 80 |
Item Definition (Operational Metadata) |
---|
contains the licenced professional who has done the wildlife mapping (species account, wildlife habitat ratings, wildlife report, rating models). Where there is more than one mapper on a project, this is the name of the project leader. |
FGDB (Operational) |
Wildlife Habitat Mapper or Modeller: 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. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
The licenced professional who has done the wildlife mapping (species account, wildlife habitat ratings, wildlife report, rating models). Where there is more than one mapper on a project, this is the name of the project leader. |
RISC Standard Instructions |
N/A |
Item MetaData ID 329 (Report Item 20)
contains the name of the individual or organization responsible for digital capture of spatial data. Examples include: Chartwell Consultants Ltd..
This item was added on 7/1/2008. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | DIG_CAP | Digital Data Capture |
ArcSDE (BCGW) | DIGITAL_DATA_CAPTURE_NAME | DIGITAL_DATA_CAPTURE_NAME |
Oracle (BCGW) | DIG_CAP | DIGITAL_DATA_CAPTURE_NAME |
E00 (Coverage) | DIG_CAP | None |
RISC Standard | DIG_CAP | Digital Data Capture |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 125 | 0 | 0 |
ArcSDE (BCGW) | String | 125 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 125 | ||
E00 (Coverage) | C | 125 | 125 |
Item Definition (Operational Metadata) |
---|
contains the name of the individual or organization responsible for digital capture of spatial data. |
FGDB (Operational) |
The public or private-sector individual or organization responsible for digital capture of spatial data. For SEI data, this field is used if SE data is mapped stereomodelled from TEM or other images; if SE data istraditionally from mapping, refer to t |
Oracle (BCGW) Metadata Description |
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.. |
RISC Standard Description |
The public or private-sector individual or organization responsible for digital capture of spatial data. For SEI data, this field is used if SE data is mapped stereomodelled from TEM or other images; if SE data is traditionally from mapping, refer to t |
RISC Standard Instructions |
New field for Terrain. |
Item MetaData ID 330 (Report Item 21)
contains the name of the individual responsible for sign-off on the spatial digital data. Examples include: Jason Kubian.
This item was added on 7/1/2008. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | GIS_SUP | GIS Supervisor |
ArcSDE (BCGW) | GIS_SUPERVISOR_NAME | GIS_SUPERVISOR_NAME |
Oracle (BCGW) | GIS_SUP | GIS_SUPERVISOR_NAME |
E00 (Coverage) | GIS_SUP | None |
RISC Standard | GIS_SUP | GIS Supervisor |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 80 | 0 | 0 |
ArcSDE (BCGW) | String | 80 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 80 | ||
E00 (Coverage) | C | 80 | 80 |
Item Definition (Operational Metadata) |
---|
contains the name of the individual responsible for sign-off on the spatial digital data. |
FGDB (Operational) |
The public or private-sector individual responsible for sign off on the spatial digital data. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
The public or private-sector individual responsible for sign off on the spatial digital data. |
RISC Standard Instructions |
N/A |
Item MetaData ID 331 (Report Item 22)
contains the name(s) of the person(s) who entered the project and polygon attribute data into a database. Examples include: Tony Button, Jo-Anne Stacey and Maija Finvers.
It is unknown when this item was added. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | REC_NAME | Recorder Name |
ArcSDE (BCGW) | RECORDER_NAME | RECORDER_NAME |
Oracle (BCGW) | REC_NAME | RECORDER_NAME |
E00 (Coverage) | REC_NAME | None |
RISC Standard | REC_NAME | Recorder Name |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 254 | 0 | 0 |
ArcSDE (BCGW) | String | 254 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 254 | ||
E00 (Coverage) | C | 254 | 254 |
Item Definition (Operational Metadata) |
---|
contains the name(s) of the person(s) who entered the project and polygon attribute data into a database. |
FGDB (Operational) |
The person(s) who entered the project and polygon attribute data into a database. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
The person(s) who entered the project and polygon attribute data into a database. |
RISC Standard Instructions |
N/A |
Item MetaData ID 332 (Report Item 23)
contains the name of the client for whom the project was completed. Examples include: Tolko Industries Ltd..
This item was added on 7/1/2008. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | CLIENT | Client |
ArcSDE (BCGW) | PROJECT_CLIENT_NAME | PROJECT_CLIENT_NAME |
Oracle (BCGW) | CLIENT | PROJECT_CLIENT_NAME |
E00 (Coverage) | CLIENT | None |
RISC Standard | CLIENT | Client |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 80 | 0 | 0 |
ArcSDE (BCGW) | String | 80 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 80 | ||
E00 (Coverage) | C | 80 | 80 |
Item Definition (Operational Metadata) |
---|
contains the name of the client for whom the project was completed. |
FGDB (Operational) |
The client (public or private organization) for whom the project was completed. |
Oracle (BCGW) Metadata Description |
PROJECT_CLIENT_NAME (aka CLIENT) contains the name of the client for whom the project was completed. For example: Tolko Industries Ltd.. |
RISC Standard Description |
The client (public or private organization) for whom the project was completed. |
RISC Standard Instructions |
N/A |
Item MetaData ID 333 (Report Item 24)
contains a one-digit integer representing the version of TRIM mapping used for the project. Examples include: 1 or 2.
This item was added on 7/1/2008. This item should not be indexed, and is not mandatory. This item is restricted to the TRIM_Version DOMAIN.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | TRIM_NBR | TRIM Version |
ArcSDE (BCGW) | TRIM_VERSION_NUMBER | TRIM_VERSION_NUMBER |
Oracle (BCGW) | TRIM_NBR | TRIM_VERSION_NUMBER |
E00 (Coverage) | TRIM_NBR | None |
RISC Standard | TRIM_NBR | TRIM Version |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 1 | 0 | 0 |
ArcSDE (BCGW) | String | 1 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 1 | ||
E00 (Coverage) | C | 1 | 1 |
Item Definition (Operational Metadata) |
---|
contains a one-digit integer representing the version of TRIM mapping used for the project. |
FGDB (Operational) |
The version of TRIM mapsheets used for the project mapping. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
The version of TRIM mapsheets used for the project mapping. |
RISC Standard Instructions |
N/A |
Item MetaData ID 334 (Report Item 25)
contains a one-character code indicating specific details about the image type from which the mapped information was interpreted. Examples include: 1 (colour airphoto), 2 (black and white airphoto), 3 (digital colour airphoto), 4 (digital black and white airphoto), 5 (orthophoto), or 6 (landsat).
This item was added on 7/1/2008. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | PHO_TYPE | Image Type |
ArcSDE (BCGW) | IMAGE_TYPE | IMAGE_TYPE |
Oracle (BCGW) | PHO_TYPE | IMAGE_TYPE |
E00 (Coverage) | PHO_TYPE | None |
RISC Standard | PHO_TYPE | Image Type |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 1 | 0 | 0 |
ArcSDE (BCGW) | String | 1 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 1 | ||
E00 (Coverage) | C | 1 | 1 |
Item Definition (Operational Metadata) |
---|
contains a one-character code indicating specific details about the image type from which the mapped information was interpreted. |
FGDB (Operational) |
Indicates specific details about the image type. |
Oracle (BCGW) Metadata Description |
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). |
RISC Standard Description |
Indicates specific details about the image type. |
RISC Standard Instructions |
N/A |
Item MetaData ID 335 (Report Item 26)
contains the scale of air photos/images used for polygon delineation and pre-typing. Examples include: 20000, 50000 or 100000.
This item was added on 7/1/2008. This item should not be indexed, and is not mandatory. This item has a minimum RANGE of 5000.0 and a maximum of 250000.0. 5000 to 250000 (Values outside of this scale range may be valid.) COMMENTS: This should become an integer in all locations when data cleanup funds allow (was string(8)).
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | PHO_SC | Image Scale |
ArcSDE (BCGW) | IMAGE_SCALE | IMAGE_SCALE |
Oracle (BCGW) | PHO_SC | IMAGE_SCALE |
E00 (Coverage) | PHO_SC | None |
RISC Standard | PHO_SC | Image Scale |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 8 | 0 | 0 |
ArcSDE (BCGW) | Integer | 4 | 0 | 0 |
Oracle (BCGW) | NUMBER | 10 | ||
E00 (Coverage) | C | 8 | 8 |
WIDTH WARNING: String items do not all have the same width.
Item Definition (Operational Metadata) |
---|
contains the scale of air photos/images used for polygon delineation and pre-typing. |
FGDB (Operational) |
Scale of air photos/images used for polygon delineation and pre-typing. For example, 20000 represents 1:20000. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
Scale of air photos/images used for polygon delineation and pre-typing. For example, 20000 represents 1:20000. |
RISC Standard Instructions |
N/A |
Item MetaData ID 336 (Report Item 27)
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. Examples include: 1996.
This item was added on 7/1/2008. This item should not be indexed, and is not mandatory. This item has a minimum RANGE of 1950.0 and a maximum of 2011.0. 1950 to 2011 (Items outside of this range may be valid. The range may change.)
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | PHO_YR | Image Year |
ArcSDE (BCGW) | IMAGE_YEAR | IMAGE_YEAR |
Oracle (BCGW) | PHO_YR | IMAGE_YEAR |
E00 (Coverage) | PHO_YR | None |
RISC Standard | PHO_YR | Image Year |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | SmallInteger | 2 | 0 | 0 |
ArcSDE (BCGW) | SmallInteger | 2 | 0 | 0 |
Oracle (BCGW) | NUMBER | 4 | ||
E00 (Coverage) | I | 4 | 4 |
Item Definition (Operational Metadata) |
---|
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. |
FGDB (Operational) |
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. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
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. |
RISC Standard Instructions |
N/A |
Item MetaData ID 337 (Report Item 28)
contains a reference to the origin of a customized legend, if utilizing a legend developed for another project. Examples include: D. Filatow, 1999, Boundary Forest District Recon TSM Project, Appendix 2.
This item was added on 1/1/2008. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | TER_LEG_SC | Terrain Legend Source |
ArcSDE (BCGW) | TERRAIN_LEGEND_SOURCE | TERRAIN_LEGEND_SOURCE |
Oracle (BCGW) | TER_LEG_SC | TERRAIN_LEGEND_SOURCE |
E00 (Coverage) | TER_LEG_SC | None |
RISC Standard | TER_LEG_SC | Terrain Legend Source |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 50 | 0 | 0 |
ArcSDE (BCGW) | String | 50 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 50 | ||
E00 (Coverage) | C | 50 | 50 |
Item Definition (Operational Metadata) |
---|
contains a reference to the origin of a customized legend, if utilizing a legend developed for another project. |
FGDB (Operational) |
The origin of a customized legend, if utilizing a legend developed for another project. See Table: Metadata for Header on Data Form. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
The origin of a customized legend, if utilizing a legend developed for another project. See Table: Metadata for Header on Data Form. |
RISC Standard Instructions |
N/A |
Item MetaData ID 338 (Report Item 29)
contains a 1-3 letter code indicating the type of legend associated with the map. Examples include: G (general), S (short), TS (terrain stability), O (other) or C (custom) .
This item was added on 1/1/2008. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | TER_LEG_TP | Terrain Legend Type |
ArcSDE (BCGW) | TERRAIN_LEGEND_TYPE | TERRAIN_LEGEND_TYPE |
Oracle (BCGW) | TER_LEG_TP | TERRAIN_LEGEND_TYPE |
E00 (Coverage) | TER_LEG_TP | None |
RISC Standard | TER_LEG_TP | Terrain Legend Type |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 3 | 0 | 0 |
ArcSDE (BCGW) | String | 3 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 3 | ||
E00 (Coverage) | C | 3 | 3 |
Item Definition (Operational Metadata) |
---|
contains a 1-3 letter code indicating the type of legend associated with the map. |
FGDB (Operational) |
The type of legend associated with the map; refer to the Terrain Mapping Methodology (RIC) for legend format and specifications. |
Oracle (BCGW) Metadata Description |
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) . |
RISC Standard Description |
The type of legend associated with the map; refer to the Terrain Mapping Methodology (RIC) for legend format and specifications. |
RISC Standard Instructions |
N/A |
Item MetaData ID 339 (Report Item 30)
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. Examples include: 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)). .
This item was added on 7/1/2008. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | PACK_NBR | Version of Package Used |
ArcSDE (BCGW) | VERSION_OF_PACKAGE_USED | VERSION_OF_PACKAGE_USED |
Oracle (BCGW) | PACK_NBR | VERSION_OF_PACKAGE_USED |
E00 (Coverage) | PACK_NBR | None |
RISC Standard | PACK_NBR | Version of Package Used |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 2 | 0 | 0 |
ArcSDE (BCGW) | String | 2 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 2 | ||
E00 (Coverage) | C | 2 | 2 |
Item Definition (Operational Metadata) |
---|
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. |
FGDB (Operational) |
Versions of standards used for project mapping. As codes have changedover time, indicates the versions of manuals used for the project. |
Oracle (BCGW) Metadata Description |
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)).
. |
RISC Standard Description |
Versions of standards used for project mapping. As codes have changed over time, indicates the versions of manuals used for the project. |
RISC Standard Instructions |
N/A |
Item MetaData ID 340 (Report Item 31)
contains a one character code indicating the classification system used to classify slope stability for the current project. Examples include: R (Reconnaissance), D (Detailed), or E (Es).
It is unknown when this item was added. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | STBCLS_TP | Stability Classification Type |
ArcSDE (BCGW) | STABILITY_CLASSIFICATION_TYPE | STABILITY_CLASSIFICATION_TYPE |
Oracle (BCGW) | STBCLS_TP | STABILITY_CLASSIFICATION_TYPE |
E00 (Coverage) | STBCLS_TP | None |
RISC Standard | STBCLS_TP | Stability Classification Type |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 1 | 0 | 0 |
ArcSDE (BCGW) | String | 1 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 1 | ||
E00 (Coverage) | C | 1 | 1 |
Item Definition (Operational Metadata) |
---|
contains a one character code indicating the classification system used to classify slope stability for the current project. |
FGDB (Operational) |
The classification system used to classify slope stability for the current project. Indicate only one of the following with an (R) Recon, (D) Detailed, or (E) Es. |
Oracle (BCGW) Metadata Description |
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). |
RISC Standard Description |
The classification system used to classify slope stability for the current project. Indicate only one of the following with an (R) Recon, (D) Detailed, or (E) Es. |
RISC Standard Instructions |
N/A |
Item MetaData ID 341 (Report Item 32)
contains a one character code indicating the type of slope units used. Examples include: P (Percent) or D (Degree).
It is unknown when this item was added. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | SLP_UNIT | Slope Units |
ArcSDE (BCGW) | SLOPE_UNIT | SLOPE_UNIT |
Oracle (BCGW) | SLP_UNIT | SLOPE_UNIT |
E00 (Coverage) | SLP_UNIT | None |
RISC Standard | SLP_UNIT | Slope Units |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 1 | 0 | 0 |
ArcSDE (BCGW) | String | 1 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 1 | ||
E00 (Coverage) | C | 1 | 1 |
Item Definition (Operational Metadata) |
---|
contains a one character code indicating the type of slope units used. |
FGDB (Operational) |
The type of units, if slope classes were done for this database, percent or degrees denoting slope steepness. See able: Metadata for Header on Data Form and see Table: Slope Steepness. |
Oracle (BCGW) Metadata Description |
SLOPE_UNIT (aka SLP_UNIT) contains a one character code indicating the type of slope units used. For example: P (Percent) or D (Degree). |
RISC Standard Description |
The type of units, if slope classes were done for this database, percent or degrees denoting slope steepness. See Table: Metadata for Header on Data Form and see Table: Slope Steepness. |
RISC Standard Instructions |
The same units must be used for all slope steepness values in a given project. Indicate one of the following with a (P) Percent, (D) Degrees or (N) Null. |
Item MetaData ID 342 (Report Item 33)
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. Examples include: 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..
This item was added on 1/1/2008. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | PROJ_COM | Project Comments |
ArcSDE (BCGW) | PROJECT_COMMENTS | PROJECT_COMMENTS |
Oracle (BCGW) | PROJ_COM | PROJECT_COMMENTS |
E00 (Coverage) | PROJ_COM | None |
RISC Standard | PROJ_COM | Project Comments |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 254 | 0 | 0 |
ArcSDE (BCGW) | String | 254 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 254 | ||
E00 (Coverage) | C | 254 | 254 |
Item Definition (Operational Metadata) |
---|
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. |
FGDB (Operational) |
This field records 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 u |
Oracle (BCGW) Metadata Description |
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.. |
RISC Standard Description |
This field records 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 u |
RISC Standard Instructions |
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 identify user defined data files or other documents associated with |
Item MetaData ID 343 (Report Item 34)
contains a unique five-character identifier (project short name) for each project being delivered. Examples include: WILLW.
It is unknown when this item was added. This item should be INDEXED, and is MANDATORY. COMMENTS: This field will be populated in the long table so it should be a straight across? No?
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | PROJ_ID | Project Identification |
ArcSDE (BCGW) | PROJECT_IDENTIFICATION | PROJECT_IDENTIFICATION |
Oracle (BCGW) | PROJ_ID | PROJECT_IDENTIFICATION |
E00 (Coverage) | PROJ_ID | None |
RISC Standard | PROJ_ID | Project Identification |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 5 | 0 | 0 |
ArcSDE (BCGW) | String | 5 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 5 | ||
E00 (Coverage) | C | 5 | 5 |
Item Definition (Operational Metadata) |
---|
contains a unique five-character identifier (project short name) for each project being delivered. |
FGDB (Operational) |
A unique identifier (project short name) for each project being delievered. See Section: Digital Data Specification and Table: Metadata for Header on Data Form. |
Oracle (BCGW) Metadata Description |
PROJECT_IDENTIFICATION (aka PROJ_ID) contains a unique five-character identifier (project short name) for each project being delivered. For example: WILLW. |
RISC Standard Description |
Contains a unique five-character identifier (project short name) for each project being delivered. |
RISC Standard Instructions |
N/A |
Item MetaData ID 344 (Report Item 35)
contains a description of the generic map legend found at MAP LEGEND DATA DOWNLOAD LINK (MAP_LEG). Examples include: Information on how to interpret terrain labels is available at the following site..
It is unknown when this item was added. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | LEGEND_COM | Map Legend Comments |
ArcSDE (BCGW) | MAP_LEGEND_DESCRIPTION | MAP_LEGEND_DESCRIPTION |
Oracle (BCGW) | LEGEND_COM | MAP_LEGEND_DESCRIPTION |
E00 (Coverage) | LEGEND_COM | None |
RISC Standard | LEGEND_COM | Map Legend Comments |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 140 | 0 | 0 |
ArcSDE (BCGW) | String | 140 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 140 | ||
E00 (Coverage) | C | 140 | 140 |
Item Definition (Operational Metadata) |
---|
contains a description of the generic map legend found at MAP LEGEND DATA DOWNLOAD LINK (MAP_LEG). |
FGDB (Operational) |
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. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
contains a description of the generic map legend found at MAP LEGEND DATA DOWNLOAD LINK (MAP_LEG). |
RISC Standard Instructions |
N/A |
Item MetaData ID 24 (Report Item 36)
contains the URL for the website or FTP site where the generic map legend is available. Examples include: http://a100.gov.bc.ca/pub/acat/public/viewReport.do?reportId=1531.
It is unknown when this item was added. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | LEGEND_URL | Map Legend Link |
ArcSDE (BCGW) | MAP_LEGEND_DATA_DOWNLOAD_LINK | MAP_LEGEND_DATA_DOWNLOAD_LINK |
Oracle (BCGW) | LEGEND_URL | MAP_LEGEND_DATA_DOWNLOAD_LINK |
E00 (Coverage) | LEGEND_URL | None |
RISC Standard | LEGEND_URL | Map Legend Link |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 100 | 0 | 0 |
ArcSDE (BCGW) | String | 100 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 100 | ||
E00 (Coverage) | C | 100 | 100 |
Item Definition (Operational Metadata) |
---|
contains the URL for the website or FTP site where the generic map legend is available. |
FGDB (Operational) |
Contains a link to an internet resource related to the map legend or compliation methods. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
Contains a link to an internet resource related to the map legend or compilation methods. |
RISC Standard Instructions |
N/A |
Item MetaData ID 346 (Report Item 37)
contains a description of the Ecological Reports Catalogue (EcoCat) link found at ECOCAT URL DATA DOWNLOAD LINK (ECOCAT_URL). Examples include: Project related data is available from the EcoCat site.
It is unknown when this item was added. This item should not be indexed, and is not mandatory. COMMENTS: Width was changed from 254 to 200 based on e-mail/feedback Oct, 2009.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | ECOCAT_COM | EcoCat Comments |
ArcSDE (BCGW) | ECOCAT_DATA_DESCRIPTION | ECOCAT_DATA_DESCRIPTION |
Oracle (BCGW) | ECOCAT_COM | ECOCAT_DATA_DESCRIPTION |
E00 (Coverage) | ECOCAT_COM | None |
RISC Standard | ECOCAT_COM | EcoCat Comments |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 200 | 0 | 0 |
ArcSDE (BCGW) | String | 200 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 200 | ||
E00 (Coverage) | C | 200 | 200 |
Item Definition (Operational Metadata) |
---|
contains a description of the Ecological Reports Catalogue (EcoCat) link found at ECOCAT URL DATA DOWNLOAD LINK (ECOCAT_URL). |
FGDB (Operational) |
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. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
contains a description of the Ecological Reports Catalogue (EcoCat) link found at ECOCAT URL DATA DOWNLOAD LINK (ECOCAT_URL). |
RISC Standard Instructions |
N/A |
Item MetaData ID 347 (Report Item 38)
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. Examples include: 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.
It is unknown when this item was added. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | ECOCAT_URL | EcoCat Link |
ArcSDE (BCGW) | ECOCAT_URL_DATA_DOWNLOAD_LINK | ECOCAT_URL_DATA_DOWNLOAD_LINK |
Oracle (BCGW) | ECOCAT_URL | ECOCAT_URL_DATA_DOWNLOAD_LINK |
E00 (Coverage) | ECOCAT_URL | None |
RISC Standard | ECOCAT_URL | EcoCat Link |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 100 | 0 | 0 |
ArcSDE (BCGW) | String | 100 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 100 | ||
E00 (Coverage) | C | 100 | 100 |
Item Definition (Operational Metadata) |
---|
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. |
FGDB (Operational) |
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 |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
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. |
RISC Standard Instructions |
N/A |
Item MetaData ID 348 (Report Item 39)
contains a description of the link found at REFERENCE 1 DATA DOWNLOAD LINK (REF_1_URL). Examples include: Project report is available from the Ministry library, or Raster and/or PDF maps are available from the following FTP site.
It is unknown when this item was added. This item should not be indexed, and is not mandatory. COMMENTS: Width was changed to a standard of 100 based on e-mail/feedback Oct, 2009.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | REF_1_COM | Reference 1 Comments |
ArcSDE (BCGW) | REFERENCE_1_DATA_DESCRIPTION | REFERENCE_1_DATA_DESCRIPTION |
Oracle (BCGW) | REF_1_COM | REFERENCE_1_DATA_DESCRIPTION |
E00 (Coverage) | REF_1_COM | None |
RISC Standard | REF_1_COM | Reference 1 Comments |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 100 | 0 | 0 |
ArcSDE (BCGW) | String | 100 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 100 | ||
E00 (Coverage) | C | 100 | 100 |
Item Definition (Operational Metadata) |
---|
contains a description of the link found at REFERENCE 1 DATA DOWNLOAD LINK (REF_1_URL). |
FGDB (Operational) |
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 avavailable from the following FTP site. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
contains a description of the link found at REFERENCE 1 DATA DOWNLOAD LINK (REF_1_URL). |
RISC Standard Instructions |
N/A |
Item MetaData ID 349 (Report Item 40)
contains a URL to additional project information and/or files (not in the LRDW or EcoCat). Examples include: 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/.
It is unknown when this item was added. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | REF_1_URL | Reference 1 Link |
ArcSDE (BCGW) | REFERENCE_1_DATA_DOWNLOAD_LINK | REFERENCE_1_DATA_DOWNLOAD_LINK |
Oracle (BCGW) | REF_1_URL | REFERENCE_1_DATA_DOWNLOAD_LINK |
E00 (Coverage) | REF_1_URL | None |
RISC Standard | REF_1_URL | Reference 1 Link |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 100 | 0 | 0 |
ArcSDE (BCGW) | String | 100 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 100 | ||
E00 (Coverage) | C | 100 | 100 |
Item Definition (Operational Metadata) |
---|
contains a URL to additional project information and/or files (not in the LRDW or EcoCat). |
FGDB (Operational) |
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/ |
Oracle (BCGW) Metadata Description |
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/. |
RISC Standard Description |
contains a URL to additional project information and/or files (not in the LRDW or EcoCat). |
RISC Standard Instructions |
N/A |
Item MetaData ID 350 (Report Item 41)
contains a description of the link found at REFERENCE 2 DATA DOWNLOAD LINK (REF_2_URL). Examples include: Project report is available from the Ministry library, or Raster and/or PDF maps are available from the following FTP site.
It is unknown when this item was added. This item should not be indexed, and is not mandatory. COMMENTS: Width was changed to a standard of 100 based on e-mail/feedback Oct, 2009.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | REF_2_COM | Reference 2 Comments |
ArcSDE (BCGW) | REFERENCE_2_DATA_DESCRIPTION | REFERENCE_2_DATA_DESCRIPTION |
Oracle (BCGW) | REF_2_COM | REFERENCE_2_DATA_DESCRIPTION |
E00 (Coverage) | REF_2_COM | None |
RISC Standard | REF_2_COM | Reference 2 Comments |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 100 | 0 | 0 |
ArcSDE (BCGW) | String | 100 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 100 | ||
E00 (Coverage) | C | 100 | 100 |
Item Definition (Operational Metadata) |
---|
contains a description of the link found at REFERENCE 2 DATA DOWNLOAD LINK (REF_2_URL). |
FGDB (Operational) |
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 avavailable from the following FTP site. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
contains a description of the link found at REFERENCE 2 DATA DOWNLOAD LINK (REF_2_URL). |
RISC Standard Instructions |
N/A |
Item MetaData ID 351 (Report Item 42)
contains a URL to additional project information and/or files (not in the LRDW or EcoCat). Examples include: 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/.
It is unknown when this item was added. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | REF_2_URL | Reference 2 Link |
ArcSDE (BCGW) | REFERENCE_2_DATA_DOWNLOAD_LINK | REFERENCE_2_DATA_DOWNLOAD_LINK |
Oracle (BCGW) | REF_2_URL | REFERENCE_2_DATA_DOWNLOAD_LINK |
E00 (Coverage) | REF_2_URL | None |
RISC Standard | REF_2_URL | Reference 2 Link |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 100 | 0 | 0 |
ArcSDE (BCGW) | String | 100 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 100 | ||
E00 (Coverage) | C | 100 | 100 |
Item Definition (Operational Metadata) |
---|
contains a URL to additional project information and/or files (not in the LRDW or EcoCat). |
FGDB (Operational) |
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/ |
Oracle (BCGW) Metadata Description |
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/. |
RISC Standard Description |
contains a URL to additional project information and/or files (not in the LRDW or EcoCat). |
RISC Standard Instructions |
N/A |
Item MetaData ID 352 (Report Item 43)
contains a description of the link found at REFERENCE 3 DATA DOWNLOAD LINK (REF_3_URL). Examples include: Project report is available from the Ministry library, or Raster and/or PDF maps are available from the following FTP site.
It is unknown when this item was added. This item should not be indexed, and is not mandatory. COMMENTS: Width was changed to a standard of 100 based on e-mail/feedback Oct, 2009.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | REF_3_COM | Reference 3 Comments |
ArcSDE (BCGW) | REFERENCE_3_DATA_DESCRIPTION | REFERENCE_3_DATA_DESCRIPTION |
Oracle (BCGW) | REF_3_COM | REFERENCE_3_DATA_DESCRIPTION |
E00 (Coverage) | REF_3_COM | None |
RISC Standard | REF_3_COM | Reference 3 Comments |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 100 | 0 | 0 |
ArcSDE (BCGW) | String | 100 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 100 | ||
E00 (Coverage) | C | 100 | 100 |
Item Definition (Operational Metadata) |
---|
contains a description of the link found at REFERENCE 3 DATA DOWNLOAD LINK (REF_3_URL). |
FGDB (Operational) |
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 avavailable from the following FTP site. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
contains a description of the link found at REFERENCE 3 DATA DOWNLOAD LINK (REF_3_URL). |
RISC Standard Instructions |
N/A |
Item MetaData ID 353 (Report Item 44)
contains a URL to additional project information and/or files (not in the LRDW or EcoCat). Examples include: http://www.for.gov.bc.ca/hfd/library/index.htm, or ftp://fshftp.env.gov.bc.ca/pub/outgoing/Terrain_Data/Terrain_Soils_Maps_Raster/.
It is unknown when this item was added. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | REF_3_URL | Reference 3 Link |
ArcSDE (BCGW) | REFERENCE_3_DATA_DOWNLOAD_LINK | REFERENCE_3_DATA_DOWNLOAD_LINK |
Oracle (BCGW) | REF_3_URL | REFERENCE_3_DATA_DOWNLOAD_LINK |
E00 (Coverage) | REF_3_URL | None |
RISC Standard | REF_3_URL | Reference 3 Link |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 100 | 0 | 0 |
ArcSDE (BCGW) | String | 100 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 100 | ||
E00 (Coverage) | C | 100 | 100 |
Item Definition (Operational Metadata) |
---|
contains a URL to additional project information and/or files (not in the LRDW or EcoCat). |
FGDB (Operational) |
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/ |
Oracle (BCGW) Metadata Description |
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, or ftp://fshftp.env.gov.bc.ca/pub/outgoing/Terrain_Data/Terrain_Soils_Maps_Raster/. |
RISC Standard Description |
contains a URL to additional project information and/or files (not in the LRDW or EcoCat). |
RISC Standard Instructions |
N/A |
Item MetaData ID 354 (Report Item 45)
contains a description of the link found at REFERENCE 4 DATA DOWNLOAD LINK (REF_4_URL). Examples include: Project report is available from the Ministry library, or Raster and/or PDF maps are available from the following FTP site.
It is unknown when this item was added. This item should not be indexed, and is not mandatory. COMMENTS: Width was changed to a standard of 100 based on e-mail/feedback Oct, 2009.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | REF_4_COM | Reference 4 Comments |
ArcSDE (BCGW) | REFERENCE_4_DATA_DESCRIPTION | REFERENCE_4_DATA_DESCRIPTION |
Oracle (BCGW) | REF_4_COM | REFERENCE_4_DATA_DESCRIPTION |
E00 (Coverage) | REF_4_COM | None |
RISC Standard | REF_4_COM | Reference 4 Comments |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 100 | 0 | 0 |
ArcSDE (BCGW) | String | 100 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 100 | ||
E00 (Coverage) | C | 100 | 100 |
Item Definition (Operational Metadata) |
---|
contains a description of the link found at REFERENCE 4 DATA DOWNLOAD LINK (REF_4_URL). |
FGDB (Operational) |
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 avavailable from the following FTP site. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
contains a description of the link found at REFERENCE 4 DATA DOWNLOAD LINK (REF_4_URL). |
RISC Standard Instructions |
N/A |
Item MetaData ID 355 (Report Item 46)
contains a URL to additional project information and/or files (not in the LRDW or EcoCat). Examples include: http://www.for.gov.bc.ca/hfd/library/index.htm, or ftp://fshftp.env.gov.bc.ca/pub/outgoing/Terrain_Data/Terrain_Soils_Maps_Raster/.
It is unknown when this item was added. This item should not be indexed, and is not mandatory.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | REF_4_URL | Reference 4 Link |
ArcSDE (BCGW) | REFERENCE_4_DATA_DOWNLOAD_LINK | REFERENCE_4_DATA_DOWNLOAD_LINK |
Oracle (BCGW) | REF_4_URL | REFERENCE_4_DATA_DOWNLOAD_LINK |
E00 (Coverage) | REF_4_URL | None |
RISC Standard | REF_4_URL | Reference 4 Link |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 100 | 0 | 0 |
ArcSDE (BCGW) | String | 100 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 100 | ||
E00 (Coverage) | C | 100 | 100 |
Item Definition (Operational Metadata) |
---|
contains a URL to additional project information and/or files (not in the LRDW or EcoCat). |
FGDB (Operational) |
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/ |
Oracle (BCGW) Metadata Description |
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, or ftp://fshftp.env.gov.bc.ca/pub/outgoing/Terrain_Data/Terrain_Soils_Maps_Raster/. |
RISC Standard Description |
contains a URL to additional project information and/or files (not in the LRDW or EcoCat). |
RISC Standard Instructions |
N/A |
Item MetaData ID 2 (Report Item 47)
contains a value based on the Canadian Council of Surveys and Mapping's (CCSM) system for classification of geographic features. Examples include: FF84550000.
It is unknown when this item was added. This item should be INDEXED, and is MANDATORY. COMMENTS: Changed RISC long name to "Feature Code" (MN 2010-02-02).
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | FCODE | Feature Code |
ArcSDE (BCGW) | FEATURE_CODE | FEATURE_CODE |
Oracle (BCGW) | FCODE | FEATURE_CODE |
E00 (Coverage) | FCODE | None |
RISC Standard | FCODE | Feature Code |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 10 | 0 | 0 |
ArcSDE (BCGW) | String | 10 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 10 | ||
E00 (Coverage) | C | 10 | 10 |
Item Definition (Operational Metadata) |
---|
contains a value based on the Canadian Council of Surveys and Mapping's (CCSM) system for classification of geographic features. |
FGDB (Operational) |
FEATURE CODE contains a value based on the Canadian Council of Surveys and mapping's (CCSM) system for classification of geographic features. |
Oracle (BCGW) Metadata Description |
FEATURE_CODE (aka FCODE) contains a value based on the Canadian Council of Surveys and mapping's (CCSM) system for classification of geographic features. For example: FF84550000. |
RISC Standard Description |
This field contains a value based on the Canadian Council of Surveys and mapping's (CCSM) system for classification of geographic features. |
RISC Standard Instructions |
N/A |
Item MetaData ID 420 (Report Item 48)
contains a Y/N to indicate there is only a project boundary and no detailed polygon data in the LRDW. Examples include: Y, N.
This item was added on 10/6/2009. This item should not be indexed, and is not mandatory. COMMENTS: We may only want to use this for the 'completed' projects that do not have long table, not the 'initiated' ones - what do others think?? What are the Boolean values and field type in geodatabase.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | BDRY_ONLY | Boundary Only Flag |
ArcSDE (BCGW) | BOUNDARY_ONLY_FLAG | BOUNDARY_ONLY_FLAG |
Oracle (BCGW) | BDRY_ONLY | BOUNDARY_ONLY_FLAG |
E00 (Coverage) | ||
RISC Standard | BDRY_ONLY | Boundary Only Flag |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 1 | 0 | 0 |
ArcSDE (BCGW) | String | 1 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 1 | ||
E00 (Coverage) | C | 0 | 0 |
Item Definition (Operational Metadata) |
---|
contains a Y/N to indicate there is only a project boundary and no detailed polygon data in the LRDW. |
FGDB (Operational) |
Project Boundary Only Flag: contains a Y/N to indicate there is only a project boundary and no detailed polygon data in the LRDW. |
Oracle (BCGW) Metadata Description |
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. |
RISC Standard Description |
N/A |
RISC Standard Instructions |
N/A |
Item MetaData ID 421 (Report Item 49)
contains a summary description of data issues such as coding errors, problems with geometry, identified during a TEIS_ENVIRONEMENT review of the data. Examples include: Several invalid codes were identified. .
This item was added on 10/6/2009. This item should not be indexed, and is not mandatory. COMMENTS: Need to insert an example output from scripts. No script will produce an output for this field. We will be summarizing this from the Short table error summaries by polygon.
Platform | Name | Alias |
---|---|---|
FGDB (Operational) | REVW_COM | Review Comments |
ArcSDE (BCGW) | REVIEW_COMMENTS | REVIEW_COMMENTS |
Oracle (BCGW) | REVW_COM | REVIEW_COMMENTS |
E00 (Coverage) | REVW_COM | None |
RISC Standard | REVW_COM | Review Comments |
Platform | Type | Width | Precision | Scale |
---|---|---|---|---|
FGDB (Operational) | String | 254 | 0 | 0 |
ArcSDE (BCGW) | String | 254 | 0 | 0 |
Oracle (BCGW) | VARCHAR2 | 254 | ||
E00 (Coverage) | C | 254 | 254 |
Item Definition (Operational Metadata) |
---|
contains a summary description of data issues such as coding errors, problems with geometry, identified during a TEIS_ENVIRONEMENT review of the data. |
FGDB (Operational) |
Data Quality Review Comments: contains a summary description of data issues such as coding errors, problems with geometry, identified during a TEIS_ENVIRONEMENT review of the data. |
Oracle (BCGW) Metadata Description |
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. . |
RISC Standard Description |
contains a summary description of data issues such as coding errors, problems with geometry, identified during a TEIS_ENVIRONEMENT review of the data. |
RISC Standard Instructions |
N/A |