1. INTRODUCTION PURPOSE APPLICABILITY... 3

Transcription

1 STANDARD OPERATING PROCEDURE CADASTRAL BASE MAPPING SECTION BASE MAPPING AND GEOMATICS SERVICES BRANCH, MINISTRY OF SUSTAINABLE RESOURCES MANAGEMENT TABLE OF CONTENTS 1. INTRODUCTION PURPOSE APPLICABILITY ICF COMPILATION GENERAL METHODOLOGY SUMMARY Survey Plans and Cadastral Fabric Introduction of Control Data Old and New Cadastral Fabric Integration Attributing the ICF Other DATA CAPTURE METHODOLOGY COGO Compilation Fine Adjust Bulk Parcel Adjust Attribution QUALITY ASSURANCE FIELD NAMES AND ATTRIBUTES TYPOGRAPHICAL CONVENTIONS TERMINOLOGY ATTRIBUTES REQUESTS SUBMITTED TO REFORMAT TABLE TO HAVE EACH FIELD NAME ON ONE PAGE WITH DEFINITION AND EXAMPLES TYPES OF ICF PARCEL FORESHORE LOTS ROADS (HIGHWAYS, LANES, ROAD ALLOWANCES, WALKWAYS, WIDENINGS) Road Designations with Associated PID Land Exchange for Road Purposes EASEMENTS AND RIGHTS-OF-WAY PARKS RETURNED TO CROWN REMAINDER PARCELS BARE LAND STRATA PROPERTIES NON BARE LAND STRATA PROPERTIES Strata Plan Prefixes COMMON PROPERTY Created: April 10, 2006 Page 1of 65

2 STANDARD OPERATING PROCEDURE CADASTRAL BASE MAPPING SECTION BASE MAPPING AND GEOMATICS SERVICES BRANCH, MINISTRY OF SUSTAINABLE RESOURCES MANAGEMENT 6.10 MINERAL CLAIM SURVEYS, COAL LICENCE, PHOSPHATE LICENCE AND SPECIAL TIMBER LICENCE UNVERIFIED PARCELS SPLIT BY JURISDICTION UNSURVEYED CROWN LAND INDIAN RESERVES FEDERAL LAND APPENDIX A APPENDIX B APPENDIX C APPENDIX D APPENDIX E APPENDIX F APPENDIX G APPENDIX H APPENDIX I APPENDIX J APPENDIX K APPENDIX L GLOSSARY Created: April 10, 2006 Page 2of 65

3 STANDARD OPERATING PROCEDURE CADASTRAL BASE MAPPING SECTION BASE MAPPING AND GEOMATICS SERVICES BRANCH, MINISTRY OF SUSTAINABLE RESOURCES MANAGEMENT 1. Introduction This Specifications and Standards document pertains to the production of the Integrated Cadastral Fabric (ICF). The ICF is a geo-referenced, spatial database representing the registered legal structure of land parcels in the Province of BC. The unit responsible for its production is the Cadastral Base Mapping Section (CBMS) within the Base Mapping and Geomatics Services (BMGS) Branch of the Ministry of Agriculture and Lands (MAL). This document is currently under revision. The next version will include updated specifications and standards that have been developed since February It will also be modified to reflect practices that have been developed during production of the ICF by contracted private sector organizations under the contract management of the CBMS staff. Most of the text in this original document will remain largely unchanged from the February 2003 issue with the exception of a few text revisions to reflect the nature of the document as a specification (e.g. in certain cases the word shall is used) and the addition of new sections. A Standard Operating Procedure (SOP) is also in development, which will describe ICF and explain the procedures, specifications, standards and quality assurance principles that apply to all participants in the production of ICF. 2. Purpose The purpose of this document is to provide guidance on specifications and standards that are to be followed by organizations involved in: The supply of both spatial and attribute data, The processing of that source data, and The production of the final ICF product. 3. Applicability This document has been prepared for use by the following organizations: Organizations that provide spatial and attribute data, which will be used either directly, or which will be processed prior to being used in the ICF (e.g. B.C. Ministries, Regional Districts, Local Government, Utility companies and the Integrated Cadastral Information Society - ICIS). The CBMS whose responsibility is for the production and maintenance of the ICF product. Organizations, primarily private sector, that receive data from the CBMS and further process the data under contract to the CBMS. The Information Management Branch (IMB) who receives the ICF product from the CBMS and is responsible for loading it into the Land and Resource Data Warehouse. Information on IMB can be found at this link: End users. Although this document has not been designed for end users, they may find it of use when working with ICF data. Created: April 10, 2006 Page 3of 65

