Strategic Land and Resource Plans - Current
1463 views (14 recent)Published by the Ministry of Forests, Lands, Natural Resource Operations and Rural Development - Resource Planning and Assessment
Licensed under Open Government Licence - British Columbia
Data and Resources
BC Geographic Warehouse Custom Downloadother
WMS getCapabilities requestwms
For use in viewers such as ESRI tools use this truncated link:...
KML Network Linkkml
For use in viewers such as Google Earth Click here for information on how to...
Data Dictionaries for Strategic Land and Resource Plansother
Data dictionaries to help interpret the data are available in PDF format for...
The layer is to provide direction for Crown land use through the establishment of broad land use goals, planning zone designations, objectives and strategies.
Minor gaps and overlaps between plan boundaries exist and are legitimate. This is due to planning processes that occurred at different times and using different base data. There may be overlapping plan types (e.g. LRMP vs. SRMP). This is a result of different planning mechanisms existing in the same geographic area.
Users should not export features from the Data Distribution Service in ArcINFO Interchange format (.E00). It does not work correctly at this time as region topology is lost. Data integrity is compromised as a result.
|Name||Carole Mahood (pointOfContact)|
|Organization||Ministry of Forests, Lands, Natural Resource Operations and Rural Development|
|Sub-Organization||Regional Operations - Cariboo|
Access & Security
|Who can view this dataset?||Public|
|Who can download this dataset?||Public|
|Record Last Modified||2019-05-04|
Object Name: WHSE_LAND_USE_PLANNING.RMP_STRGC_LAND_RSRCE_PLAN_SVW
Short Name: RMPSLR_SVW
Comments: WHSE_LAND_USE_PLANNING.RMP_STRGC_LAND_RSRCE_PLAN_SVW is a selection of the layer RMP_STRGC_LAND_RSRCE_PLAN_SP, where the RETIREMENT DATE is null. Strategic land and resource plans (SLRPs) provide direction for Crown land use through the establishment of broad land use goals, planning zone designations, objectives and strategies. Plan types include SRMPs, LRMPs, and RLUPs.
|Column Name||Short Name||Data Type||Data Precision||Comments|
|STRGC_LAND_RSRCE_PLAN_ID||SLRP_ID||NUMBER||5||STRGC LAND RSRCE PLAN ID. A unique, static user maintained identifier used for quality control and quality assurance reporting purposes.|
|STRGC_LAND_RSRCE_PLAN_PROVID||SLRPPRVID||NUMBER||5||STRGC LAND RSRCE PLAN PROVID The provincial identifier. Unique for any polygon (or collection of polygons for SLRPs managed with distinct attribute values) that does not have a retired date. Not unique for polygon features with multiple retirements. This identifier stays with the polygon feature over time as the feature changes.|
|STRGC_LAND_RSRCE_PLAN_NAME||SLRP_NAME||VARCHAR2||100||STRGC LAND RSRCE PLAN NAME. The official name assigned to the plan|
|STRGC_LAND_RSRCE_ABRVN||SLRP_ABRVN||VARCHAR2||12||STRGC LAND RSRCE ABRVN. Official abbreviation on plan name ( e.g. CCLRMP, VILUP)|
|PLAN_TYPE||PLAN_TYPE||VARCHAR2||30||PLAN TYPE. Name or acronym of plan type e.g. coastal, LRMP, RLUP, or SRMP (Note: All plans are considered SLRPs, but some plans have specific naming convention sub-types based on their content, planning scope and historical timing of plan development. It is this sub-type (or overarching SLRP type if there is no sub-type) that is captured in this attribute).|
|PLAN_STATUS||PLANSTATUS||VARCHAR2||20||PLAN STATUS. Contains an indicator of plan status. E.g. draft, approved or legal.|
|APPROVAL_DATE||APP_DT||DATE||7||APPROVAL DATE. A non-mandatory date field to indicate the date the SLRP polygon was formally approved by government decision-makers (e.g. Cabinet, Minister of Ag & lands etc.) as official government policy (Note: this approval process does not mean the planning direction has been formally legalized).|
|APPROVAL_LAST_AMEND_DATE||APP_AMD_DT||DATE||7||APPROVAL LAST AMEND DATE. A non-mandatory date field to indicate the date the SLRP polygon was last formally amended by government decision-makers (i.e. formal amendment has occurred but SLRP direction still remains in policy, not legalized).|
|LEGALIZATION_DATE||LEGAL_DT||DATE||7||LEGALIZATION DATE. A non-mandatory date field to indicate the date the SLRP polygon was formally enacted in law e.g. Higher Level Plan boundary.|
|LEGALIZATION_LAST_AMEND_DATE||LGL_AMD_DT||DATE||7||LEGALIZATION LAST AMEND DATE A non-mandatory date field to indicate the date the SLRP polygon was last legally amended.|
|GIS_CHANGE_DATE||GIS_CH_DT||DATE||7||GIS CHANGE DATE: A mandatory date field to indicate the date the SLRP polygon was updated by the GIS Change Person.|
|GIS_CHANGE_PERSON||GIS_CH_PER||VARCHAR2||20||GIS CHANGE PERSON: A mandatory text field to indicate the technical GIS person who physically made a change to the SLRP polygon. This GIS task is typically resulting from direction received from the business area "Initiator of Change".|
|CHANGE_REASON||CHG_REASON||VARCHAR2||100||CHANGE REASON. A text field to indicate the business reason for initiating a change in a SLRP polygon.|
|INITIATOR_OF_CHANGE||INITIATOR||VARCHAR2||20||INITIATOR OF CHANGE. Person in the business area who has requested change(s) to be made.|
|ENABLING_DOCUMENT_TITLE||ENBLNG_DCE||VARCHAR2||275||ENABLING DOCUMENT TITLE is the title of the legal order that enabled the strategic land or resource use plan or specific objective to come into legal force, or other document which confirms the plan or objective as policy of government. The document describes the objective and often contains additional management direction for accomplishing the objective which may affect use of natural resources. Example: “Ministerial Order: Land use Objectives for the Cariboo-Chilcotin Land Use Area”|
|ENABLING_DOCUMENT_URL||ENBLNG_DCL||VARCHAR2||254||ENABLING DOCUMENT URL is the link for the document which enabled the legal or policy land or resource objective to come into force. Documents are stored in a variety of file formats and may be large files as many contain maps.|
|FEATURE_CODE||F_CODE||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_AREA_SQM is the system calculated area of a two-dimensional polygon in square meters|
|FEATURE_LENGTH_M||FEAT_LEN||NUMBER||19||FEATURE_LENGTH_M is the system calculated length or perimeter of a geometry in meters|
|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 column required by spatial layers that interact with ESRI ArcSDE. It is populated with unique values automatically by SDE.|
|SE_ANNO_CAD_DATA||ANNO_CAD||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.|