ArcGIS REST Services Directory
JSON

Layer: Sidewalk_walkable (ID:1)

View In:   Map Viewer

Name: Sidewalk_walkable

Display Field: LINEAR_N_1

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: Toronto Sidewalk Inventory (2015)The sidewalk inventory provides information on the location of sidewalks along all transportation corridors within the City of Toronto limits. City centreline data was utilized as the base network while aerial photography (orthoimagery) captured in spring of 2015 was used to determine sidewalk presence. The sidewalk inventory is used by City staff in addition to others such as consultants hired by the City for various purposes (e.g. infrastructure planning, safety studies, area specific studies, Environmental Assessments and Transportation Master Plans). The Essential Links Capital Program utilizes this inventory in order to identify and prioritize building of new sidewalk links.There may be inaccuracies in the dataset due to human input errors, low visibility of some aerial photos and recent changes since the aerial photos were captured in 2015. Help us improve the accuracy of the inventory by reporting any errors to Walking@Toronto.caThe original centreline data organizes all transportation corridors into line segments which are typically from one intersection to another. Each line segment has been assigned a code to indicate its corresponding sidewalk presence. The description of each code is outlined below:SDWLK_CodeDescription1Sidewalk on south side only2Sidewalk on north side only3No sidewalk on either side4Sidewalk on west side only5Sidewalk on east side only6Pending (Roadway under development)7Sidewalk on both sides10Laneway without sidewalks11Walkway12Pathway13Not applicableFurther Clarification:Pending (code 6) segments indicate areas which are under new development (construction) and may or may not include a sidewalk after the observed development is completed.Walkways (code 11) within the inventory are pedestrian only paths that typically connect two roadways and are part of the official City centerline data. Pathways (code 12): Pathways are segments that are pedestrian paths of interest observed within the aerial imagery but not documented within the official City centreline data. These unofficial paths may not be maintained or owned by the City. Examples of pathways include walkways, recreational trails and desire lines which may not be paved.Not applicable (code 13) segments are either roadways on which the City does not build sidewalks (e.g. expressways and dedicated busways) or features that are not physical roadways (e.g. shorelines, railways).Sidewalks are not a required component of laneways, however, where sidewalks are present on laneways codes 1 to 7 are used to indicate sidewalk presence. Otherwise code 10 is used to indicate laneways without sidewalks. Sidewalk codes are determined on a worse case basis. For example if a roadway segment only has full sidewalks on one side but partial sidewalks on the other side, the segment is considered as having a sidewalk on one side only.Other Data Field Descriptions:To document the presence of a sidewalk with partial / intermittent coverage, the "partial" indicator is included as a field in the inventory. Additionally, a "multiuse" indicator is included as a field to provide further information on the sidewalk conditions of a segment. These fields are described below:Partial: Some sidewalks end before they reach the next intersection, or only exist for a part of the block. Segments with this sidewalk condition are marked with a "1" in the "partial" field of the inventory. An entry of "0" indicates that the sidewalk, if present, is not partial.Multi-use: Some pedestrian pathways adjacent to roadways are intended to be multi-use trails which accommodate other methods of transportation such as cycling. If a dedicated sidewalk is not present but a multi-use trail is, the segment is still considered to have a sidewalk, but is marked with a "1" in the "multi-use" field of the inventory. An entry of "0" indicates there is either no multi-use trail present or that a dedicated sidewalk is present in addition to the multi-use trail.Other centreline related information for each segment is included in the sidewalk inventory. These fields are described below:FID: System generated unique geographic identifier.Shape: Geometry type (i.e. Polyline)GEO_ID: A unique identifier associating the segment with the city centreline data. This data is unavailable for pathways (sidewalk code 12) as they are not included within the official city centreline. Some of these identifiers may become outdated as the centreline dataset is modified (i.e. updated) and refreshed more frequently than the sidewalk inventory.LINEAR_N_1: Street name with abbreviated suffix.LINEAR_N_2: Full street name.ADDRESS_L: Address number ranges on left (typically north or west) side of road.ADDRESS_R: Address number ranges on right (typically south or east) side of the road.LINEAR_N_3: Street name with no suffix.LINEAR_N_4: Street suffix only.LINEAR_N_5: Street direction.LINEAR_N_6: Former Municipality/District noted for duplicate street names.JURISDICTI: Jurisdiction (ownership) of street segment.SDWLK_DESC: A textual description of the segment and its relation to the sidewalk inventory. This text is generated based on the other data fields. It describes whether a sidewalk is present or partially present, which side of the roadway the sidewalk is present on or what type of feature the segment represents otherwise. Road_Type: Describes the road classification of a segment (e.g. local, collector, major arterial). This information is derived directly from the 2016 city centreline data.Shape_Leng: Length of road segment in meters.Although the sidewalk inventory contains information on trails, roadways and other features related to the centreline, its intent is to provide information about sidewalks. Information on other features may be incomplete/out of date. For more updated or expanded datasets on such features, please visit the City of Toronto Open Data website.

Copyright Text: Pedestrian Projects, Public Realm, Transportation Services, City of Toronto

Min. Scale: 0

Max. Scale: 0

Default Visibility: true

Max Record Count: 1000

Supported query Formats: JSON, geoJSON, PBF

Use Standardized Queries: True

Extent:

Drawing Info:

HasZ: false

HasM: false

Has Attachments: false

Has Geometry Properties: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Object ID Field: OBJECTID

Unique ID Field:

Global ID Field:

Type ID Field:

Fields:
Templates:

Is Data Versioned: false

Has Contingent Values: false

Supports Rollback On Failure Parameter: true

Last Edit Date: 4/15/2018 5:57:22 PM

Schema Last Edit Date: 4/15/2018 5:57:22 PM

Data Last Edit Date: 4/15/2018 5:57:22 PM

Supported Operations:   Query   Query Pivot   Query Top Features   Query Analytic   Query Bins   Generate Renderer   Validate SQL   Get Estimates   ConvertFormat