4 STANDARD OPERATING PROCEDURE CADASTRAL BASE MAPPING SECTION BASE MAPPING AND GEOMATICS SERVICES BRANCH, MINISTRY OF SUSTAINABLE RESOURCES MANAGEMENT 4. ICF Compilation Compilation of spatial and attribute data for the ICF shall conform to this specification. The following sections describe the methodology for polygon capture and attribution with the objective of reducing the time required to research parcel status in order to obtain the key link between the spatial and attribute data sets. 4.1 General The ICF is compiled from data from a number of sources (see Appendix L). Fabric adjustment in the compilation process is dependent on the information provided by the original data source owner, i.e the Local Government (Municipal or Regional District), as to its accuracy and completeness. The positional accuracy of the source data varies widely from sub 1 meter to in excess of 10 meters. Where additional data that can enhance the positional accuracy is available, it is used in the compilation of the ICF and attributes are provided to explain the accuracy. Caution should be exercised in using the ICF for only those purposes for which it is intended i.e. as a database to link cadastral spatial data with its attribute data for both public and private land. As the ICF is a reference product, the legal aspects of a land parcel and its locations are as described in the appropriate Crown Land Registry, the Land Title Registry and in the Official Survey Plan documents and the evidence on the ground. 4.2 Methodology Summary The following is a summary of the key points that form the framework for the methodology that is required when undertaking a cadastral fabric compilation project Survey Plans and Cadastral Fabric Wherever possible, the original intent of the survey plans shall be followed Wherever possible, spatial discrepancies between the survey plan and the cadastral fabric should be distributed throughout the parcels in question while maintaining the road allowance widths as per the prescribed distances on the survey plans. Distribution of discrepancies shall distort the survey plan in the least manner possible All the compiled cadastral fabric is expected to have inherent relative and positional spatial errors, including cadastral fabric assembled using Coordinate Geometry (COGO). The compiler shall quantify the positional errors and rate the cadastral fabric as per CBMS-CBM-PE-005 Guidelines for Spatial Adjustments The quality of legal survey plans in BC varies and there are a number of poor surveys that are represented in legal survey plans that are in error. The accuracy of a survey plan is largely dependent upon the accuracies required by the regulations governing cadastral surveys at the time of the survey. Consideration must be given to the general topography, the method of the survey and the type of instrumentation available at the time of the survey. If internal closure is more than 1:5000, identify these potential problems to the CBMS for compilation resolution. If the survey itself is inaccurate and is in conflict with newer plans, refer back to the CBMS. Created: April 10, 2006 Page 4of 65

5 STANDARD OPERATING PROCEDURE CADASTRAL BASE MAPPING SECTION BASE MAPPING AND GEOMATICS SERVICES BRANCH, MINISTRY OF SUSTAINABLE RESOURCES MANAGEMENT Introduction of Control Data A review of the provided control information will identify areas requiring parcel adjustment (move and adjust) and a trial and error approach will be used to find the best fit to the available control The hierarchal order (most accurate to least accurate) for spatial control shall be: a. Cadastral ties into the Integrated Survey Area (ISA) with sub metre accuracy, b. Cadastral ties created through Global Positional System (GPS) 90%+ confidence level, c. Cadastral fabric of higher positional quality adjacent to or surrounding the area being compiled, d. Line work from other mapping products such as Digital Road Atlas (DRA) and Terrain Resource Information Mapping (TRIM) COGO shall be used to bring in any new [or missing] parcels from legal survey plans or titled documents into the compiled cadastral fabric. Discrete Digitizing shall be used only where natural features (refer to Glossary) define the boundary. When offsets to the natural boundary are not included in the survey plan, the natural feature boundary as in the survey plan shall be digitized. Refer to CBMS-CBM-ST-002 Compilation Case Studies and Acceptance Criteria. Note: Parcel natural boundaries are captured at the time of the survey. show riparian variations. The ICF does not The cadastral fabric is generally compiled based on metes and bounds of legal survey plans and titled documents. In the survey plan, the defined natural boundary of parcels may differ from that of TRIM, orthophotos and Tantalis. Line work for parcels, whose metes and bounds description are not supported with a survey plan or sketch and depicts the boundary as the natural features, can be traced from TRIM Compilation of parcels will use the best available control and evidence. Typically this compilation process starts with the newest to oldest survey chronology as well as using the surveys with the highest positional accuracy Old and New Cadastral Fabric Integration Prior to commencement of integrating old and new parcels, the provided cadastral fabric spatial file (refer to CBMS-CBM-SP-004 Specifications for Spatial Data from Local Government) shall be polygonalized and shall include only those polygons that make up the parcels. Slivers, gaps, and gores shall be evaluated for deletion or retention through research for associated attribution. Multi-part polygons are to be separated (refer to 4.27 CBMS-CBM-ST-002 Compilation Case Studies and Acceptance Criteria) The integrated (i.e. the old, new and adjusted) parcel fabric shall be reviewed to ensure that it is contiguous, with no slivers, gaps, gores, or overlapping polygons, subject to the evaluation of slivers, gaps and gores in para (see Glossary for definitions). Submission of the parcel fabric to the CBMS shall include documentation summarizing the findings and cleanup of the data. Created: April 10, 2006 Page 5of 65

6 STANDARD OPERATING PROCEDURE CADASTRAL BASE MAPPING SECTION BASE MAPPING AND GEOMATICS SERVICES BRANCH, MINISTRY OF SUSTAINABLE RESOURCES MANAGEMENT Concepts of integration include: a. When comparing the cadastral fabric spatial file with other provided parcel spatial datasets, e.g. Tantalis SDE, parcels identified by the compiler as missing from the Cadastral Fabric data file shall be copied and pasted into the cadastral fabric spatial file and reconciled for accuracy with the existing data and control information (refer to 4.26 CBMS-CBM-ST-002 Compilation Case Studies and Acceptance Criteria and CBMS- CBM-SP-003 Specification for Spatial Data Extracted From Tantalis). Note: If the Primary parcel e.g. district lot, has been subdivided, the shape shall be defined as the original parcel less the subdivided parcels. Tantalis parent PINs are created for Primary parcels, e.g. district lot that has not been subdivided or alienated. Once they are subdivided or have exceptions removed, the subsequent subdivisions must be created as a remainder parcel(s) of the original Primary parcel. The only occurrence, in which a remainder parcel is attributed, is when an actual PIN or PID and the associated legal description accurately reflect the geometry of the parcel. The originating PIN will not be attributed to this remainder parcel. When no legal information is found for this remainder parcel the DESCRIPT field shall be attributed with the REM PARCEL NAME and the CROWNADMIN field with CROWN PROVINCIAL. Do not assume that a parcel is a remainder if there is no legal information available. If it is unclear follow the rules for Unverified polygons in Section 6.11 (also refer to 4.12 and 4.13 CBMS-CBM-ST-002 Compilation Case Studies and Acceptance Criteria). b. Where railway properties are owned in fee simple, appropriate parcel polygons shall be created. Where a railway traverses a property as an easement, no parcel polygon shall be created. c. Where highways and roads are owned in fee simple, appropriate parcel polygons shall be created. Otherwise, highways and roads shall not create a cadastral parcel except for the noted exceptions from Section 6.2 Roads and 6.9 Common Property in regards to exception-enclosed road. d. Boundaries for Rights of Way and easements, where these corridors do not convey registered title in fee simple other than to the Province, (refer to Section 6.3 Easements and Right-of-Ways and Glossary) on parcels of land, are not to be excluded from the ICF parcel and are not to form their own parcel in the ICF (Case Study pending) unless the legal description for the parcels indicates it as being excluded. e. Subdivision Lots shall not be split by a Primary parcel boundary if they straddle more than one Primary parcel. An exception to this is as follows: i. Where the Subdivision Lot is identified with separate PIDs and each PID is described as that part lying within each Primary parcel. Each PID shall have one parcel.(refer to 4.20 CBMS-CBM-ST-002 Compilation Case Studies and Acceptance Criteria). f. Where a parcel straddles different jurisdiction s, (e.g. Regional District s, Electoral Areas and Municipalities), and therefore where one PID may have different JUROLS, the parcel will not be split along the jurisdictional boundary (refer to 4.1 CBMS-CBM-ST-002 Compilation Case Studies and Acceptance Criteria). The rules in which to capture a parcel that straddles different datasets are currently: Created: April 10, 2006 Page 6of 65

