20240411
21080400
1.0
FGDC CSDGM Metadata
FALSE
ROADS
530238.830325
542328.683625
4808863.369729
4819865.837029
1
002
Projected
GCS_North_American_1983
Linear Unit: Meter (1.000000)
NAD_1983_UTM_Zone_17N
<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.8'><WKT>PROJCS["NAD_1983_UTM_Zone_17N",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER["False_Easting",500000.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-81.0],PARAMETER["Scale_Factor",0.9996],PARAMETER["Latitude_Of_Origin",0.0],UNIT["Meter",1.0],AUTHORITY["EPSG",26917]],VERTCS["NAD_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PARAMETER["Vertical_Shift",0.0],PARAMETER["Direction",1.0],UNIT["Meter",1.0],AUTHORITY["Esri",115702]]</WKT><XOrigin>-5120899.9999752901</XOrigin><YOrigin>-9998099.9999713898</YOrigin><XYScale>10000</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.00020000000000000001</XYTolerance><ZTolerance>7.4976715938000001e-05</ZTolerance><MTolerance>7.4976715938000001e-05</MTolerance><HighPrecision>true</HighPrecision><WKID>26917</WKID><LatestWKID>26917</LatestWKID><VCSWKID>115702</VCSWKID><LatestVCSWKID>115702</LatestVCSWKID></ProjectedCoordinateSystem>
20250117
14020100
20250117
14020100
500000
5000
FGDC
Base_Data
Chris Jacob
City of Waterloo
GIS Analyst
Chris Jacob
100 Regina Street South, PO Box 337 Stn Waterloo
Waterloo
ON
N2J 4A8
chris.jacob@waterloo.ca
CA
519.747.8550
10.6.1
Feature Class
ROADS
2010-07-12T00:00:00
Roads is a Single-Line Street Network representing centrelines of roads within the City of Waterloo. It includes both currently built and proposed (draft) road segments. It includes official legal road names and address ranges on each segment, as well as attributes used for various mapping projects and business processes. It is the definitive source for municipal roads data in the City of Waterloo.
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This fundamental base data is used in many business processes at the City; generally for all base mapping and cartographic production, and applications including emergency services provision and fire dispatch, address coding (locators), a public road closures application, the Official Plan mapping, Operations maintenance activities, the Road Patrol application, Maximo, etc. It is coded with many attributes designed to support these uses, details of which are found in the "Entity Attribute" section of this metadata.</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN>Updates to this data are sent to </SPAN><SPAN>Kitchener F</SPAN><SPAN>ire Dispatch</SPAN><SPAN /><SPAN>(under contract for Dispatch services)</SPAN><SPAN>, </SPAN><SPAN>and the Region of Waterloo</SPAN><SPAN>,</SPAN><SPAN /><SPAN>for inclusion in their road networks, and is </SPAN><SPAN>also </SPAN><SPAN>shared further with other agencies</SPAN><SPAN>, sometimes </SPAN><SPAN>via the Region.</SPAN></P><P><SPAN>Road segments represented in this data include all public access roads within the City of Waterloo. Segments which represent access lanes within City parks and facilities are also included. Some private roads are included where they have had "public" road names assigned, and have had addresses assigned on them (notably: developments at Boardwalk, Barrelyards, </SPAN><SPAN>and </SPAN><SPAN>Bearinger (north of Northfield))</SPAN><SPAN>. </SPAN><SPAN>This practice should be discouraged in future, though it seems to be at the discretion of Building Standards to grant these developer requests.</SPAN></P><P><SPAN>Address range values are based on actual addresses assigned, not theoretical ranges.</SPAN></P><P><SPAN>A version of this</SPAN><SPAN>is published as Open Data </SPAN><SPAN>at</SPAN><SPAN>https://data.waterloo.ca</SPAN><SPAN>/datasets/roads.</SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
roads
SLSN
SLRN
network
transportation
location
streets
City of Waterloo GIS
roads, SLSN, SLRN, network, transportation, location, streets
Chris Jacob
City of Waterloo
GIS Manager
Chris Jacob
Version 6.2 (Build 9200) ; Esri ArcGIS 10.9.1.28388
1
-80.626381
-80.476154
43.531123
43.431469
This is the official version of the City roads GIS data.
Process steps below give high-level descriptions of the creation and maintenance of the data.
Linework created by digitizing parallel to property boundaries and down the centre of road allowances. Started with major roads as single arcs along their entire length, then intersected them with each other. Added minor roads and intersected them as required. Goal was smooth and cartographically pleasing linework. Included the creation of smooth curves for cul-de-sacs. Developed rules for segmentation and coding as appropriate, and based on application requirements and other existing standards (e.g. Bell 9-1-1 rules and Fire Dispatch requirements). Referred to 2009 12cm orthophotography for reference if in doubt as to road alignment within the allowance, and followed the actual pavement.
Process software and version: ArcGIS Desktop 9.3.1
Process date: 2010/07/12
2010-07-12T00:00:00
Chris Jacob
City of Waterloo
GIS Analyst
Defined attributes to match those in the 'original' WSLSN data that originally came from the Region, and had been maintained at the City for several years. Transferred values from the old to the new linework using the ArcGIS Attribute Transfer Tool.
Process software and version: ArcGIS Desktop 9.3.1
Process date: 2010/07/15
2010-07-15T00:00:00
Added attributes for new coding to reduce maintenance of other datasets with duplicated linework and simply different attributes. (e.g. official plan coding, main roads coding, one way coding, cul-de-sac coding) Completed coding based on background information from appropriate sources (e.g. Development Services for OP coding, earlier separate dataset for main roads coding, listing of one-way streets from Public Works, cul-de-sac spreadsheet from Operations) Visually verified coding consistency by using vivid symbolization and comparison with other data sources.
Process software and version: ArcGIS Desktop 9.3.1
Process date: 2010/07/16
2010-07-16T00:00:00
Renamed and rearranged attributes as per notes from Daniela and Todd. Created new attributes with specified names and data types, transferred values as appropriate. Used the Reorder Fields tool from ArcScripts to put them in a logical order. Deleted old superseded attributes.
Process software and version: ArcGIS Desktop 9.3.1
Process date: 2010/07/27
2010-07-27T00:00:00
Added many "side" cul-de-sacs to cartographically represent situations where the road surface was widened and sometimes had an island. These side segments don't split the main road segment, and don't have address ranges coded against them. Addresses continue to be assigned against and recorded in ranges on the road segment that the side is adjacent to. They could optionally be omitted from data sent to fire dispatch. They are coded with a code from Operations maintenance regarding the island. Much other information is maintained against this Operations code value in a spreadsheet maintained by PWS Operations (Parks) staff.
Process software and version: ArcGIS Desktop 9.3.1
Process date: 2010/07/29
2010-07-29T00:00:00
Updated cul-de-sac segments with street_name, ID, and range-related attributes. Improved the appearance of linework for some cul-de-sacs. Decided that if a cul-de-sac style segment has a distinct name and address ranges against it, it should be coded with cul_de_sac = 'N' so it will always draw, even if most are excluded.
Process software and version: ArcMap 9.3.1 sp2
Process date: 2010/08/25
2010-08-25T00:00:00
Metadata imported.
Source used: WSLSN_20101013.xml
Process
date: 20110510 at time 08472500
2011-05-10T00:00:00
Updated / checked for consistency STREET_NAME, FROM_STREET and TO_STREET attributes based on the STREET NAMES MASTER table.
Process software and version: ArcInfo 9.3.1
Process date: 2011/05/11
2011-05-11T00:00:00
Metadata imported.
Source used: WSLSN_20110816.xml
Process
date: 20110816 at time 09243200
2011-08-16T00:00:00
Transition from WSLSN_NEW to ROADS.
Added attributes for use in supporting the Region's data model, and exporting data to them. Dealt with conflicts where noted.
Review of attribute contents, calculations, comparisons, and corrections continued through to July 2013, then more again in March 2014, then March 2015.
Details of some changes and decisions are in
2013-04-15T00:00:00
Reviewed for attribute consistency (in concert with Addresses) by FME tools & rules written by Warren Davison.
Corrections made as appropriate, for range overlaps, etc.
2018-11-05T00:00:00
Warren Davison
City of Waterloo
GIS Analyst
EPSG
6.11(3.0.1)
ROADS
Feature Class
3523
Arcs / lines representing roads in the City of Waterloo.
City of Waterloo
OBJECTID
OBJECTID
OID
4
10
0
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
Shape
Shape
Geometry
4
0
0
Feature geometry.
Esri
Coordinates defining the features.
SEGMENT_ID
SEGMENT_ID
Integer
4
10
0
unique ID value for the road segment; unique over time (never re-used); changes if the geometry is modified; new CoW values are in the range 80000+ as agreed by all local municipalities (in ~2006?)
City of Waterloo GIS
SEQUENCE
SEQUENCE
Double
8
38
8
sequential number of the segment along the series of segments with the same name
City of Waterloo GIS
STREET_NAME
STREET_NAME
String
50
0
0
street name text from STREET_NAME_MASTER
City of Waterloo GIS
STREET_NAME_ID
STREET_NAME_ID
Integer
4
10
0
ID value of the street name from STREET_NAME_MASTER
City of Waterloo GIS
FROM_LEFT
FROM_LEFT
SmallInteger
2
5
0
lowest actual address number on the left side
City of Waterloo GIS
TO_LEFT
TO_LEFT
SmallInteger
2
5
0
highest actual address number on the left side
City of Waterloo GIS
FROM_RIGHT
FROM_RIGHT
SmallInteger
2
5
0
lowest actual address number on the right side
City of Waterloo GIS
LOW__
_LOW
SmallInteger
2
5
0
lowest actual address number on the segment (both sides)
City of Waterloo GIS
HIGH__
_HIGH
SmallInteger
2
5
0
highest actual address number on the segment (both sides)
City of Waterloo GIS
RANGE__
_RANGE
String
15
0
0
overall range of actual address numbers on the segment
City of Waterloo GIS
TO_RIGHT
TO_RIGHT
SmallInteger
2
5
0
highest actual address number on the right side
City of Waterloo GIS
LEFT_PARITY
LEFT_PARITY
String
1
0
0
parity (even, odd, mixed, unknown, zero) of address numbers on the left side of the road segment
City of Waterloo GIS
ROAD_ADDRESS_PARITY
City of Waterloo GIS
RIGHT_PARITY
RIGHT_PARITY
String
1
0
0
parity (even, odd, mixed, unknown, zero) of address numbers on the right side of the road segment
City of Waterloo GIS
ROAD_ADDRESS_PARITY
City of Waterloo GIS
LEFT_MUNICIPALITY
LEFT_MUNICIPALITY
String
30
0
0
City of Waterloo GIS
municipality name to the left side of the road segment
Road_Municipality
City of Waterloo GIS
CRISYS_STREET_NAMES
_ALT_STREET_NAMES
String
50
0
0
City of Waterloo GIS
Alternate names for the street (e.g. Regional Rd 86) as used to ship to Crisys
RIGHT_MUNICIPALITY
RIGHT_MUNICIPALITY
String
30
0
0
City of Waterloo GIS
municipality name to the right side of the road segment
Road_Municipality
City of Waterloo GIS
FROM_STREET
FROM_STREET
String
50
0
0
City of Waterloo GIS
cross street name at the beginning of the segment, from STREET_NAME_MASTER
FROM_STREET_ID
FROM_STREET_ID
Integer
4
10
0
City of Waterloo GIS
cross street name ID at the beginning of the segment, from STREET_NAME_MASTER
TO_STREET
TO_STREET
String
50
0
0
City of Waterloo GIS
cross street name at the end of the segment, from STREET_NAME_MASTER
TO_STREET_ID
TO_STREET_ID
Integer
4
10
0
City of Waterloo GIS
cross street name ID at the end of the segment, from STREET_NAME_MASTER
LIFECYCLE_STATUS
LIFECYCLE_STATUS
String
20
0
0
City of Waterloo GIS
The lifecycle status of the road segment, similar to how the attribute is used for other infrastructure This data is directly translated into the Region's data model for upload.
(Active, Proposed)
_LifeStatus
City of Waterloo GIS
STATUS_PHYSICAL
STATUS_PHYSICAL
String
20
0
0
City of Waterloo GIS
physical status of the road segment
(BUILT, PLANNED, UNDER CONSTRUCTION, NEVER BUILT)
Road_Status_Physical
City of Waterloo GIS
STATUS_PLANNING
STATUS_PLANNING
String
20
0
0
City of Waterloo GIS
planning or legal status of the road segment
(PLANNED, DRAFT APPROVED, REGISTERED, NA (last one for private access lanes))
Road_Status_Planning
City of Waterloo GIS
STREET_TYPE
STREET_TYPE
String
12
0
0
City of Waterloo GIS
description of function / construction of road segment
STREET_CLASS
STREET_CLASS
String
20
0
0
City of Waterloo GIS
class of road segment; roughly corresponds to the Region's carto_class; could be superseded by it?
Also roughly equivalent to Road Matrix Functional Class - compare?
Also compare with the Transportation Master Plan.
Also compare with
CARTO_CLASS
CARTO_CLASS
String
30
0
0
City of Waterloo GIS
The cartographic (drawing) class of the road segment.
This is aimed directly at the Region's data model and uses values defined by the Region.
*********We should choose to maintain one or the other, and feed data to the Region from it.
Road_CartoClass
Region of Waterloo GIS
OWNED_BY
OWNED_BY
String
30
0
0
City of Waterloo GIS
The owner of the street segment (i.e. ~ same as property on which it sits)
This is aimed directly at the Region's data model and uses values defined by the Region.
_OwnedBy
Region of Waterloo GIS
MANAGED_BY
MANAGED_BY
String
30
0
0
City of Waterloo GIS
Maintainer of the road segment, from a road maintenance point of view
This is aimed directly at the Region's data model and uses values defined by the Region.
_OwnedBy
Region of Waterloo GIS
MAIN_ROAD
MAIN_ROAD
String
1
0
0
City of Waterloo GIS
Boolean value - "main" roads draw at a City-wide scale, and may use different symbols than those which aren't main
Feeds into the Region's data model as "show at regional scale"
boolean_text_single
City of Waterloo GIS
FLOW_DIRECTION
FLOW_DIRECTION
String
6
0
0
City of Waterloo GIS
Directions in which vehicular travel is allowed (i.e. coding for one-way streets)
Traffic is allowed in one of the directions "FromTo", "ToFrom", "TwoWay", compared to the direction of digitising.
This data is maintained in GIS, and values in Road Matrix (RMXP) are synchronized by manual edits, prompted by a QA view that highlights differences.
Roads_FlowDirection
City of Waterloo GIS
SURFACE_TYPE
SURFACE_TYPE
String
10
0
0
City of Waterloo GIS
Coding for surface type
(Paved, Not Paved)
This is aimed directly at the Region's data model and uses values defined by the Region.
Road_SurfaceClass
Region of Waterloo GIS
NUMBER_LANES
NUMBER_LANES
SmallInteger
2
5
0
City of Waterloo GIS
Number of travelled lanes.
This data is maintained in Road Matrix (RMXP), and values in GIS are synchronized by manual edits, prompted by a QA view that highlights differences.
Road_Lanes
Region of Waterloo GIS
ROAD_WIDTH
ROAD_WIDTH
Double
8
38
8
City of Waterloo GIS
The average width of road pavement for the segment, in metres.
Not currently coded or maintained.
SPEED_ZONE
SPEED_ZONE
SmallInteger
2
5
0
City of Waterloo GIS
Speed limit for the segment.
Where there's a portion at 40 km/h (e.g. in a school zone), the segment should be coded as 40.
This data was initially populated based on values from the Road Matrix database.
This data is maintained in GIS, and is synchronized to values in Road Matrix (RMXP) by manual edits in that application, prompted by a QA view that highlights differences.
Road_SpeedZones
Region of Waterloo GIS
REGIONAL_ROAD_NUMBER
REGIONAL_ROAD_NUMBER
SmallInteger
2
5
0
City of Waterloo GIS
Regional road number, wherever one is applicable
PUBLIC_ACCESS
PUBLIC_ACCESS
String
60
0
0
City of Waterloo GIS
Is the road segment publicly accessible or not.
This is aimed directly at the Region's data model and uses values defined by the Region.
Not currently coded or maintained by City of Waterloo.
Road_PublicAccess
Region of Waterloo GIS
STREET_INDEX
STREET_INDEX
String
5
0
0
City of Waterloo GIS
Primary index grid sheet number for the road segment
RUNCARD_ID
RUNCARD_ID
SmallInteger
2
5
0
City of Waterloo GIS
Primary runcard index sheet grid for the road segment
DEMAND_ZONE
DEMAND_ZONE
SmallInteger
2
5
0
City of Waterloo GIS
Primary Fire demand zone for the segment
TANKER_RQR
TANKER_RQR
String
1
0
0
City of Waterloo GIS
Boolean, whether a fire tanker is required during response
boolean_text_single
City of Waterloo GIS
FIRST
FIRST
SmallInteger
2
5
0
City of Waterloo GIS
Fire station that responds first
SECOND
SECOND
SmallInteger
2
5
0
City of Waterloo GIS
Fire station that responds second
THIRD
THIRD
SmallInteger
2
5
0
City of Waterloo GIS
Fire station that responds third
FOURTH
FOURTH
SmallInteger
2
5
0
City of Waterloo GIS
Fire station that responds fourth
RP_CLASS
RP_CLASS
SmallInteger
2
5
0
City of Waterloo GIS
Road Patrol Class. Could also be called MTO Class or Maintenance Class. Possible values from 1-8 indicating the class of road for patrolling frequency.
0
8
RP_ROUTE_CODE
RP_ROUTE_CODE
SmallInteger
2
5
0
City of Waterloo GIS
Road Patrol route number.
CUL_DE_SAC
CUL_DE_SAC
String
1
0
0
City of Waterloo GIS
Code indicating whether the segment represents the "turning circle" portion of a cul-de-sac. These can be excluded from catrography at small scales. They are excluded from some other things, such as Asset Management (TCA) reporting, where their length is added to the segment that precedes them.
Values include: N = not a cul-de-sac arc; Y = a cul-de-sac arc; S = a 'side' cul-de-sac representing a wider section of pavement (these are included for cartographic purposes, but don't split the arc that they adjoin, and have no addresses coded on them because the addressing pattern around them is continuous along the main segment.)
Road_CulDeSac
City of Waterloo GIS
CUL_DE_SAC_ISLAND
CUL_DE_SAC_ISLAND
String
1
0
0
City of Waterloo GIS
Indicates whether there's an island in the middle of a cul-de-sac segment. This is used by operations staff to indicate where maintenance activities have to occur. It can also have implications for pavement area calculations, and planning of plowing and winter control.
Only coded if CUL_DE_SAC = 'Y'.
boolean_text_single
City of Waterloo GIS
CUL_DE_SAC_GRASS_CODE
CUL_DE_SAC_GRASS_CODE
String
6
0
0
City of Waterloo GIS
Grass mowing code as specified and used by operations staff to plan grass mowing activities.
NOTES
NOTES
String
50
0
0
City of Waterloo GIS
Free text notes on the road segment. Currently used for FME-based Data Review, in order to record exceptions to the rules.
CREATE_DATE
CREATE_DATE
Date
8
0
0
City of Waterloo GIS
Date the feature was created.
Maintained through ArcGIS editor tracking.
CREATE_USER
CREATE_USER
String
16
0
0
City of Waterloo GIS
Username that created the feature. Specifically which user was connected to the database during the edit session.
Maintained through ArcGIS editor tracking.
UPDATE_DATE
UPDATE_DATE
Date
8
0
0
City of Waterloo GIS
Date the feature was last updated.
Maintained through ArcGIS editor tracking.
UPDATE_USER
UPDATE_USER
String
16
0
0
City of Waterloo GIS
Username that last updated the feature. Specifically which user was connected to the database during the edit session.
Maintained through ArcGIS editor tracking.
ROW_ID
ROW_ID
String
20
0
0
City of Waterloo GIS
Right-of-Way ID.
Used (historically) by Infrastructure group to associate different types of infrastructure.
May be superseded by Corridors, one day.
The ROW_ID is also used in traffic collisions data by the Transportation group. This should be reviewed.
MXLOCATION
MXLOCATION
String
12
0
0
City of Waterloo GIS
Deprecated code for integration with Maximo Spatial. No longer used.
MXSITEID
MXSITEID
String
8
0
0
Deprecated code for integration with Maximo Spatial. No longer used.
City of Waterloo GIS
MXCREATIONSTATE
MXCREATIONSTATE
SmallInteger
2
5
0
City of Waterloo GIS
Deprecated code for integration with Maximo Spatial. No longer used.
ROWSTAMP
ROWSTAMP
String
40
0
0
Deprecated code for integration with Maximo Spatial. No longer used.
City of Waterloo GIS
GLOBAL_ID
GLOBAL_ID
GUID
38
0
0
City of Waterloo GIS
Not used.
FIRE_ROUTE
FIRE_ROUTE
String
10
0
0
MEDIAN
MEDIAN
String
3
0
0
AADT
AADT
Integer
4
10
0
AADT_DATE
AADT_DATE
Date
8
0
0
SCHOOL_ZONE
SCHOOL_ZONE
String
10
0
0
AADT_SOURCE
AADT_SOURCE
String
4
0
0
SHAPE.LEN
SHAPE.LEN
Double
0
0
0
Esri
Feature geometry.
dataset
3523
Simple
FALSE
3523
TRUE
FALSE
20250117