Mississauga Official Plan (2010) Designated Right-Of-Way Widths
This dataset reflects the Mississauga Official Plan (2010), parts of Schedule 8 - Designated Right-of-Way Widths as per its current consolidation.
Designated right-of-way widths are considered the
basic required rights-of-way along roadway
sections
Mississauga Official Plan guides how the City will grow and develop, as required by the Ontario Planning Act. The goals and policies of this Official Plan are intended to be achieved over 25 years, by 2031.
The Official Plan provides the basis for Mississauga’s land use and urban design, in line with the City’s Strategic Plan. Its policies address important parts of city-building that affect everyone that lives and works in Mississauga, including transportation, housing, culture and heritage, the environment, and the economy.
The Official Plan also sets standards for the review and approval of development applications in the City. This Plan aligns itself with the legislative and policy initiatives set out by the Province of Ontario and the Region of Peel.
To understand the planning rationale and policy objectives of Mississauga Official Plan, it should be read in its entirety and all relevant text, tables and schedules are to be applied to each situation
Mississauga Official Plan
Parts of Schedules:
Schedule 8 Designated Right-of-Way Widths
Symbology:
20m: HEX #F500F5, Width (W) 2pt, Dash Template (DT) 2 1, At line ends (ALE) Half Pattern, Cap Type (CT) Butt, Join Type (JT) Round
20m-26m: HEX #FF0024, W- 4pt, DT- 1 2, ALE-Half Pattern, CT-Butt, JT-Round
22m: HEX #91FF94, W- 2pt, DT- 8 2 2 2 2 2, ALE-Half Pattern, CT-Butt, JT-Round
23m-26m: HEX #FF5400, W- 2pt, DT-7 2 2 2 2 2, ALE-Half Pattern, CT-Butt, JT-Round
26m: HEX #FF5400, W- 4pt, DT- 2 6, ALE-Half Pattern, CT-Square, JT-Round
26m-35m: HEX #000000, W- 1.5pt, DT- 6 2 2 2, ALE-Half Pattern, CT-Butt, JT-Round
27.5: HEX #000000, W- 2pt, DT- 8 5, ALE-No Constraint, CT-Square, JT-Round
30m: HEX #6F00FF, W- 4pt, DT- 8 2 1 2 1 2, ALE-Half Pattern, CT-Butt, JT-Round
30m-50m: HEX #D99191, W- 4pt, DT- 8 2 1 2, ALE-Half Pattern, CT-Butt, JT-Round
35m: HEX #48FF00, W- 4pt, DT- 12 2, ALE-Half Pattern, CT-Butt, JT-Round
36m: HEX #00FF00, W- 4pt, DT- 22 3, ALE-No Constraint, CT-Butt, JT-Round
40m: HEX #0048FF, W- 4pt, DT- 22 3, ALE-No Constraint, CT-Butt, JT-Round
42m: HEX #0000C6, W-4pt, DT- 8 2 1 2, ALE-Half Pattern, CT-Butt, JT-Round
43.5m: HEX #D99191, W- 4pt, DT- 22 3, ALE-No Constraint, CT-Butt, JT-Round
44.5m: HEX #AF6B6B, W- 4pt, DT- 12 2, ALE-No Constraint, CT-Butt, JT-Round
45m: HEX #FF0024, W- 4pt, DT- 25 3, ALE-No Constraint, CT-Butt, JT-Round
50m: HEX #FF24FF, W- 4pt, DT- 8 2 1 2, ALE-Half Pattern, CT-Butt, JT-Round
55m: HEX #FF24FF, W- 4pt, DT- 1 2, ALE-Half Pattern, CT-Butt, JT-Round
60m: HEX #DD0000, W- 4pt, DT- 8 2 1 2, ALE-Half Pattern, CT-Butt, JT-Round
65m: HEX #000000, W- 4pt, DT- 1 2, ALE-Half Pattern, CT-Butt, JT-Round
67m: HEX #000000, W- 4pt, CT-Butt, JT-Round
Datasets available for download
-
MOP_DesignatedRightOfWayWidthsFeature Layer
Layer 0 via ArcGIS REST API
-
MOP_DesignatedRightOfWayWidths (Explore)HTML
Explore MOP_DesignatedRightOfWayWidths on ArcGIS Hub
Additional Info
| Field | Value |
|---|---|
| Last Updated | March 24, 2026, 22:46 (UTC) |
| Created | March 24, 2026, 22:46 (UTC) |
|
Domain / Topic
Domain or topic of the dataset being cataloged.
|
|
|
Title
Title for the Dataset.
|
Mississauga Official Plan (2010) Designated Right-Of-Way Widths |
|
Description
A description of the dataset.
|
This dataset reflects the Mississauga Official Plan (2010), parts of Schedule 8 - Designated Right-of-Way Widths as per its current consolidation. Designated right-of-way widths are considered the
basic required rights-of-way along roadway
sections Mississauga Official Plan guides how the City will grow and develop, as required by the Ontario Planning Act. The goals and policies of this Official Plan are intended to be achieved over 25 years, by 2031. The Official Plan provides the basis for Mississauga’s land use and urban design, in line with the City’s Strategic Plan. Its policies address important parts of city-building that affect everyone that lives and works in Mississauga, including transportation, housing, culture and heritage, the environment, and the economy. The Official Plan also sets standards for the review and approval of development applications in the City. This Plan aligns itself with the legislative and policy initiatives set out by the Province of Ontario and the Region of Peel. To understand the planning rationale and policy objectives of Mississauga Official Plan, it should be read in its entirety and all relevant text, tables and schedules are to be applied to each situation Mississauga Official Plan Symbology: 20m: HEX #F500F5, Width (W) 2pt, Dash Template (DT) 2 1, At line ends (ALE) Half Pattern, Cap Type (CT) Butt, Join Type (JT) Round |
|
Tags / Keywords
Keywords/tags categorizing the dataset.
|
|
|
Format (CSV, XLS, TXT, PDF, etc)
File format of the dataset.
|
|
|
Dataset Size
Dataset size in megabytes.
|
320.0 |
|
Metadata Identifier
Metadata identifier – can be used as the unique identifier for catalogue entry
|
1669907517308r9794595504248913 |
|
Published Date
Published date of the dataset.
|
2022-11-29 |
|
Time Period Data Span (start date)
Start date of the data in the dataset.
|
|
|
Time Period Data Span (end date)
End date of time data in the dataset.
|
|
|
GeoSpatial Area Data Span
A spatial region or named place the dataset covers.
|
| Field | Value |
|---|---|
|
Identifier
Unique identifier for the dataset.
|
b61270492a79410e9b38272f38780c61 |
|
Language
Language(s) of the dataset
|
English |
|
Link to dataset description
A URL to an external document describing the dataset.
|
https://opendata-mississauga.hub.arcgis.com/datasets/mississauga::mississauga-official-plan-2010-designated-right-of-way-widths |
|
Persistent Identifier
Data is identified by a persistent identifier.
|
|
|
Globally Unique Identifier
Data is identified by a persistent and globally unique identifier.
|
|
|
Contains data about individuals
Does the data hold data about individuals?
|
|
|
Contains data about identifiable individuals
Does the data hold identifiable data about individual?
|
|
|
Contains Indigenous Data
Does the data hold data about Indigenous communities?
|
|
|
Portal Type
Platform type of the source portal.
|
| Field | Value |
|---|---|
|
Version
Version of the datatset
|
None |
|
Source
Source of the dataset.
|
None |
|
Version notes
Version notes about the dataset.
|
|
|
Is version of another dataset
Link to dataset that it is a version of.
|
|
|
Other versions
Link to datasets that are versions of it.
|
|
|
Provenance Text
Provenance Text of the data.
|
City of Mississauga |
|
Provenance URL
Provenance URL of the data.
|
|
|
Temporal resolution
Describes how granular the date/time data in the dataset is.
|
|
|
GeoSpatial resolution in meters
Describes how granular (in meters) geospatial data is in the dataset.
|
|
|
GeoSpatial resolution (in regions)
Describes how granular (in regions) geospatial data is in the dataset.
|
| Field | Value |
|---|---|
|
Indigenous Community Permission
Who holds the Indigenous Community Permission. Who to contact regarding access to a dataset that has data about Indigenous communities.
|
|
|
Community Permission
Community permission (who gave permission).
|
|
|
The Indigenous communities the dataset is about
Indigenous communities from which data is derived.
|
| Field | Value |
|---|---|
|
Number of data rows
If tabular dataset, total number of rows.
|
210 |
|
Number of data columns
If tabular dataset, total number of unique columns.
|
4 |
|
Number of data cells
If tabular dataset, total number of cells with data.
|
840 |
|
Number of data relations
If RDF dataset, total number of triples.
|
|
|
Number of entities
If RDF dataset, total number of entities.
|
|
|
Number of data properties
If RDF dataset, total number of unique properties used by the triples.
|
|
|
Data quality
Describes the quality of the data in the dataset.
|
|
|
Metric for data quality
A metric used to measure the quality of the data, such as missing values or invalid formats.
|
0 Comments