7 STANDARD OPERATING PROCEDURE CADASTRAL BASE MAPPING SECTION BASE MAPPING AND GEOMATICS SERVICES BRANCH, MINISTRY OF SUSTAINABLE RESOURCES MANAGEMENT Note: i. Municipal data to Rural: capture in Municipal ii. Municipal to Municipal: capture in higher quality data set iii. If datasets are both of high quality: capture in 1st dataset compiled iv. Rural to Rural: capture in higher quality dataset or capture in 1st dataset compiled. Use the JUROL related to the jurisdiction in which the parcel is to be captured in Adjust the line work to enhance the positional accuracy (refer to Glossary for definition) of the fabric by the use of new or higher quality survey control data (Refer to CBMS-CBM-PE-005 Guidelines for Spatial Adjustments) Tolerances should be set to ensure that the ICF cadastral fabric spatial data maintains its relative accuracy (refer to Glossary for definition) when the files undergo: a. Transformation using survey control points to reposition the fabric, portions of the fabric or parcels, b. Change of map projection e.g. UTM to Albers to UTM, c. Change of datum e.g. NAD 27 to NAD 83, d. Conversion from one data format to another and that true curves which define a parcel boundary retain their shape Using the available evidence and compilation criteria (refer to Section 3 CBMS-CBM-ST-002 Compilation Case Studies and Acceptance Criteria), develop a method to adjust the data to best fit the evidence. Depending on the available control and the initial results of test adjustments, the fabric may need to be separated into smaller blocks and each block adjusted individually to improve the spatial accuracies with minimal compromise to the original intent of the cadastral fabric. Using a trial and error approach find the best fit and adjust accordingly, and then document the adjustment and error factors. Spatial adjustments are defined as moving, rotating, and possibly scaling by means specified in CBMS-CBM-PE-005 Guidelines for Spatial Adjustments When integrating adjusted cadastral fabric into an existing completed cadastral fabric, the edge match shall be verified according to the edge matching criteria (refer to Section 3 CBMS-CBM- ST-002 Compilation Case Studies and Acceptance Criteria) The CBMS shall be advised prior to proceeding with major changes to the cadastral fabric spatial file including movements, adjustments, rotations or scaling which have not been previously identified by the CBMS and which the compiler recommends. The CBMS will review the recommended changes and will notify the contractor within four working days if the changes are approved or rejected and make appropriate contract revisions. Acceptance criteria will still have to be met (refer to Section 3 CBMS-CBM-ST-002 Compilation Case Studies and Acceptance Criteria) Proceed with the fabric adjustments, analyze the included line work and remove any duplication of lines. Created: April 10, 2006 Page 7of 65

