ALR Applications - Internal

234 views (6 recent)

Published by the BC Agency - Agricultural Land Commission
Licensed under Access Only

The spatial view APPLICATIONS is a multi part polygon that represents all the spatial extents for applications within the ALR regardless of status or application type. Access to this dataset is restricted to BC Provincial Government employees.

Data and Resources

Dataset Extent

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

Additional Information

Purpose

For use by Government staff only. Used to research application history on a piece of land.

Data Quality
Lineage Statement

More Information

Contact Information

NameGabriel Hazaparu (custodian)
EmailGabriel.Hazaparu@gov.bc.ca
OrganizationBC Agency
Sub-OrganizationAgricultural Land Commission
NameCraig Phillips (pointOfContact)
EmailCraig.Phillips@gov.bc.ca
OrganizationBC Agency
Sub-OrganizationAgricultural Land Commission

Access & Security

Who can view this dataset? Named users
Who can download this dataset?Named users

Metadata Information

Record Published 2015-01-27
Record Last Modified 2017-05-29
Resource Status onGoing

Object Description

Object Name: WHSE_LEGAL_ADMIN_BOUNDARIES.OATS_ALR_APPLICATIONS_INT_SVW

Comments: The two spatial views of ALR APPLICATIONS include a multi part polygon representing all the spatial extent of application within the ALR regardless of status or application type; this view is NOT restricted to only display those applications whose extents have been reviewed by the Agricultural Land Commission.

Column Name Short Name Data Type Data Precision Comments
ALR_APPLICATION_ID NUMBER 18 ALR_APPLICATION_ID is a system generated sequence number to uniquely identify an ALR APPLICATION. This is also used as the ALR APPLICATION'S external reference number.
RECEIVED_DATE DATE 7 RECEIVED_DATE is the date the application was received by the ALC office.
PANEL_REGION VARCHAR2 300 PANEL_REGION is the name of the ALC panel region where the application is located, e.g., Island.
REGIONAL_DISTRICT VARCHAR2 354 REGIONAL_DISTRICT is the name of the regional district where the application is located, e.g., Capital Regional District.
LOCAL_GOVERNMENT VARCHAR2 300 LOCAL_GOVERNMENT is the name of the local government where the application is located, e.g., Capital.
APPLICANT_NAME VARCHAR2 300 APPLICANT_NAME is the name of the first applicant on the application.
APPLICATION_STATUS VARCHAR2 54 APPLICATION_STATUS is the name of the public status of the application, e.g. Approved.
APPLICATION_CLASS_CODE VARCHAR2 300 APPLICATION_CLASS_CODE is the name of the classification category under which the application can be applied, e.g. Land Owner Application. This will establish the default fee amount collected for the application.
PROPOSAL_COMPONENT_TYPE VARCHAR2 496 PROPOSAL_COMPONENT_TYPE is the comma-separated names of the proposal component types that are present for the application, e.g. Exclusion, Subdivision.
OATS_URL VARCHAR2 119 OATS_URL is a link back to the operational OATS web application by application ID, e.g. https://a100.gov.bc.ca/int/oats/ApplicationSearch/SearchApplicationsView.do?id=43965.
GEOMETRY_VERIFICATION_IND VARCHAR2 1 GEOMETRY_VERIFICATION_IND indicates whether the Agricultural Land Commision have reviewed the geometry provided within the application and consider it to be representative of the application. Value consist of 'N' and 'Y'; when a determination as the review status of the application's shape cannot be made users should assume the shape has not been reviewed ('N').
FEATURE_CODE VARCHAR2 10 FEATURE_CODE is most importantly a means of linking a feature to its name and definition. For example, the code GB15300120 on a digital geographic feature links it to the name " Lake - Dry" with the definition "A lake bed from which all water has drained or evaporated." The feature code does NOT mark when it was digitized, what dataset it belongs to, how accurate it is, what it should look like when plotted, or who is responsible for updating it. It only says what it represents in the real world. It also doesn't even matter how the lake is represented. If it is a very small lake, it may be stored as a point feature. If it is large enough to have a shape at the scale of data capture, it may be stored as an outline, or a closed polygon. The same feature code still links it to the same definition.
GEOMETRY SDO_GEOMETRY 64 GEOMETRY is the column used to reference the spatial coordinates defining the feature.
OBJECTID NUMBER 38 OBJECTID is a required attribute of feature classes and object classes in a geodatabase.
SE_ANNO_CAD_DATA BLOB 4000 SE_ANNO_CAD_DATA is a binary column used by spatial tools to store annotation, curve features and CAD data when using the SDO_GEOMETRY storage data type.
FEATURE_AREA_SQM NUMBER 19 FEATURE_AREA_SQM is the system calculated area of a two-dimensional polygon in square meters.
FEATURE_LENGTH_M NUMBER 19 FEATURE_LENGTH_M is the system calculated length or perimeter of a geometry in meters.

Comments

No comments have been posted yet.