The City of Kitchener assumes no responsibility for the accuracy of the provided data. Any use of this information is done so at the users risk. Good survey practices must be applied when utilizing this information. The City of Kitchener and its partners have created this data for information purposes on an as-is and as available basis and is under no circumstances a substitute for a Legal Survey. The City does not make any representations or warranty, express or implied, concerning the accuracy, quality, likely results, or reliability of the use of the data. The City of Kitchener assumes no responsibility for any errors and is not liable for any damages of any kind resulting from the use of, or reliance on, the information and material contained in this layer. All information should be verified independently before being used or relied on. Users are encouraged to contact the City of Kitchener to ensure the accuracy of the information provided by Kitchener.
Source and Contraints
Source Map Label:
Zoning: Development & Technical Services - Planning (Current to date of printing)
History:
Original information was maintained on mylar 8 1/2 x 11 sheets on a bi-annual basis by mapping staff in the Planning and Development Department. In 1998 an initiative began to digitize the information into a GIS layer utilizing microstation. In 2000 the initial digital conversion was completed and a review process began to ensure the information was transcribed properly. A number of issues were discovered which ranged from simple digitizing errors to administrative errors in the original mylar maintenance or transcription of the bylaw itself. In 2001 the zone layer was converted into ESRI SHP format and ultimately moved in to the ESRI SDE environment in the Corporate Database. In 2001 a comprehensive review of the zone layer was conducted by zoning staff which resulted in a considerable number of edits to the zoning bylaw text as the schedule number references have changed between the mylar sheets and the digital version. Administrative errors were also corrected in the bylaw text. In 2002, mapping staff undertook the task of updating the zone layer to current state as well as make corrections as identified by zoning staff.
Original Source:
CS - Zoning
Original Source Process:
Zone Change Application - Planning & Development Services
Maintenance:
ArcMap Editor of the ESRI ArcGIS suite is the tool utilized to maintain both the polygons and the associated attributes. At this time, the environment is not customized and the vanilla tools from ESRI are utilized. Later in 2002 it is expected that a maintenance tool will be developed to assist in maintaining the attributes and related tables based on automated spatial joins.
Current Info Source:
The zone layer is maintained based on zone change applications processed by the Planning Division. Prior to 2002 this process was managed through a paper system and the resulting changes in the zone schedules were applied to the mylar schedules. As of 2003, changes are made directly to the digital layers as approved by zoning committee. Mylars are no longer maintained.
Outstanding Issues:
Update Frequency:
ON DEMAND
Data Fields & Domain Information
Zoning
Column Name
Alias
Data Type
Comments
Domain Name
Default value
Domain Values
OBJECTID
OBJECTID
NUMBER
ESRI system maintained integer field used to uniquely identify rows in tables in a geodatabase. Note that OBJECTIID values change upon export or import of the data and should not be used as a primary field for searching or identifying records.
ZONE_TYPE
Zone Type
VARCHAR2
ZoneType
Agricultural Zone; Business Park Zone; Commercial Residential Zone; Commercial Zone; Existing Use Zone; Industrial Zone; Mixed Use Corridor Zone; Park Zone; Residential Zone; Retail Commercial Zone ...See GIS for a complete list...
ZONE_CLASS
Zone Class
VARCHAR2
ZoneClass
AGR-1 Prime Agriculture; By-Law 4830; By-Law 878A; COM-1 Local Commercial; COM-2 General Commercial; COM-3 Arterial Commercial; COM-4 Commercial Campus; MIX-1 Mixed Use One; MIX-2 Mixed Use Two; MIX-3 Mixed Use Three ...See GIS for a complete list...
EFFECTIVE_DATE
Effective Date
DATE
END_DATE
End Date
DATE
BYLAW_NO
Bylaw No
VARCHAR2
CENTROID_X
Centroid X
NUMBER
CENTROID_Y
Centroid Y
NUMBER
MAP_LABEL
Map Label
VARCHAR2
PROVISION1
Provision1
VARCHAR2
PROVISION2
Provision2
VARCHAR2
PROVISION3
Provision3
VARCHAR2
PROVISION4
Provision4
VARCHAR2
PROVISION5
Provision5
VARCHAR2
LAST_UPDATE_DATE
Last Update Date
DATE
LAST_UPDATE_BY
Last Update By
VARCHAR2
CREATE_DATE
Create Date
DATE
Database maintained field. Updates to the current data/time. Update takes place when the feature is created.
PROVISION6
Provision6
VARCHAR2
PROPERTY_DETAIL
Property Detail
VARCHAR2
NOTE
Note
VARCHAR2
Descriptive text outlining any problems or to highlight special characteristics of the feature.
ZONE_CLASS_DOCUMENT
Zone Class Document
VARCHAR2
PROVISION1_DOCUMENT
Provision1 Document
VARCHAR2
PROVISION2_DOCUMENT
Provision2 Document
VARCHAR2
PROVISION3_DOCUMENT
Provision3 Document
VARCHAR2
PROVISION4_DOCUMENT
Provision4 Document
VARCHAR2
PROVISION5_DOCUMENT
Provision5 Document
VARCHAR2
GENERALDOCUMENT1
Generaldocument1
VARCHAR2
GENERALDOCUMENT2
Generaldocument2
VARCHAR2
GENERALDOCUMENT3
Generaldocument3
VARCHAR2
APPLICATION_NO
Application No
VARCHAR2
STATUS
Status
VARCHAR2
Indicates the status of feature. A pick list is used for this field - contact GIS for pick list values.
ZoneStatus
APPLICATION
APPLICATION; APPROVED; HISTORIC; PASSED - NOT YET APPROVED; UNDER APPEAL
PROVISION6_DOCUMENT
Provision6 Document
VARCHAR2
ZONEID
Zoneid
NUMBER
Database maintained field that permanently assigns a unique value for each record. This ID value should be the one referred to when identifying a record.
SHAPE
Shape
ST_GEOMETRY
ESRI system maintained field. Stores the geometry type and geometry of the feature.
UPDATE_BY
Update By
VARCHAR2
Database maintained field. Updates to the user name that most recently updated either an attribute or the geometry of the feature. Update takes place when the feature is created and/or changed.
UPDATE_DATE
Update Date
DATE
Database maintained field. Updates to the current data/time when an attribute or the geometry of the feature is changed. Update takes place when the feature is created and/or changed.