8 STANDARD OPERATING PROCEDURE CADASTRAL BASE MAPPING SECTION BASE MAPPING AND GEOMATICS SERVICES BRANCH, MINISTRY OF SUSTAINABLE RESOURCES MANAGEMENT Any new parcels compiled by COGO from surveyed plans shall be positioned using the control data. Parcels copied from other spatial datasets shall recognize the positional hierarchy rules (refer to para and Section 3 CBMS-CBM-ST-002 Compilation Case Studies and Acceptance Criteria). New parcels incorporated into existing fabric may be used to update the adjoining parcels. It may be possible to simply fit the new parcel into the existing cadastral fabric; however, it is more likely to require at least a partial recompilation or adjustment of the surrounding parcels. This will depend largely upon the strength of the cadastral fabric and the control network in the vicinity of the new information and throughout the fabric Any parcels that are found in need of further subdivision, for which the information has not been provided in the attribute files (parcel file (pcl.dbf) or not found file (nf.dbf)) (refer to Section 4.2.4), nor the Tantalis spatial and attribute file shall be brought to the attention of the CBMS for affirmation to COGO and positioning into the cadastral fabric spatial file and shall be noted in the parcel CMPLR_COMM field In most cases the accuracy code for a parcel is not expected to change, however, new data may be obtained which is of higher accuracy (e.g. within an Integrated Survey Area). In these situations, adjacent parcel polygons must be reviewed to identify whether or not they are eligible for upgrading. Once assigned, accuracy codes are never downgraded but they may be upgraded if accompanied by verifiable supporting data The parcel geometry must accurately reflect the legal descriptions. If the legal description has excluded plans, then the parcel shape shall have those plans either removed from the parcel or shown within the parcel (refer to example in 4.11 CBMS-CBM-ST-002 Compilation Case Studies and Acceptance Criteria) Attributing the ICF The attribute files used to assist in the compilation of the ICF are referred to as the parcel file (pcl.dbf) and not found file (nf.dbf). The file names are preceded with the project area name it pertains to (e.g. victoria_pcl.dbf, victoria_nf.dbf). The pcl.dbf contains attribute information for a project specific area. It is a combination of the records ordered from the Land Title database and BC Assessment database and received as textual files. The LTO data comes in the form of a flat ASCII text file within which processes are run to split out the multiple files used to help create the parcel file. This data is ordered based on the Taxation Authority that LTO assigns the parcel. The BCA data is received as a DBF file. The BCA data is based on the School District in which the project area lies and is ordered using the corresponding BCA Area and Jurisdiction. Part of the creation of the pcl.dbf involves the loading and joining of BCA and LTO data sets and is as complete as the information entered into the LTO and BCA databases. Note: The data dumps from the LTO and BCA are current to the day the data are processed and based on LTO and BCA s update cycle. The initial pcl.dbf created can invariably contain more information than is required for the project area and there are many instances where it contains less. This is due to LTO Taxation boundaries, BCA Jurisdiction boundaries, Municipal and Regional District boundaries not being coincident causing either an overlap of information, excluded information and information extending beyond the project area boundaries. Project areas are based on Regional Districts and/or Municipalities. Manual interpretation and research are involved to try to resolve inconsistencies between the data sets that prevent a successful join. Extensive preparatory work is required to include only those records pertaining to the project area (refer to CBMS- Created: April 10, 2006 Page 8of 65

9 STANDARD OPERATING PROCEDURE CADASTRAL BASE MAPPING SECTION BASE MAPPING AND GEOMATICS SERVICES BRANCH, MINISTRY OF SUSTAINABLE RESOURCES MANAGEMENT CBM-PO-002 BCA and LTO Data Requests and CBMS-CBM-PO-005 Draft Completing the Parcel File). The nf.dbf contains attribute information that is deemed missing from the Local Government s spatial file (refer to CBMS-CBM-SP-004 Specification for Spatial Data from Local Government). This file is created when the finalized pcl.dbf and the Local Government s (LG) spatial attribute data are joined through unique IDs (e.g. PID) for a match. The resulting unmatched records from the pcl.dbf are extracted to create the nf.dbf. The method of the join involves matching existing LG attributes with that of the pcl.dbf through a combination of Folio, PID, and legal information joins. Although every polygon is intended to represent the legal lay of the land based on their legal descriptions supported by legal documents found within the LTO, BCA and Tantalis, no further research is undertaken to verify attribute to parcel correctness if there is a successful match between the LG data and the Parcel file. Therefore it may contain errors that are not detectable. Note: The Parcel file can also be the not found file if the project area is to be cogo d from scratch. The Cadastral Base Mapping Section (CBMS) or ICF Compilers will create the following interim fields for the spatial and attribute files that are to identify compilation methods and comments relating to the compilation. The purpose of these fields is to provide information for data capture only, and will not be stored with the final ICF. The interim fields are as follows: Field Name CBMS_CODE CBMS_COMM CMPLR_CODE CMPLR_COMM Description The CBMS will enter the coding for the probable method of capture of the parcel for the ICF compiler to follow. The CBMS may enter information relating to the parcel. The compiler will enter the coding of the actual method of capture of the parcel. The compiler will enter any information relating to compilation or anomalies of the parcel. Attribution of the following parcel fields, where information exists, is the sole responsibility of CBMS: CBMS_CODE, CBMS_COMM, DATAOWNER, LABSYM, XTRAC_DATE. Attribution of the following parcel fields, where information exists through compilation efforts or from other attribute and spatial data sets, is the responsibility of the ICF compiler (CBMS or Contractor): ACCURACY, ADDRMUNIC, ADDRSOURCE, ADDNOTES, ADDRTYPE, AREA, BLK, COMMENTS, CMPLR_CODE, CMPLR_COMM, CROWNADMIN, DESCRIPT, DIRECTION, FREEFORM, JUROL, LAND_DIST, LOT, METHOD, PCL, PCLLINKSID, PERIMETER, PID, PN, PLACENAME, PLANDEFDOC, PRIMARY, STREETNUM, STREETNAME, STREETYPE, STRNUMSUF, AND UNITNUMBER. AREA and PERIMETER is typically system generated, but there are occasions when operator intervention is needed to update the fields. Created: April 10, 2006 Page 9of 65

