Georgia Basin Ecosystem Initiative Boundary - Linework
166 views (3 recent)Published by the Ministry of Forests, Lands, Natural Resource Operations and Rural Development - GeoBC
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...
To improve conservation planning in the Georgia Basin by providing science-based information about biodiversity to a broad range of audiences.
SDE layers created from arc/info coverages. Arc/Info coverage are the format updates occur in.
|Name||GeoBC Inquiries (pointOfContact)|
|Organization||Ministry of Forests, Lands, Natural Resource Operations and Rural Development|
Access & Security
|Who can view this dataset?||Public|
|Who can download this dataset?||Public|
|Record Last Modified||2019-12-17|
Object Name: WHSE_ADMIN_BOUNDARIES.ENVCAN_GEORGIA_BASIN_BND_LINE
Short Name: GB_BDY_LIN
Comments: Georgia Basin Boundary Lines (GEORGIA BASIN BND LINE) are the Geographical line features that define the edge of the Georgia Basin polygon. This is not a multipart feature class.
|Column Name||Short Name||Data Type||Data Precision||Comments|
|GEORGIA_BASIN_BND_ID||GB_BND_ID||NUMBER||10||GEORGIA BASIN BND ID is the unique numeric identifier for a spatial feature.|
|FEATURE_CODE||FEAT_CODE||VARCHAR2||10||FEATURE CODE is a standard alphanumeric code to identify the type of feature represented by the spatial data. A 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.|
|SOURCE_GEOMETRY_ACQUIRED_FROM||SRCGEO_FRM||VARCHAR2||16||SOURCE GEOMETRY ACQUIRED FROM Indicates source for line segment. e.g. �Watershed_Atlas�, �Regional_Dist�, �Ecosections�, �BC_250000�.|
|GEOMETRY||GEOMETRY||SDO_GEOMETRY||1||GEOMETRY is the column used to reference the spatial coordinates defining the feature.|
|OBJECTID||OBJECTID||NUMBER||38||OBJECTID is a required attribute of feature classes and object classes in a geodatabase.|
|SE_ANNO_CAD_DATA||BLOB||4000||SE_ANNO_CAD_DATA is a binary column used by spatial tools to store annotation, curve features and CAD data when using the SDO_GEOMETRY storage data type.|
|FEATURE_LENGTH_M||FEAT_LEN||NUMBER||19||FEATURE_LENGTH_M is the system calculated length or perimeter of a geometry in meters|