WPCO 2BBVPZB3|B10cpi?xxx,wx6X@8;X@ HP LaserJet IIISiHPLASIII.PRSx  @,\,-{X@USUK    X` hp x (#%'0*,.8135@8:a8TechnicalTechnical Document Style(D a) . PleadingHeader for numbered pleading paperP@n   $] X X` hp x (#%'0*,.8135@8:PPCPP(PPPPPPPPPPCխxCCCCCCCCxxxxxxPPPPCxPx5PPP5PPPxxxxPPP㭠xxxNTCPYXȅPP.PPPPxx5PP2/$|'*C,-"^Sd SdduSdSSdd%SdSdSdSSS uduTudSdd,2ddddddddddS, SSSSSSSSddddSdSdddS,uuudddNiSdonddG,dd,,S,d"S^CPrխCPP]CPCCPP꭭Cȭ㠠PCPCPCCCՓ]Px]C]PCPP(PPPPPPPPPPCխCCCCCCCCPPPPCPCPPPC]]]PPP㻠xxNTCPYXȅPP9xxPPCxP"S^!!+CCkP((/F!(!!CCCCCCCCCC!!FFFCzPPWWPI]W!VI=II%IIIIIIIIII=zzzzzğzzzzz========zzzzzzzzzzzzzIIII=zIz=III=ПVVVzzzzIIIЫznnNM=zzIzzzzzQPzIzI4nnzIIzz=nI2= y689b;"S^..;]]o%88Aa.8..]]]]]]]]]]..aaa]ooxxofx.So]xoxofxooof...N]%]]S]].]]%%S%]]]]8S.]SxSSS8+8a8.888888888888f.o]o]o]o]o]xSo]o]o]o]........x]]]]]x]x]x]x]oSo]x]f]oSx]o]o]o]xSxSxSxSx]o]o]o]o]]]]]]x]x]8f8f88.fS8oS]%]8]8]8]%x]x]x]]]x8x8x8oSoSoSoSf8f8f8x]x]x]x]xoSfSfSN:.Z]8f]]]]]>=]8{{]8 88]88]]SS%88"S^.8O]]x.88Aa.8..]]]]]]]]]]88aaafxxxxofx.]xfxoxofxooof8.8a].]f]f]8ff..].ffffA]8f]]]SA/Aa8.888888888888f.x]x]x]x]x]x]o]o]o]o]........xfffffxfxfxfxfo]x]xfffo]xfofx]x]x]x]x]x]xfo]o]o]o]fffffxfxf8f8f88.f]8x]f.f8f8f8f.xfxfxfffxAxAxAo]o]o]o]f8f8f8xfxfxfxfo]fSfSN:.]]8f]]]]]>=]8{{]8(SS]88]]ff.S8"S^..;]]o%88Aa.8..]]]]]]]]]]..aaa]ooxxofx.So]xoxofxooof...N]%]]S]].]]%%S%]]]]8S.]SxSSS8+8a8.888888888888f.o]o]o]o]o]xSo]o]o]o]........x]]]]]x]x]x]x]oSo]x]f]oSx]o]o]o]xSxSxSxSx]o]o]o]o]]]]]]x]x]8f8f88.fS8oS]%]8]8]8]%x]x]x]]]x8x8x8oSoSoSoSf8f8f8x]x]x]x]xoSfSfSN:.Z]8f]]]]]>=]8{{]8 88]88]]SS%88"S^$88YC!!':!8888888888:::8fCCHHC=NH2C8SHNCNHC=HC^CC=/888288882S8888!282H222!!:!!!d!!!!!!!!!!=C8C8C8C8C8dYH2C8C8C8C8H8N8N8N8N8H8H8H8H8C2C8H8N=N8C2H8C8C8C8H2H2H2H2H8C8C8C8C8N8N8N8N8N8H8H8!=!=!!=2!C288!8!8!8H8H8H8N8N8d^H!H!H!C2C2C2C2=!=!=!H8H8H8H8^HC2=2=2N#68!=88888%%SS8!JJ8S!!!8d!!88d22d!d!21C7=>L}@hB"S^&&1LLy[..5P&.&&LLLLLLLLLL&&PPPL[[cc[Tjc&D[Lrcj[jc[Tc[[[T&&&@LLLDLL&LLDrLLLL.D&LDcDDD.$.P.&............T&[L[L[L[L[LycD[L[L[L[L&&&&&&&&cLjLjLjLjLcLcLcLcL[D[LcLjTjL[DcL[L[L[LcDcDcDcDcL[L[L[L[LjLjLjLjLjLcLcL.T.T..&TD.[DLL.L.L.LcLcLcLjLjLc.c.c.[D[D[D[DT.T.T.cLcLcLcLc[DTDTDN0&IL.TLLLLL32rrL.eeLr...L..LLDD.."S^..:[[m$77@`.7..[[[[[[[[[[..```[mmvvmdv.Rm[vmvmdvmmmd...M[$[[R[[.[[$$R$[[[[7R.[RvRRR7+7`7.777777777777d.m[m[m[m[m[vRm[m[m[m[........v[[[[[v[v[v[v[mRm[v[d[mRv[m[m[m[vRvRvRvRv[m[m[m[m[[[[[[v[v[7d7d77.dR7mR[$[7[7[7[$v[v[v[[[v7v7v7mRmRmRmRd7d7d7v[v[v[v[vmRdRdRN9.X[7d[[[[[=<[7yy[777[77[[RR$77"S^!,6CCoh,,,CK!,!%CCCCCCCCCC%%KKK;{`YY`QJ``,4`Qw``J`YJQ``~``Q,%,?C,;C;C;,CC%%C%hCCCC,4%CC`CC;@@H,!,,,,,,,,,,,,C%`;`;`;`;`;wYY;Q;Q;Q;Q;,%,%,%,%`C`C`C`C`C`C`C`C`C`C`;`C`C`C`C`CJC`;`;Y;Y;Y;Y;`CQ;Q;Q;Q;`C`C`C`C`C`C`C,C,C,,,C4,`CQ%Q,Q,Q,Q%`C`C`C`C`Cw`Y,Y,Y,J4J4J4J4Q,Q,Q,`C`C`C`C~``CQ;Q;N/!=]x]8 88]88]]SS%8~~~~nx\\\w.\77\\\wwwweeC\.wR)EreewwwwIeenR\\\wwwrrr\SRRRRRRRRe@@@@@@@@@@@@Dxio\eEfRfIfRxe|W87y\r\`xWlRx\\]\ceIfIs`Wx\rrigew"S^!,JCCo,,,CL!,!%CCCCCCCCCC,,LLLC|`Y``YQhh4ChY~`hQh`JY````Y,%,MC,CJ;J;,CJ%,J%oJCJJ;4,JC`CC;55E,!,,,,,,,,,,,,J%`C`C`C`C`C``;Y;Y;Y;Y;4%4%4%4%`JhChChChC`J`J`J`J`C`C`JhChC`C`CQJ`C`C`;`;`;`;`JY;Y;Y;Y;hChChChChChJhJ4J4J4,4JC,hJY%Y,Y,Y,Y%`J`J`JhChC``;`;`;J4J4J4J4Y,Y,Y,`J`J`J`J``CY;Y;N/!HC,CCCCCC(,ddC(ddCd(%CCC,,CCJJ,C(tLLIILLPP!5L%n_B!7f_nfffXsI1RaI[IJ``Ij[T?xxxNx6X@KX@L!1sC8:s2PkCXP /xC8/:x2p}wCXLIdSW2PkCPFdSOW2p}wCL:PC22PkCP8PCo<2p}wCL[E(!eVE2PkChP\H(!VH2p}wChL-i=3 i2PkC&P +n=3_ n2p}wC&L6I=s2PkCP 4I=Es2p}wCL~)`8.z`2PkCP'd8.jd2p}wC~)`8.!C`2x(CXLL:!E:2PkC,P~)N-&3\NxzPCP1^6.3F:^xzPCXPD"~)[8.D'[2PAP(a$J,!KeJ\  PCPa$M,!W£eM4  p(AC2O #XX2PQXP# M  >? 1991 DIGITAL CARTOGRAPHIC FILES M  g H>USER GUIDE  M M M  P M@M MapInfo for Windows Format M M M * * * * * * * * * ;Hn #&Q2PQ &P# ;Hn  *  U M M Produced by the Geography Division "SStatistics Canada *  U# %AUGUST 1993 *U # J2PQ zP#  H( La version fran'aise de ce guide est disponible sur demande (0*0*0*  J # J2PQ zP# __________________________________________________________________________________ _  H PREFACE  HZ  ___________________________________________________________________________________ This document is intended to provide the user with an understanding of the 1991 Digital Cartographic File(DCF) products, their uses and limitations.  J  The Digital Cartographic Files are geographic boundary files for thematic mapping applications used by Geographic Information Systems and mapping software packages. The DCF do not include any software or instructions on how to use the product within specific GIS or mapping packages. These products are basic boundary files in a polygon format. The Digital Cartographic File products discussed in this guide cover the following levels of standard geographic areas: XX` ` Provinces and territories (PR/TERR)(#` ` ` Census divisions (CD) equivalent to counties(#` ` ` Census subdivisions (CSD) equivalent to local municipalities(#` ` ` Census tracts (CT) equivalent to neighbourhoods(#` All Digital Cartographic File products were derived from the 1991 Enumeration Area Digital Boundary File  ~J base. Detailed information for these files is provided in the 1991 Digital Boundary Files User Guide. Purchasers of a Census Tract Digital Cartographic File will receive an additional file of major streets and some railway features used to define the census tract boundaries. This file, called the Skeletal Street Network File(SSNF), has been produced to provide some cartographic reference features for underlaying the Census Tract cartographic files in thematic mapping applications. A description of Skeletal Street  ~J< Network Files is provided in the 1991 Skeletal Street Network FileUser Guide.  ~J ARC/Info is a registered trademark of the Environmental Systems Research Institute  ~J| MapInfo is a registered trademark of Mapping Information Systems Corporation. Windows is a trademark of Microsoft Corporation. 0*0*0*  H "a TABLE OF CONTENTS Đ*U    X 1.ABOUT THIS GUIDE p["(#H 1 X  2.XOVERVIEW OF THE DIGITAL CARTOGRAPHIC FILE PRODUCTS(#p["(#H 2 X  X2.1X` ` Description(#` p["(#H 2 X2.2X` ` Purpose of the Digital Cartographic Files(#` p["(#H 2 X 2.3X` ` Geographic Reference Date ` p["(#H 2 X2.4X` ` Comparison to the 1986 CARTLIB Product(#` p["(#H 3 X 2.5X` ` The Census Geography Hierarchies ` p["(#H 3 X 3.GEOGRAPHIC CODES p["(#H 4 X 4.DATA QUALITY STATEMENT p["(#H 6 X 4.1X` ` Lineage ` p["(#H 6 X 4.2X` ` Positional Accuracy ` p["(#H 8 X 4.3X` ` Attribute Accuracy ` p!(#G 10 X 4.4X` ` Logical Consistency ` p!(#G 11 X 4.5X` ` Completeness ` p!(#G 11 X 4.6X` ` Other Considerations ` p!(#G 12 5.XTECHNICAL NOTES(#p!(#G 13 X 6.GLOSSARY OF TERMS p!(#G 14 X 7.SUPPLEMENTARY INFORMATION p!(#G 19 X 7.1X` ` Related Geographic Products and Services ` p!(#G 19 X 7.2X` ` For further information ` p!(#G 21 X›7.3X` ` Additional references and services(#` p!(#G 22 SUPPLEMENT 1: EA LINKAGE ERRORS ON THE 1991 GEOGRAPHIC ATTRIBUTE DATA BASE p!(#G 23@0*0*0*  H Q5   yxdddy  ~J K(#U# ?c> P>WQ\P#Page ؐ:Statistics CanadaK(#U,,1991 Digital Cartographic FilesK(#U#XLc> P>WQFXP#   __________________________________________________________________________________  H     I. A. 1. a.(1)(a) i) a) 1. 1.(1)(a)(i) 1) a) 1.XABOUT THIS GUIDE (#  HX  __________________________________________________________________________________ This User Guide is intended for users of any or all of the Digital Cartographic File (DCF) products. The guide provides an overview of these Digital Cartographic Files including a comparison with the equivalent 1986 product (called CARTLIB), a data quality statement and a glossary of terms. The purpose of a data quality statement is to provide detailed information for users to evaluate the suitability of the data for a particular use.  ~J The 1991 Digital Boundary Files User Guide provides more detailed background information on the digital boundary files used to create the DCFs. In addition, more details on geographic terms can be found in the  ~J 1991 Census Dictionary (Catalogue 92301E or 92301ED). This User Guide does not provide information on specific software packages for using the Digital Cartographic File products. The user is advised to contact the specific software vendor for information. This report is based on the best information available at the time of its release. It in no way constitutes a warranty of the data in the event that users may observe characteristics that deviate from those stated in this document. $0*&&Ԍ H  __________________________________________________________________________________  2.XOVERVIEW OF THE DIGITAL CARTOGRAPHIC FILE PRODUCTS(# __________________________________________________________________________________   H  X2.1X` ` Description (#` XThe 1991 Digital Cartographic Files are computer boundary files of selected standard geographic areas. Each Digital Cartographic File includes geostatistical area boundaries that have been modified to follow shorelines and coastlines. In addition some major lakes are included in the files. Digital Cartographic Files are available for each of the following geographic areas:(# XX` ` Provinces and territories (PR/TERR)(#` ` ` Census divisions (CD) equivalent to counties(#` ` ` Census subdivisions (CSD) equivalent to local municipalities(#` XX` ` Census tracts (CT) equivalent to neighbourhoods(#` XThe 1991 Digital Cartographic Files were derived from the 1991 Digital Boundary Files with modifications at the shorelines and coastlines (hereafter referred to as shoreline) and the addition of major lakes.(# XThe x,y coordinates defining the digital boundaries are available in the Lambert Conformal Conic  ~J projection. They are provided as a standard product in the MapInfo for Windows format. They  ~J can also be ordered from Statistics Canada in ARC/Info Export format.(#  H  X2.2X` ` Purpose of the Digital Cartographic Files (#` XWith the appropriate computer software, Digital Cartographic Files provide the framework for  Jp  thematic mapping to support applications such as land use and demographic studies, or social, economic, and market research. (#  J XIn particular, the shoreline adjusted boundary files were produced to support thematic mapping of data from the 1991 Census of Population and Housing and other data sources using Statistics Canada's standard geographic area definitions. (#   H X2.3X` ` Geographic Reference Date (#` XAll 1991 Census data reflect the census reference date of June 4, 1991. There is also a geographic reference date on which the geographic framework takes effect. This date is earlier than the census reference date in order to give Statistics Canada enough time before Census Day to process the necessary boundary and name changes. For the 1991 Census, the Geographic Reference Date is January 1, 1991. The Digital Cartographic Files reflect the legislative/administrative geographic framework as it existed on January 1, 1991, provided that the information on any changes was received by Statistics Canada from the provincial or territorial authorities by March 1, 1991.(#$0*&&Ԍ H ԙX 2.4X` ` Comparison to the 1986 CARTLIB Product (#` XFor 1986, a cartographic library of computer files of standard geographic areas, called CARTLIB, was created. Each CARTLIB file included boundaries adjusted to follow shoreline where appropriate, and some major lakes. The primary difference between the 1986 CARTLIB product and the 1991 Digital Cartographic Files is in the methodology used to create the base files on which the shoreline adjustments were made:(# XThe 1986 base files were created by digitizing 1986 boundaries as drafted on map sheets of various scales (CSDs were drafted on the National Topographic Series (NTS) published by Energy, Mines and Resources at scales of 1:50,000, 1:250,000, 1:500,000 or 1:4,000,000 depending on the population density of the CSD and the availability of the maps. 1986 CTs were digitized from the NTS 1:50,000 map series.(#  X(# XThe 1991 base files were created by aggregating digital enumeration area (EA) boundaries. The EA Digital Boundary File was created using different methodologies, some automatically, some from an inhouse process involving semimanual procedures, and the remaining through the  ~J digitization of boundaries on source maps. Detailed descriptions are provided in the 1991 Digital  ~J Boundary Files User Guide.(# XAlthough the sources for the base files for the 1986 and 1991 products differ, except for one specific case described below, the shoreline and hydrographic features in the 1986 CARTLIB products were used for the 1991 cartographic files.(# XThe only major physical feature change is the addition of the north shore of Laval in the 1991 files.(#  H  X2.5X` ` The Census Geography Hierarchies (#` XThe geographic areas included in the Digital Cartographic Files are part of the standard hierarchies used by Statistics Canada.(# XCSDs can be combined in a hierarchical fashion to form CDs, then provinces/territories, and finally Canada, as shown in the following diagram (from the smallest unit aggregated to the larger geographic units).(# XCSD > CD > PR/TERR > CANADA(# XCensus tracts (CTs) are delineated within all 25 census metropolitan areas (CMAs) and 14 of the 115 census agglomerations (CAs). The only hierarchical relationship depicted in the digital cartographic files is their aggregation to CMAs or CAs, as follows:(# XCT > CMA/CA(# $0*&&Ԍ H ԙ __________________________________________________________________________________  H  3.XGEOGRAPHIC CODES (#  HX  __________________________________________________________________________________ XCSD Digital Cartographic File(#  Jx XEach CSD is uniquely identified by its Standard Geographical Classification (SGC) code. The SGC is Statistics Canada's official classification providing unique numeric identification for three types of geographic areas. These are:(# X©X` ` $provinces and territories (PR/TERRs)(#` X©X` ` $census divisions (CDs)(#` X©X` ` $census subdivisions (CSDs)(#` XThe three geographic areas are hierarchically related. CSDs aggregate to CDs, which in turn aggregate to a province or a territory. This relationship is reflected in the 7digit SGC code:(# XX` ` $PR/TERR6Xhh?XHCDXQXppZXd CSD(# XX` ` $ XX -6hh?` HXXQppZd XXX xxvX (# XX` ` $2 digitsX -X6 Xhh?XH2 digits ppZ Xd 3 digits(# XThe 7digit SGC code is assigned to each CSD polygon.(# XCD Digital Cartographic File(#  J XEach CD is uniquely identified by the first 4 digits of the Standard Geographical Classification  J (SGC) code. These 4 digits provide unique identification of CDs and reflect the hierarchical relationship that CDs aggregate to a province or territory. The 4 digit code is described by:(# XX` ` $PR/TERR6Xhh?CD(#h XX` ` $ XXX -X6Xhh?XX(#h XX` ` $2 digitsX - X6 2 digits(# XX` ` $(#` XPR/TERR Digital Cartographic File(#  J XEach PR/TERR is uniquely identified by the first 2 digits of the Standard Geographical  J Classification (SGC) code. (# XX` ` $PR/TERR(#` XX` ` $ XX(#` XX` ` $2 digits(#` $0*&&Ԍ H  3.XGEOGRAPHIC CODES(CONTD) (#  H  XCT Digital Cartographic File (# XCTs are identified by a 6 character numerical name of the form xxx.xx where x is one digit. This form is referred to as the "CT name". These CT names are designed to be unique within the Primary Census Metropolitan Area (PCMA) or Primary Census Agglomeration (PCA) containing the CT. If the CMA or CA does not have any component PCMAs or PCAs, the CT name is unique within the CMA or CA. For the 1991 Census geographic structure, the CT names are unique within a CMA or CA regardless if it contains PCMAs and/or PCAs. This uniqueness may not remain in subsequent censuses as more PCMAs and PCAs are created and consolidated.(# XIn order to identify a CT uniquely within a province or across Canada, the relevant CMA or CA code is provided with the CT name in the CT Digital Cartographic Files.(# XIn the MapInfo version of the CT Digital Cartographic Files, CTs are identified by a 9character code XXXYYY.YY (including the decimal point). The first 3 characters (XXX) represent the 3digit CMA/CA code and the last 6 characters (YYY.YY) represent the 6character CT name (CT "names" are actually numbers).(# XLeading zeroes in the 6character CT name and in the 3digit CMA/CA code must be retained and not left blank. For example, 040.00 is a valid CT name, but 40.00 or 40 are not valid. Often, if the 2 decimal digits are 00, they may not be shown on Statistics Canada's reference maps, but they must be used for processing with digital files which include the CT name.(# XCMAs and CAs are identified uniquely across Canada by a 3digit code. Note that the first digit of the 3digit CMA/CA code is the second digit of the PR/TERR code if the CMA or CA does not straddle a provincial or territorial boundary (as in the case of the CMA of OttawaHull which straddles the Ontario/Quebec border).(# XThe terms CT name and CT code are not synonymous. The former is the numerical name (described above) that is used to identify CTs on maps and in data products, whereas the CT code is a fourdigit numeric identifier used to access a CT on Statistics Canada's internal digital files. The CT name is used with the CMA/CA code in the CT Digital Boundary Files (making a 9character code) with leading and trailing zeroes specified explicitly.(# $0*&&Ԍ H  __________________________________________________________________________________  H  4.XDATA QUALITY STATEMENT (#  HX  __________________________________________________________________________________ XThe 1991 Digital Cartographic Files were created by adding hydrographic features to the equivalent 1991 Digital Boundary Files. The user should review the Data Quality Statement contained in the  ~Jx 1991 Digital Boundary Files User Guide (since the quality of those files has a direct implication on  ~J@ the derived Digital Cartographic Files) and the attached supplement EA Linkage Errors on the 1991  ~J Geographic Attribute Data Base.(# XDetails in this document consider only the additional processes required to create the 1991 Digital Cartographic Files from the 1991 Digital Boundary Files.(# XThe source files from which the DCFs are derived are "frozen" at a specific point in time after they are created and verified, and before the creation of any derived files or products (e.g. the DCFs). Errors identified after that date are documented but not corrected. Thus errors identified in the boundaries or codes in the DCFs are not corrected to ensure their "state" conforms to the geographic infrastructure from which the files were built.(#  Hh  X4.1X` ` $Lineage (#`  ~J XLineage includes descriptions of the source material from which the data were derived and the methods of derivation, including the dates of the source material and all transformations involved in producing the final digital files or map products.(#  XSource Materials for the CSD, CD and PR/TERR DCFs(# XX` ` $The CSD digital cartographic boundaries were obtained from the 1991 CSD Digital Boundary File, which in turn were derived from the 1991 Enumeration Area (EA) Digital Boundary File. The CD and PR/TERR Digital Cartographic Files were created by aggregating the CSD cartographic boundaries.(#` XX` ` $The shorelines and lakes were obtained from the 1986 CARTLIB file, which in turn was derived from the 1981 CD CARTLIB file. The 1981 file was digitized from mylar EMR base maps at 1:2,000,000(for the ten provinces) and 1:5,000,000(for the two territories) from  ~J a Lambert Conformal Conic projection with standard parallels at 49oN and 77oN. The 1986 file was enhanced by digitizing 1:250,000 NTS maps for shorelines where there was a high concentration of small CSDs; This ensured that all CSD computed centroids were contained within the CSD polygons. Other enhancements included extracting the Toronto, Montr)al and Qu)bec shorelines (digitized at 1:50,000) from the 1986 CT CARTLIB files. Finally, for the national 1991 CARTLIBs, the northern shoreline of Laval was added by digitizing the shoreline from the 1991 Street Network File for Laval. The 1986 and 1991 enhancements also involved projection transformations from Transverse Mercator to Lambert Conformal Conic. (#` $ 0*&&Ԍ H  X4.1X` ` $Lineage(contd) (#` XSource Material for the CT DCF:(# XX` ` $The CT boundaries were obtained from the 1991 CT Digital Boundary File, which in turn  ~J had been derived from the 1991 EA Digital Boundary File. Refer to the 1991 Digital  ~J Boundary File User Guide for a complete description.(#` XX` ` $The CT shoreline and lakes were derived from two separate sources. The 1991 Street Network File (SNF) provided hydrographic features for the areas of the CTs covered by the SNF. The SNF hydrography was originally digitized from municipal documents where available (scales varying from 1:1,000 to 1:30,000), or the 1:50,000 NTS map sheets and Ontario Base Maps. (#` XX` ` $For areas outside SNF coverage, the shoreline was derived from 1986 CARTLIB files. These shoreline features were digitized from the 1:50,000 NTS map sheets produced by Energy, Mines and Resources.(#` XMethod of Derivation:(#  ~Jh X1.X` ` $Working in an ARC/Info Version 6.0 environment, the shoreline features were extracted from the 1986 source files described above, the 1991 Digital Boundary Files were "clipped" using the shoreline coverage, and both files were merged together. During this process, boundaries which extended into water bodies were replaced with a more realistic shoreline, and some major lakes were added.(#` X2.X` ` $The CSD boundary areas, as depicted in the resulting digital cartographic file, were aggregated through the hierarchical nature of the SGC code to create a digital cartographic file for each CD and PR/TERR. This ensured that the files would match appropriately when overlaid.(#` X3.X` ` $The files were then processed through inhouse computer programs to determine which individual polygons in the coverages exceeded the 4,000 point per polygon or 8,000 point per geographic unit (if comprised of more than 1 polygon) limitation imposed by the  ~JX MapInfo software. In the cases where these point limitations were exceeded the number of points was reduced to respect the 4,000 and 8,000 point limitations. An inhouse program was executed to ensure that the point limitations were respected and that the overlay compatibility among the CSD, CD and PR/TERR files was retained.(#` XX` ` $(#`  ~J X4.X` ` $Using an inhouse enhanced version of MapInfo's ARCLINK module, the digital  ~J cartographic files were converted from ARC/Info 6.0 to MapInfo Windows Version 2.0.(#` $ 0*&&Ԍ XSource Material for the CT DCF(contd)(#  ~J X5.X` ` $Once the final DCFs were successfully converted to MapInfo, all polygons representing  ~J lakes were processed through a series of MapInfo commands to remove their topology. This process converted water bodies from polygons with labels to "holes" or nonpolygon items. This process allows for the onetoone matching of the geographic codes associated with 1991 Census data without users having to manipulate datasets to account for lake  ~J polygons. Thus the lake "holes" cannot be accessed in MapInfo (they cannot be  ~J selected).(#`  ~J( X6.X` ` $At this point, the map tables in MapInfo contain one record per polygon. The last step  ~J in preparing the MapInfo formatted files was to link geographic units with multiple parts (polygons). This link ensured the value assigned to these multiple polygon units was  ~J "counted" only once by the MapInfo software when calculating frequency tables since there would be only one record per geographic unit, regardless of the number of polygons  ~J making up that geographic unit.(#`  ~J X7.X` ` $An additional step was performed on the CT MapInfo Digital Cartographic Files to provide the CT numeric name in a form suitable for linking to 1991 Census electronic data files.  ~J0 This step was performed in MapInfo, and concatenated the CMA/CA code and the CT numeric name to provide one field with the combined unique CT identifier.(#`  ~J XAll processing was done using ARC/Info Version 6.0 and MapInfo Windows Version 2.0 in the Lambert Conic Conformal projection.(#  ~J XThe CSD file was also subdivided into provincial and territorial files in MapInfo.(# XEach of the 39 CT Digital Cartographic Files (one per tracted CMA/CA) were processed separately and independently.(#  H  X4.2X` ` $Positional Accuracy (#`  ~J  XPositional accuracy is the difference between the "true" position of a feature in the real world and "estimated" position stored in the digital file.(#  XPositional accuracy depends on the quality of the source material used and the process used to create the files (ie. manual drafting, digitizing etc.). No numerical measurements of positional accuracy have been made for these products. (# XFor this report, the "true" boundaries against which the CSD, CD and PR/TERR cartographic files are compared, are those as depicted on the 1991 CD/CSD Reference Maps. The CT cartographic files were compared with the CMA/CA/CT Reference Maps.(# X(#$ 0*&&Ԍ  H  X4.2X` ` $Positional Accuracy(contd) (#` X(# XCSD, CD, PR/TERR Digital Cartographic Files(# XThe cartographic boundaries were visually checked by producing several regional plots (in  ~Jx ARC/Info) at appropriate scales of both the nongeneralized and generalized cartographic files. The CSDs, CDs and PR/TERRs were plotted on the same map, using different colours for differentiating the geographic areas.(# XThe plots of the generalized files were visually compared with the CD/CSD Reference maps. Approximately 50% of the boundaries and codes were checked. All inconsistencies found also existed in the nongeneralized files, indicating that the generalization process had not caused them.(# XInconsistencies resulted from the use of the EA based 1991 CSD Digital Boundary File and the 1986 CARTLIB shoreline. Even though boundaries extended into water bodies in the Digital Boundary File, because they were originally created at the fine level of detail of the EA boundary (i.e., larger scale), they were more detailed than the 1986 CARTLIB shoreline. This caused either a misrepresentation of a boundary or the creation of an extra polygon which may actually be water, but has been coded to a geographic unit. These inconsistencies were not corrected. Twentyfour such cases were identified along the Newfoundland shoreline, and four in Ontario (around Manitoulin Island). There may also be minor occurrences of these inconsistencies along the B.C. coastline, where a small CSD should appear on the coast, but the DCF places it a short distance inland.(#  ~JP XSpot checks were performed on the graphic terminal to determine the correctness of the MapInfo conversion.(# XCT Digital Cartographic Files(#  ~J XThe ARC/Info version of the ungeneralized CT cartographic files were plotted and visually checked with the CMA/CA/CT Reference Maps. All tracted CMA/CAs were plotted and all CT boundaries checked. Any discrepancies between the CT cartographic files and the reference maps were further checked with source maps used inhouse for census collection. The boundary discrepancies were minor and occurred in the CMA of Montreal (CMA code 462) on the boundaries of CTs 865, 510 and between 660.01 and 660.02. In these cases, the CT cartographic files matched the CT boundaries as depicted on the source maps. Additional minor boundary  ~Jx discrepancies may occur (e.g., a followup check of the MapInfo converted files with the CMA/CA/CT reference maps for Hamilton CMA identified a small jog in the north boundary of CT 040.00 which was not shown on the CMA/CT map). These boundary discrepancies will not have any impact on the thematic mapping purposes for which these digital files were created.(# $ 0*&&Ԍ H ԙ X4.3X` ` $Attribute Accuracy (#`  ~J XAttribute accuracy refers to the accuracy of the nonpositional information attached to each polygon contained in the Digital Cartographic Files.(#  XCSD, CD, PR/TERR Digital Cartographic Files(# XThe 1991 PR/TERR DCF contains a 2 digit PR/TERR code used to identify each polygon in the  ~J@ file. In the MapInfo table structure, the field is labelled PROV and defined as an integer (no index).(# XThe 1991 CD DCF contains a 4 digit PROV/CD code used to identify each polygon in the file. In  ~J` the MapInfo table structure, the field is labelled CD and defined as an integer (no index).(# XThe 1991 CSD DCF contains the 7 digit Standard Geographical Classification (SGC) code  ~J (PROV/CD/CSD) used to identify each polygon in the file. In the MapInfo table structure, the field is labelled CSD and defined as an integer (no index).(# XTo verify the accuracy of the attribute data attached to each of the cartographic file polygons, the 4 digit CD code and the last 3 digits of the CSD codes were plotted in different colours on the  ~J ARC/Info plots discussed under Positional Accuracy. The labels were visually checked with those on the CD/CSD Reference map series.(# XIn the area of Langley B.C. and in Ontario south of Chatham, labels differed from those on the reference maps. In the case of Langley, B.C., the CD/CSD Reference Map was found to be in error (the CSD DCFs depict the correct SGCs) . In the case of southern Ontario, CSD 3536018 and CSD 3536019 in the DCF were found to have their SGC codes reversed. This error was not corrected in the DCF.(# XCT Digital Cartographic Files(#  ~J8 XX` ` $CT codes on the ARC/Info plots described earlier were checked with the CMA/CA/CT  ~J Reference Maps. Subsequent checks of the CT codes in the MapInfo formatted CT DCFs were made onscreen with the CMA/CA/CT Reference Maps. This was performed by  ~J using the AUTOLABEL feature within MapInfo (with "Allow Duplicates" and "Overlapping Labels" checked). Where a CT was split into more than one part (e.g. by a river), only one of the parts was labelled using this feature. The other part had to be labelled manually (using the Label tool).(#` XX` ` $A discrepancy was found in Hamilton. CT number 062.2 shown on the reference map should read 026.02. The label is correct in the Hamilton CT DCF.(#` XX` ` $No other discrepancies were identified.(#` XThe DCFs contain geographic codes attached with each geographic unit. (#  ~J(# XNote that lakes included in the MapInfo DCFs do not have attribute (e.g. names) information associated with them. Nor are they counted in the total number of polygons in the files. Nor can they be selected.(#$ 0*&&Ԍ H ԙX 4.4X` ` $Logical Consistency (#`  ~J XLogical consistency describes the fidelity of relationships encoded in the data structure of the digital spatial data (ie. how well elements of the data structure follow the rules imposed on them).(#   ~J XAutomated processing through both ARC/Info software verified that all boundary polygons were topologically correct, that they closed with no overlaps, overshoots or slivers. Lines are intersected only where intended and no lines are entered twice.(# XThe 1991 CSD, CD and PR/TERR Digital Cartographic Files are consistent with each other since the CD and PR/TERR files were created from the CSD boundaries, and the generalization process was designed to maintain the consistency. However, these cartographic files may not be consistent with the CT Digital Cartographic File since different source shoreline files were used. (# XThe lakes included in the DCFs cannot be selected or shaded.(#  Hh  X4.5X` ` $Completeness (#`  ~J XCompleteness expresses the degree to which the geographic entities (features) are captured according to the data capture specifications. It also contains information about selection criteria,  ~J definitions used and other relevant mapping rules.(# XFrequency checks were made between the generalized and nongeneralized cartographic files to ensure the same numbers of geographic units and parts were included in each file (thus no polygons were lost or created during the generalization process).(# XVerification of the total number of geographic units was manually performed against established counts (12 PR/TERRs, 290 CDs and 6006 CSDs in Canada). The number of CTs by CMA/CA is  ~J provided in the 1991 Digital Boundary File User Guide.(# XThe set of lakes included with the CSD, CD and PR/TERR cartographic files is not complete, but rather represents 10 major lakes appropriate for small scale thematic mapping. The lakes have no names attached to them in the DCFs, but represent Smallwood Reservoir in Labrador, Bras d'Or Lake in Nova Scotia, Cedar Lake, Lake Winnipeg, Lake Winnipegosis and Lake Manitoba in Manitoba, Reindeer Lake in Manitoba and Saskatchewan, Lake Athabasca in Saskatchewan and Alberta, and Great Slave Lake and Great Bear Lake in the Northwest Territories.(# XThe set of lakes included with the CT cartographic files is more complete for larger scale mapping appropriate at the CT level.(# $0*&&Ԍ H  X4.6X` ` $Other Considerations (#` X` hp x (#%'0*,.8135@8:@0CEG8JLN@QSUHXXX Toll free service:`"%18005637828 Local Calls:`2"%(403) 4953027 Fax Number:`2"%(403) 49553187&/++$~%,-07ԯ aEp'  Telecommunications Device for the Hearing Impaired 18003637629 Toll Free Order Only Line (Canada and United States) 18002676677 */++Ԍ H  XX  #J2PQ zP# ęh 7.3Additional References and Services (# In addition to the Regional Reference Centres and depository libraries, Statistics Canada publications may be ordered through your local bookstore or subscription agent. Contact the nearest Regional Reference Centre for a list of Canadian outlets available, or consult the 1991 Census Catalogue (Catalogue No. 92-302E). Secondary distributors offer data access and analytical support through a variety of consulting and computer-based services not available at Statistics Canada. The names and addresses of licensed distributors may be obtained from any Regional Reference Centre. Statistics Canada provides digital geographic products which allow computer manipulation of geographic data. A customized retrieval service is available for users who wish to define their own geographic area of study. A variety of data retrieval files and services provide flexibility in selecting a geographic base. A complete description of available digital files and services is documented in the 1991 Census Catalogue (Catalogue No. 92-302E ). Information concerning Census of agriculture products and services may be referenced in the 1991 Census of Agriculture Products and Services publication, Catalogue No. 92-303, or by calling toll free 1-800-465-1991. Users with special data requirements may request post-census survey services. Data are made available on microcomputer diskettes for use with spreadsheet software, or on paper output. For additional information, please contact the nearest Regional Reference Centre. The Dissemination Division is responsible for CANSIM, Statistics Canada's computerized database network and information retrieval service. Users are provided with access to current and historical statistics in various forms including specialized data manipulation and analysis packages, graphics facilities and a bibliographic search service. For more information about CANSIM, contact any Regional Reference Centre. h"P` ` (X 2(# 8,o(o(  H  SUPPLEMENT 1: EA LINKAGE ERRORS ON THE 1991 GEOGRAPHIC ATTRIBUTE DATA BASE This supplement documents the errors found on the Geographic Attribute Data Base (GADB). These errors have been identified up to the time of releasing this User Guide or other GEO products that use GADB as a source file. The Geographic Attribute Data Base is a set of relational files that contain a number of attributes for standard geographic areas (such as names, codes, land area, population and dwelling counts) and linkages between the areas. In particular, GADB defines not only EA linkages to higher level standard geographic areas, but also linkages between all standard geographic areas. GADB is also linked to other census operational data bases. These linkages are used for various processes, such as creating digital boundary files and aggregating EAlevel census data. The data bases were "frozen" in March 1992, just prior to the first release of census data. Errors identified after that date cannot be corrected on the data bases without losing the integrity between the many interrelated data bases. Consequently, errors in 1991 Census data resulting from EA linkage errors are documented and released as "Errata" with the appropriate census publications. The supplement indicates the linkage errors between the various geographic areas, the effective date(s), the correct linkage and population/dwelling counts, and whether the errors were corrected on the Digital  ~J Boundary Files.1 The following tables are included: X `"$'h)+.p02 5x79(<>@0CEG8JLN@QSUHXX` XX` XH"Table 1. Linkage Errors Between EAs and CDs.(# H"Table 2. Linkage Errors Between EAs and CCSs.(# H"Table 3. Linkage Errors Between EAs and CSDs.(# H"Table 4. Linkage Errors Between EAs and CTs/PCTs.(# H"Table 5. Linkage Errors Between EAs and UAs.(# H"Table 6. Effect of EACSD Linkage Errors on CSD Population and Dwelling Counts(# This supplement will be updated as additional errors are identified. _______________________________________________________________  ~J$ 1 If errors were corrected on the Digital Boundary Files, there may be a discrepancy between these files and a boundary file that users create by aggregating EAs and linking EA codes using the Geographic Attribute File or using other Statistics Canada products created from the Geographic Attribute Data Base. ',o(o(Ԍ P  #\D4P,GzP# 3'X` h3'StandardScriptHPIIIP1.PRSx  3'3'StandardScriptHPIIIP1.PRSx  =eX Table 1. Linkage Errors Between EAs and CDs (as of November 4, 1992)  #HD4PyP# c ddx !ddx= c    #|M2PkCP#PROVFEDEA  PROVCD Linkage in GADB  Correct PROVCD Linkage Q Corrected on Digital Boundary FilesQ <s1991 EA Population <sand Dwelling Counts        E E mPopulationE Occupied Private Dwellings   .    61 001 209}  61 08}  61 06} ?[YES} r0}  . ^  O      ^  } #\D4P,GzP#   P< Table 2. Linkage Errors Between EAs and CCSs (as of December 22, 1992) 3'3'StandardScriptHPIIIP1.PRSx  3'3'StandardScriptHPIIIP1.PRSx  =eX #HD4PyP#""""""""" h !ddx= Addx || | h ^  } PROVFEDEAr PROVCDCCS Linkage in GADB Correct PROVCDCCS Linkage 1991 EA Population Count   f   N   35 017 413+  35 20 014+  35 20 008+ su253N .   35 017 465Y  35 20 014Y  35 20 008Y su245. . +  35 017 466  35 20 014  35 20 008 su208. . Y  48 016 272  48 11 061  48 11 052 {t 0. ^    61 001 209  61 08 098  61 06 097 p 0 ^  ,o(o(  P  #\D4P,GzP#  Table 3. Linkage Errors Between EAs and CSDs (as of December 22, 1992)   #HD4PyP# h Addx || | addx h "^     "  PROVFEDEA   PROVCDCSD Linkage in GADB Correct PROVCDCSD Linkage Corrected on Digital Boundary Files 1991 EA Population and Dwelling Counts      } }    Population Occupied Private Dwellings    .    24 047 163[  24 66 055[  24 66 025[ i NO[  0[  0. . -  24 047 164  24 66 055  24 66 025 i NO  171  57. . [  24 047 165  24 66 055  24 66 025 i NO  0  0. .   24 047 209  24 66 060  24 66 055 i NO  176  126. .    24 047 210  24 66 060  24 66 055 i NO  196  124. .    24 047 211A  24 66 060A  24 66 055A i NOA  328A  219. .    24 047 212o  24 66 060o  24 66 055o i NOo  379o  248. . A   24 047 213  24 66 060  24 66 055 i NO  347  232. . o  35 017 413  35 20 014  35 20 008 eh YES  253  132. .   35 017 465  35 20 014  35 20 008 {iYES  245  128. .   35 017 466'  35 20 014'  35 20 008' i NO'  208'  0. .   47 001 274U  47 12 042U  47 12 046U i NOU  16U  5. . '  47 001 275  47 12 042  47 12 046 i NO  15  3. . U  48 016 272  48 11 061  48 11 052 {iYES  0  0. .   59 020 360  59 15 043  59 15 063 {iYES  4  2. .   59 024 165   59 17 045   59 17 047  {iYES   0   0. ^    61 001 209k  61 08 098k  61 06 097k {iYESk  0k  0^     P #\D4P,GzP# Table 4. Linkage Errors Between EAs and CTs/PCTs (as of December 22, 1992) #|M2PkCP# | addx ddxF Q | *^       * #|M2PkCP#PROVFEDEA  Linkage in GADB  Correct Linkage Corrected on Digital Boundary Files 1991 EA Population and Dwelling Counts*   z  F* X  d ,PCMA/PCA ) d /or a d -CMA/CA!  +=CT Name! MPCMA/PCA Por NCMA/CA! "_CT Name! !  Population ! Occupied Private Dwellings"z  N :"  24 015 305 #  505#  841.02 #  505 #  841.01 # m NO # ;812# !c"256N . !  24 065 1270$  4620$  510.000$  4620$  415.010$ UqYES0$ Y 00$ "c" 0. . #  24 065 128^%  462^%  510.00^%  462^%  415.01^% UqYES^% Y 0^% "c" 0. . 0$  35 013 274&  535&  260.03&  535&  263.01& n YES & ;535& !c"326. ^  ^%  48 026 023H$'  837'  165.00'  837'  166.00' UqYES'  541' !c"116',o(o(^  &ݙ  P  X  #\D4P,GzP#Table 5. Linkage Errors Between EAs and UAs (as of December 22, 1992)  | ddxF Q ddxWx | ^  &  dB  #|M2PkCP# PROVFEDEA UA Code in GADBQ Correct UA LinkageQ Corrected on Digital Boundary Files 1991 EA Population and Dwelling Counts  z W   E E  nPopulation Occupied Private Dwellings z N K   48 022 070 J 01258 ,E0000  NO s4 0N ^    48 022 071q J 01258q ,E0000q  NOq r 0q 0^    P #\D4P,GzP#   Table 6. Effect of EACSD Linkage Errors on CSD Population and Dwelling  Counts (as of December 22, 1992)  P     r ddxWx ddx 0-% r ^  $    dBz #|M2PkCP#PROVCDCSDP CSD Name and TypeP 1991 Population and Dwelling Counts Incorrect Count Correct Count Difference$  .    24 66 025$ Montreal, V$ Population$  1,017,666$  1,017,837$  171.    b b Occupied Private Dwellings  464,880  464,937  57  . $  24 66 0556 C=teSaintLuc, C6 Population6  28,7006  29,9556  1,255.    t t Occupied Private Dwellings  11,672  12,564  892  . 6  24 66 060H Hamstead, VH PopulationH  8,645H  7,219H  (1426).      Occupied Private Dwellings,  3,498,  2,549,  (949)  . H  35 20 014Z York, CZ PopulationZ  140,525Z  139,819Z  (706).   ,   Occupied Private Dwellings>  56,335>  56,075>  (260)  . Z  35 20 008l North York, Cl Populationl  562,564l  563,270l  706.   >   Occupied Private DwellingsP  204,067P  204,327P  260  . l  47 12 042~ Biggar No. 347, RM~ Population~  1,086~  1,055~  (31).   P   Occupied Private Dwellingsb!  298b!  290b!  (8)  . ~  47 12 046" Biggar, T" Population"  2,322"  2,353"  31.   b! # # Occupied Private Dwellingst$  967t$  975t$  8   . "   48 11 061% Edmonton, C % Population% Ek No Impact ".  t$" ' ' Occupied Private Dwellings' EtNo Impact %',o(o(  P #\D4P,GzP#   Table 6. Effect of EACSD Linkage Errors on CSD Population and Dwelling Counts (as of December 22, 1992) Cont'd     r ddx 0-% ddx3% r   $  %   dB+ #|M2PkCP#PROVCDCSD CSD Name and Type 1991 Population and Dwelling Counts Incorrect Count Correct Count Difference $      48 11 052 Strathcona County No. 20, CM{ Population{ sNo Impact"  "  O  O  Occupied Private DwellingsO  sNo Impact  . {   59 15 043} Port Moody, C} Population}  17,712}  17,708}  (4).  O    Occupied Private DwellingsQ   6,201Q   6,199Q   (2)  }   59 15 063 Greater Vancouver, Subd. B, SRD% Population%  2,459%  2,463%  4  Q  S S Occupied Private dwellings  963  965  2  . %   59 17 045' Capital Subd. B, SRD' Population' sNo Impact".  " U U Occupied Private Dwellings sNo Impact" . '"  59 17 047) View Royal, T) Population) sNo Impact".  " W W Occupied Private Dwellings sNo Impact"  )"  61 06 097+ Fort Smith, Unorganized, UNO Population sNo Impact"  "   Occupied Private Dwellings sNo Impact"  "  61 08 098 Kitikmeot Unorganized, UNOy Populationy sNo Impact"  "   Occupied Private Dwellings} sNo Impact y