10 STANDARD OPERATING PROCEDURE CADASTRAL BASE MAPPING SECTION BASE MAPPING AND GEOMATICS SERVICES BRANCH, MINISTRY OF SUSTAINABLE RESOURCES MANAGEMENT Parcel polygons shall have their fields populated with their corresponding unique parcel identifier (PID, PIN or JUROL), and the related attribute information from the provided attribute files (pcl.dbf or nf.dbf) and other partial spatial files (e.g. Tantalis SDE which contain attribute information). However, not all parcel polygons have corresponding PID, PIN, or JUROL (e.g. road in a strata subdivision). In these situations a meaningful descriptive comment will be included in the appropriate field(s) as per Section 6.1 to If that is not appropriate, a comment will be added in the CMPLR_COMM field (refer to Section 3 CBMS-CBM-ST-002 Compilation Case Studies and Acceptance Criteria) Where it is found that the parcels listed in the not found file (nf.dbf) already exist in the cadastral fabric spatial file, but without attributes, then the parcel shall be populated with the related attribute information from the not found file (nf.dbf) as per para , , and All parcel polygons shall have the mandatory fields, DESCRIPT, LAND_DIST, *DATAOWNER, METHOD AND ACCURACY, populated in the cadastral fabric spatial file. *DATAOWNER, although a mandatory field, is the responsibility of the CBMS The cadastral fabric spatial file fields (PCL, LOT, BLK, PLANDEFDOC, FREEFORM, CROWNADMIN, DESCRIPT, PRIMARY, LAND_DIST, ADDSOURCE, ADDNOTES, ADDRTYPE, UNITNUMBER, STREETNUM, STRNUMSUF, DIRECTION, STREETNAME, STREETYPE, ADDRMUNIC, PLACENAME, and PCLLINKSID) shall be populated with corresponding attributes, if they occur in the parcel attribute file (pcl.dbf), not found file (nf.dbf) or Tantalis spatial and attribute files In both the attribute file and cadastral fabric spatial file, the CMPLR_COMM field shall be used by the compiler to record any documented changes and to identify cadastral fabric spatial file uncertainties regarding parcel associations. All parcels in the not found file (nf.dbf) shall be accounted for in the cadastral fabric spatial file. Comments will be provided in the not found file (nf.dbf) for those parcels not included in the cadastral fabric spatial file Any remaining parcels shall not be removed from the delivered cadastral spatial fabric file. Such parcels shall have comments included in the CMPLR_COMM field describing any uncertainties In the cadastral spatial fabric file, the CMPLR_CODE field (formatted 5 character string), shall be used by the compiler to record their method of data capture, by code, as shown in Section 4.3 Data Capture Methodology Table 1 (also refer to Sections to code description) Other Ensure that precision is set to double precision when utilizing Arc/Info software. This requirement applies when data is either imported into or compiled in Arc/Info Where required, convert existing digital data from different co-ordinate systems to UTM NAD83 (NTV2), ensuring all data sets are referenced to a single UTM zone that is predominant to the project area when compling Create a polygonalized clean topologically structured cadastral fabric (refer to para ). Created: April 10, 2006 Page 10of 65

11 STANDARD OPERATING PROCEDURE CADASTRAL BASE MAPPING SECTION BASE MAPPING AND GEOMATICS SERVICES BRANCH, MINISTRY OF SUSTAINABLE RESOURCES MANAGEMENT Verify that 100% of the supplied parcel file records from the parcel file (pcl.dbf) and not found file (nf.dbf) including both old and new parcels, ex. Tantalis spatial, are captured in the completed cadastral fabric spatial file and meets the requirements of this Specification (refer to para ). Created: April 10, 2006 Page 11of 65

12 STANDARD OPERATING PROCEDURE CADASTRAL BASE MAPPING SECTION BASE MAPPING AND GEOMATICS SERVICES BRANCH, MINISTRY OF SUSTAINABLE RESOURCES MANAGEMENT 4.3 Data Capture Methodology Table 1 lists the Data Compilation Methodology and Compilation Code in five categories. Compilers shall complete the CMPLR_CODE field of the cadastral fabric according to the capture method of the parcels during the compilation process. The data in this table are used in contract documents for pricing (see also Appendix D Compilation Codes). Table 1 Data Compilation Methodology Compilation Code COGO 1 Compilation 2 Fine Adjust 3 Bulk Parcel Adjust 4 Attribution 5 Table 2 lists the Method codes in which the ICF parcels have been captured on the completion of compilation. The METHOD field in the initial ICF is populated with the method used to create the initial spatial file from the LG. This field may require upgrading to reflect most recent method used (see also Appendix H Method). Table 2 Method Code COGO DIGI SCAN Value Cogo Digitized Scanned Note: The two Tables are not to be confused with each other. Codes in Table 1 state how the compiler captured the parcels and is used in conjunction with contracted pricing. Codes in Table 2 will reside in the distributed ICF. Confirm with Bill that we will be using two Method Codes, COGO and DIGI, and dropping SCAN. Created: April 10, 2006 Page 12of 65

13 STANDARD OPERATING PROCEDURE CADASTRAL BASE MAPPING SECTION BASE MAPPING AND GEOMATICS SERVICES BRANCH, MINISTRY OF SUSTAINABLE RESOURCES MANAGEMENT COGO This method of data capture is defined as: Polygons created from plan information, using coordinate geometry (COGO), incorporated and georeferenced within the cadastral spatial file and attributed with corresponding key attribute link of PID, JUROL and PIN and their related attributes. The PIN or PID is supported when the shape of the parcel agrees with the legal description. The parent PIN is no longer used if the parcel has been further subdivided. Ensure each new COGO parcel is reflective of its legal description. The only parcels that are to be captured by COGO are: Those identified as missing in the not found file (nf.dbf) Those identified within the spatial file DESCRIPT field as excepted out but spatially have not been (i.e. L 123 EXC PL 2003) (Case Study pending) Those identified within the not found file (nf.dbf) DESCRIPT field as excepted out but spatially have not been (i.e. L 123 EXC PL 2003) (Case Study pending) Those identified by the compilers as per para Section 4.2. Note: Refer to para , , and to inclusive in Sections and for procedure on attribution. Related attribute information are to be obtained from the: Not found file (nf.dbf) Parcel file (pcl.dbf ) Tantalis reference spatial files i.e. primary, subdivisions (refer to CBMS-CBM-SP-003 Specification for Spatial Data Extracted From Tantalis). Note: Where no key link of PID, JUROL, PIN is available in either of the not found (nf.dbf) or parcel (pcl.dbf) files for the excepted out parcel, the compiler shall note this in the CMPLR_COMM field of the spatial file. Contractors in this case shall not undertake research to find a key link. Note: Refer to para , , and to inclusive in Sections and for procedure on attribution Compilation This method of data capture is defined as: Polygons created, compiled and positioned using either discrete digitizing or copied from other provided spatial data sets, (e.g. Tantalis, TRIM), and attributed with the key linking items of PID, JUROL and PIN and their related attribute information. The PIN or PID is supported when the legal description agrees with the shape of the parcel. The parent PIN is no longer used if the parcel has been further subdivided. The only parcels that are to be captured by digitizing or copying are: Those identified in the not found file (nf.dbf) Created: April 10, 2006 Page 13of 65

14 STANDARD OPERATING PROCEDURE CADASTRAL BASE MAPPING SECTION BASE MAPPING AND GEOMATICS SERVICES BRANCH, MINISTRY OF SUSTAINABLE RESOURCES MANAGEMENT Those identified within the spatial file DESCRIPT field as excepted out but spatially have not been (i.e. L 123 EXC PL 2003) (Case Study pending) Those identified within the (nf.dbf) DESCRIPT field as excepted out but spatially have not been (i.e. L 123 EXC PL 2003) (Case Study pending) Those identified as not in the spatial file when comparing with other provided cadastral based spatial datasets (i.e. Tantalis) (refer to 4.26 CBMS-CBM-ST-002 Compilation Case Studies) The key attribution link and their related attribute information are to be obtained from the: Not found file (nf.dbf) Parcel file (pcl.dbf ) Tantalis reference spatial files (i.e. primary, subdivisions) (refer to 4.26 CBMS-CBM-SP-003 Specification for Spatial Data Extracted From Tantalis) Note: Where no key link of PID, JUROL, PIN is available in either of the not found file (nf.dbf) or parcel (pcl.dbf) files for the excepted out parcel, the compiler shall note this in the CMPLR_COMM field of the spatial file. Contractors in this case will not undertake research to find a key link. Note: Refer to para , , , in Section for the procedure on attribution Fine Adjust This method of data capture is defined as: Polygons adjusted spatially to better fit designated control i.e. integrated survey control, CAD control, Digital Road Atlas, higher quality data sets, TRIM and where identified individual polygons require adjustment through a series of complex (multiple) parcel movements/manipulations using scaling, rubber sheeting, rotating and pickup/reposition processes. Note: Fabric adjustment in the compilation process is dependent on the information provided by the Local Government as to its accuracy Bulk Parcel Adjust This method of data capture is defined as: A spatial adjustment of a large number of polygons, defined as a minimum of 50, in 1 or 2 simple movements to better fit designated control i.e. integrated survey control, CAD control, Digital Road Atlas, higher quality data sets, TRIM. Data adjustment would simply involve picking up, moving and possibly rotating a large predefined set of polygons. There shall be no rubber sheeting or scaling of data. No attribution of parcels is required. Note: Fabric adjustment in the compilation process is dependent on the information provided by the Local Government as to its accuracy. Created: April 10, 2006 Page 14of 65

15 STANDARD OPERATING PROCEDURE CADASTRAL BASE MAPPING SECTION BASE MAPPING AND GEOMATICS SERVICES BRANCH, MINISTRY OF SUSTAINABLE RESOURCES MANAGEMENT Attribution This method of data capture is defined as: When compiling plans that are listed in the not found file (nf.dbf) by COGO means, if it is found that the parcel already exists in the provided spatial file and has no key attributes, the parcel shall be attributed with the corresponding information from the nf.dbf. The provided spatial file does not contain attributes and will require attribution with the corresponding information from the pcl.dbf. Note: Attribution will be for the fields as in para , , and in Section Quality Assurance Prior to commencing work, compilers undertaking compilation of ICF data shall provide the CBMS with a Quality Assurance (QA) manual, or if no formal QA document exists then a similar high level statement of quality management processes as approved by the organization s executive officer. The compiler shall provide the CBMS with details of in-process inspection/acceptance procedures and final inspection/acceptance procedures to verify that the delivered ICF product meets the specifications and standards and the contract requirements. An example of typical quality control procedures is shown in Appendix J. The CBMS shall review and approve the QA manual and the inspection/acceptance procedures before compilation work proceeds. Organizations undertaking ICF compilation shall use Java Conflation Suite (JCS) software to investigate the agreement or otherwise between ICF spatial data from different sources (edge matching). The CBMS shall identify the Reference and the Subject data sets. The topics to be investigated shall be as in CBMS-CBM-PE-002 Guidelines for Use of Java Conflation Suite with ICF and shall include typically; basic topology checks e.g. self intersecting polygons, gap removal between lines where necessary, point selection for non coincident points, overlaps, missing vertices, and geometry collections. The compilation organization shall provide the CBMS with quality control records in the form of screen shots and/or spatial files, describing the results of the JCS quality checks and the adjustments made to the spatial data. Created: April 10, 2006 Page 15of 65

16 STANDARD OPERATING PROCEDURE CADASTRAL BASE MAPPING SECTION BASE MAPPING AND GEOMATICS SERVICES BRANCH, MINISTRY OF SUSTAINABLE RESOURCES MANAGEMENT 5. Field Names and Attributes This chapter lists the current set of field names and their definitions for the ICF with some examples of the attributes. Abbreviations, coding, and naming conventions in field attributes must be consistent throughout the ICF. The Cadastral Base Mapping Section (CBMS) or ICF Compilers will create the following interim fields for the spatial and attribute files that are to identify compilation methods and comments relating to the compilation. These fields are for the purpose of providing information for data capture only and will not be stored with the final ICF. These interim fields are as follows: Field Name CBMS_CODE CBMS_COMM CMPLR_CODE CMPLR_COMM Description The CBMS will enter the coding for the probable method of capture of the parcel for the CBM compiler to follow. The CBMS may enter information relating to the parcel. The compiler will enter the coding of the actual method of capture of the parcel. The compiler will enter any information relating to compilation or anomalies of the parcel. Attribution of the following parcel fields, where information exists, is the sole responsibility of CBMS: CBMS_CODE, CBMS_COMM, DATAOWNER, LABSYM, XTRAC_DATE. Attribution of the following parcel fields, where information exists through compilation efforts or from other attribute and spatial data sets, is the responsibility of the ICF compiler (CBMS or Contractor): ACCURACY, ADDRMUNIC, ADDRSOURCE, ADDNOTES, ADDRTYPE, AREA, BLK, COMMENTS, CMPLR_CODE, CMPLR_COMM, CROWNADMIN, DESCRIPT, DIRECTION, FREEFORM, JUROL, LAND_DIST, LOT, METHOD, PCL, PCLLINKSID, PERIMETER, PID, PN, PLACENAME, PLANDEFDOC, PRIMARY, STREETNUM, STREETNAME, STREETYPE, STRNUMSUF, AND UNITNUMBER. AREA and PERIMETER is typically system generated, but there are occasions when operator intervention is need to update the fields. All data must be in UPPER CASE except for the COMMENTS field, which is at the discretion of the compiler. Mandatory attribution is required for these fields: DESCRIPT, LAND_DIST, DATAOWNER, METHOD, and ACCURACY (refer to Para Section 4.2.4). Attribution of the remaining ICF parcels is required when corresponding attributes exists in the provided spatial files and the pcl.dbf and nf.dbf attribute files (refer to Para Section 4.2.4). Where the DESCRIPT field contains EXC (exceptions), the associated PCL, LOT, BLK, or FREEFORM field will be prefixed with PT. (refer to Appendix B). Created: April 10, 2006 Page 16of 65

17 STANDARD OPERATING PROCEDURE CADASTRAL BASE MAPPING SECTION BASE MAPPING AND GEOMATICS SERVICES BRANCH, MINISTRY OF SUSTAINABLE RESOURCES MANAGEMENT 5.1 Typographical Conventions In this document, fixed values appear in courier plain text, and variable values appear in courier italic text. For example, in the following field/attribute description, PARK PL is a fixed value and plan number is a variable value. Field Name Attributes Attribute Notes DESCRIPT PARK PL plan number 5.2 Terminology Some readers might be confused by the specialized usage of terms in the ICF. For example, readers who are familiar with land titles may be accustomed to using the word parcel as it is defined in the Land Title Act: a lot, block or other area in which land is held or into which land is subdivided. In ICF terminology, the word parcel means a polygon defining legal property and uniquely identified by PID, PIN, JUROL or DESCRIPT. Note: Refer to the Glossary for a list of terms that have distinct and possibly unfamiliar meanings in the ICF. Created: April 10, 2006 Page 17of 65

18 5.3 Attributes Requests submitted to reformat Table to have each field name on one page with definition and examples All examples and sources listed below are currently under review by the ICF workgroup. The following table is current as of September 15, Note: Field names will change to reflect the ICF Geodatabase model in the future. Field Name Type Value Width Attribution Definition Source Examples ACCURACY Character string Alpha/ Numeric 32 MANDATORY Positional accuracy of the ICF in metres Data owner, ICF Compiler See Appendix C ADDRMUNIC Character string Alpha/ Numeric 50 REQUIRED if the information exists in the provided attribute files, pcl.dbf and nf.dbf Municipality, city, or town name as per civic address of the parcel Address Custodian ADDRSOURCE Character string Alpha 50 REQUIRED if the information exists in the provided attribute files, pcl.dbf and nf.dbf The custodian of the address information (BCA, Municipal or other) Address Custodian BCA, Municipal, Other ADDRNOTES Character string Alpha/ Numeric 30 REQUIRED if the information exists in the provided attribute files, pcl.dbf and nf.dbf Address custodian notes for the parcel Address Custodian ADDRTYPE Character string Alpha/ Numeric 12 REQUIRED if the information exists in the provided attribute files, pcl.dbf and nf.dbf The type of address according to the address custodian Address Custodian AREA Number Numeric 18 MANDATORY Typically system generated but may require recalculation through editing tools Geometric area of the polygon, (typically in the storage units of the shapefile). Can not be zero (0) Systemgenerated. Recalculate using editing tools when necessary Created: April 10, 2006 Page 18of 65

19 Field Name Type Value Width Attribution Definition Source Examples BLK Character string Alpha/ Numeric 16 REQUIRED if the information exists in the provided attribute files, pcl.dbf and nf.dbf or substantiated through CBMS research efforts A portion or a particular division of surveyed land called Block, with the exception of E&N Blocks Derived from the Legal Description (either Land Act or Land Title Act) stored in the DESCRIPT field. (Refer to Appendix A, Accepted Abbreviations) See Appendix B Figure 1 CBMS_CODE Character string Numeric 5 REQUIRED. Responsibility of the CBMS. Coding for the probable method of capture for the parcel may be entered for the ICF compiler to follow. This field will not be migrated to the GDB nor distributed to the ICIS partners The Data Capture Methodology Code. See Section 4.3 Data Capture Methodology CBMS input See Appendix D CBMS_COMM Character string Alpha 254 REQUIRED. Responsibility of the CBMS. Information may be entered relating to the compilation of the parcels.. This field will not be migrated to the GDB nor distributed to the ICIS partners CBMS comments to the ICF compiler relating to the parcel CBMS input COMMENTS Character string Alpha/ Numeric 254 REQUIRED only if the information is to describe anomalies regarding the parcel. This information is kept with the ICF during migration to the database whereas the CMPLR_COMM is not. Parcel information (identified by project operator) that does not fit into existing field criteria. If there is no attribute for PID, JUROL, or PIN, and if the parcel is not a REM, UCL, PARK, CP or RTC, then there must be an attribute in the COMMENTS field to explain the ICF compiler input If a data owner s spatial file has a legal DESCRIPT that reads PCL A PL A324 against a polygon, and no record or confirmation of this lot s existence can be found in the Created: April 10, 2006 Page 19of 65

20 Field Name Type Value Width Attribution Definition Source Examples parcel various databases (LTO, BCA, or Tantalis), then the DESCRIPT field will contain the term VERIFY and the COMMENTS field will contain the parcel description. (Refer to Section 6.11 Unverified) CMPLR_CODE Character string Numeric 5 MANDATORY. Responsibility of the contracted ICF compiler. Coding for the actual method of capture for the parcel is to be entered for the ICF Administrator for the purpose of quality assurance (QA) and invoice confirmation. This field will not be migrated to the GDB nor distributed to the ICIS partners The Compilation Code. See Section 4.3 Data Capture Methodology ICF compiler input See Appendix D CMPLR_COMM Character string Alpha 254 REQUIRED. Responsibility of the contracted ICF compiler. Information shall be entered relating to compilation or anomalies of the parcels. This field will not be migrated to the GDB nor distributed to the ICIS partners Contracted ICF compiler comments to the CBMS relating to the parcel ICF compiler input CROWNADMIN Character string Alpha 32 REQUIRED if the information exists in the provided attribute files, pcl.dbf and nf.dbf or Describes Crown Administered parcels as per CROWNADMIN CODE Appendix E and derived Tantalis and/or LTO See Appendix E Created: April 10, 2006 Page 20of 65

21 Field Name Type Value Width Attribution Definition Source Examples substantiated through CBMS research efforts based on the owner, legal notation and miscellaneous notes listed in the LTO data, in conjunction with Tantalis, provided to the CBMS. Crown owned parcels may have only the PIN attribute, any combination of PID, JUROL, and PIN attributes or none of the aforementioned (e.g., UCL or REMAINDERS). Parcels confirmed to contain only a PIN attribute must also have CROWN PROVINCIAL attribute in the field DATAOWNER Character string Alpha 50 MANDATORY. It is the responsibility of the CBMS Perceived ownership of the spatial and attribute data. Can be a combination of CBMS and Local Government or CBMS and Regional District Data Owner CROWN PROVINCIAL, CBMS, LG, RD DESCRIPT Character string Alpha/ Numeric 254 MANDATORY. Retrieve the information from provided attribute files, pcl.dbf and nf.dbf, spatial files, i.e. Tantalis spatial, or substantiate through CBMS research efforts The *abbreviated Legal Description (either Land Act or Land Title Act) of a surveyed property. (Refer to Appendix A, Accepted Abbreviations). Also describes polygons with nonconforming legal descriptions. If by description a parcel s shape can not be confirmed (i.e., no copy of the plan can be found) then the term VERIFY should be used in the DESCRIPT field, and a tentative description, if found, will go into the LTO and/or Tantalis and/or ICF Compiler *If the abbreviated legal description is more than the maximum width of the field, attribute with REFER TO THE LTO The following is one example of a parcel s legal description from the LTO followed by its abbreviated form. THE NORTHEAST ¼ OF DISTRICT LOT 4268, RANGE 5 COAST DISTRICT EXCEPT THE RIGHT OF WAY OF THE GRAND Created: April 10, 2006 Page 21of 65

22 Field Name Type Value Width Attribution Definition Source Examples COMMENTS field. (Refer to Section 6.11) The abbreviated format is automated where the data was initially provided by the LTSA and run through a software routine. Manual abbreviation is for those descriptions that have been researched through BC Online. Abbreviation should never alter the description of the parcel for which it was intended. TRUNK PACIFIC RAILWAY COMPANY AND EXCEPT PART LYING SOUTHWEST OF THE RIGHT OF WAY OF THE GRAND TRUNK PACIFIC RAILWAY AND EXCEPT PLANS AND PRP13746 In its abbreviated form: NE1/4 DL 4268 EXC THE GRAND TRUNK PACIFIC RLY AND EXC PT LYING SW OF THE RLY AND EXC PLS AND PRP DIRECTION Character string Alpha 2 REQUIRED if the information exists in the provided attribute files, pcl.dbf and nf.dbf, or substantiated through CBMS research efforts Global direction Address Custodian See Appendix F FREEFORM Character string Alpha/ Numeric 32 REQUIRED if the information exists in the provided attribute files, pcl.dbf and nf.dbf or Part of the Legal Description of a parcel. This field represents a portion or a particular division of Derived from the Legal Description or alternate See Appendix B Figure 2 Created: April 10, 2006 Page 22of 65

23 Field Name Type Value Width Attribution Definition Source Examples substantiated through CBMS research efforts land that does not fit the above PCL, LOT, or BLK field attributes definitions. The description of an E&N (Esquimalt and Nanaimo) Block does not carry the E&N designation in the DESCRIPT field. The LTO does not recognize the E&N suffix, whereas Tantalis requires the suffix when querying description of a parcel stored in the DESCRIPT field. (Refer to Appendix A, Accepted Abbreviations). JUROL Character string Numeric 30 REQUIRED if the information exists in the provided attribute files, pcl.dbf and nf.dbf Concatenation of BC Assessment jurisdiction, and roll number. There can be a one JUROL to many PID relationships (i.e., one assessed owner to many parcels). There can also be a JUROL and no PID relationship BCA LABSYM A field in the spatial file for attribute tracking by CBMS operator. This field is for CBMS internal use only. LAND_DIST Character string Alpha 50 MANDATORY. Retrieve the information from provided attribute files, pcl.dbf and nf.dbf, spatial files, ex. Tantalis spatial, or substantiate through CBMS research efforts Land Districts are administrative areas of the Province, used to group primary parcels of land for surveys and legal descriptions. When a Land District name has a qualifying Group number, it is appended to the LAND_DIST field, rather Tantalis See Appendix G Created: April 10, 2006 Page 23of 65