AndreaBozzo/ceres-open-data-index huggingface dataset:
Neighbourhood Profiles

The Census of Population is held across Canada every 5 years and collects data about age and sex, families and households, language, immigration and internal migration, ethnocultural diversity, Aboriginal peoples, housing, education, income, and labour. City of Toronto Neighbourhood Profiles use this Census data to provide a portrait of the demographic, social and economic characteristics of the people and households in each City of Toronto neighbourhood. The profiles present selected highlights from the data, but these accompanying data files provide the full data set assembled for each neighbourhood.

For an interactive visualization of this data, visit the [Neighbourhood Profiles webpage](https://www.toronto.ca/city-government/data-research-maps/neighbourhoods-communities/neighbourhood-profiles/).

In these profiles, "neighbourhood" refers to the City of Toronto's 158 social planning neighbourhoods. These social planning neighbourhoods were developed in the late 1990s by the City of Toronto to help government and community organizations with local planning by providing socio-economic data at a meaningful geographic area. The boundaries of these social planning neighbourhoods are consistent over time, allowing for comparison between Census years. Neighbourhood level indicators from sources other than the Census of Population are also available through the City's [Wellbeing Toronto](https://www.toronto.ca/city-government/data-research-maps/neighbourhoods-communities/wellbeing-toronto/) mapping application and here on the Open Data portal.

Each data point in this file is presented for the City's 158 neighbourhoods or 140 neighbourhoods prior to April 2021. The data is sourced from a number of Census tables released by Statistics Canada. The general Census Profile is the main source table for this data. Data tables are available for the Census years of 2001, 2006, 2011, 2016, and 2021.   

For definitions of terms and concepts referenced in this data set, as well as limitations imposed by rounding, data suppression standards, and geometry, users should consult the reference materials produced by Statistics Canada for the [2016 Census](https://www12.statcan.gc.ca/census-recensement/2016/ref/index-eng.cfm) or the [2021 Census](https://www12.statcan.gc.ca/census-recensement/2021/ref/index-eng.cfm). Please note that social planning neighbourhoods are not an official standard geography produced by Statistics Canada and the data herein is compiled by special request through the [Community Data Program](https://communitydata.ca/).

Organization: City of Toronto
Transit Oriented Communities

This dataset provides a spatial representation of Transit‑Oriented Community (TOC) sites across the City of Toronto. The map identifies publicly owned lands located near existing or planned rapid transit stations that are being considered or advanced for higher‑density, mixed‑use development.

Transit‑Oriented Communities support the efficient use of transit infrastructure by integrating residential, employment, institutional, and community uses within walking distance of transit stations. The mapped TOC sites are intended to help accommodate population and employment growth while supporting transit ridership, complete communities, and city‑building objectives.

The dataset is intended to support planning analysis, public transparency, and engagement by illustrating where TOC initiatives are located city‑wide. It may be used by City staff, other public agencies, researchers, and the public to better understand the geographic distribution and context of Transit‑Oriented Community sites.

Tags: development
Organization: City of Toronto
Traffic Calming Database

The Vision Zero Project Unit within Transportation Services maintains a database that tracks existing locations with installed traffic calming measures. These measures are traffic islands, speed cushions and speed humps. The descriptions of these traffic calming measures can be found [here](https://www.toronto.ca/services-payments/streets-parking-transportation/traffic-management/traffic-calming/).

Our traffic calming database refreshes at the end of each week to ensure the latest updates are available for public access and review.

The Vision Zero Projects Unit also maintains a spatial version of this dataset, which is also displayed on the public [Vision Zero mapping tool](https://www.toronto.ca/services-payments/streets-parking-transportation/road-safety/vision-zero/safety-measures-and-mapping/). This spatial data is maintained and updated on a separate schedule.


Tags: speed bumps
Organization: City of Toronto
Development Pipeline

The Development Pipeline examines how and where the city has grown over the past five years and provides insight on how it will continue to develop in the near future. The Development Pipeline enables City Planning to track urban growth, monitor development trends, and measure progress towards municipal and provincial housing targets. The Development Pipeline bulletin is published annually and the dashboard is updated quarterly on a best-effort basis. A subset of the Development Pipeline information is used to create this dashboard.

Tags: construction
Organization: City of Toronto
Z39.50 - Library Catalogue

Z39.50 provides real-time library catalogue access. It is an international standard client-server, application layer communications protocol for searching and retrieving information from a database over a TCP/IP computer network.

The data is stored in the Toronto Public Library's Integrated Library System (ILS).

Z39.50 connection details:

* host: symphony.tpl.ca

* port: 2200

* database name: unicorn

* search map name: CATALOG

* unicode server: yes

Note: We are unable to publish the schematic of the library catalogue. If you elect to use Z39.50, please search the internet for available resources to learn more about accessing and parsing library catalogue data using this protocol.

Information about the MARC 21 format for bibliographic data can be found at [https://www.loc.gov/marc/bibliographic/] (https://www.loc.gov/marc/bibliographic/)

Tags: library, library catalogue, z3950
Organization: City of Toronto
Private Transportation Companies – Vehicle Operating Data

The City of Toronto collects trip and vehicle operating data from Private Transportation Companies (PTCs). This page contains data on the operations of PTC vehicles operating in the City.

### Vehicle Operating Data (from 2020-01-01 onward)

This dataset provides key operating statistics for each vehicle, summarized by hour. Key metrics include:

* Duration spent and distance travelled in various phases of a driver’s PTC shift

* Total fares collected

* Total trips completed, including pooled trips

* Total trips cancelled, including cancellations by drivers and passengers

These data can be accessed by downloading a year of data using the **operating\_hours\_yyyy.zip** links below,  which contain 12 months of data for the year **yyyy**. Once unzipped, there is one file per month. 

### Other PTC data

[Summary data and trip data are also available.](https://open.toronto.ca/dataset/private-transportation-companies-summary-and-trip-data)

Tags: PTC, Private Transportation Companies, ridehail, rideshare
Organization: City of Toronto
Private Transportation Companies - Summary and Trip Data

The City of Toronto collects trip and vehicle operating data from Private Transportation Companies (PTCs). This page contains two datasets:

* Summary Data

* Trip Data

### Summary Data (From 2018-01-01 onwards except otherwise stated)

The summary table provides daily, high-level metrics designed for quick interpretation of PTC activity across the City. It includes:

**Trip summary statistics**

* Total completed and cancelled trips by different service types

* Average trip distance

**Vehicle operating summary statistics (Only available from 2020-01-01 onwards)**

* Total active vehicles

* Average wait time

* Time and distance (percentage and absolute values) in various stages of a PTC driver shift

Refer to the **summary_data** file below



### Trip Data (From 2018-01-01 onwards)

This dataset summarizes completed trips, organized by Toronto pick-up and drop-off ward and by hour. Key metrics include:

* Total completed trips

* Average fare

* Average distance travelled

* Average trip time duration

These data can be accessed by downloading a year of data using the **trip\_yyyy.zip** links below, which contain 12 months of data for the year **yyyy**. Once unzipped, there is one file per month. 

## Other PTC data

[Vehicle operating data is also available.](https://open.toronto.ca/dataset/private-transportation-companies-vehicle-operating-data)

## Technical Documentation

Technical Documentation, including a detailed Data Dictionary, can be found in the **trips\_and\_summary\_readme** below.

Tags: PTC, Private Transportation Companies, ridehail, rideshare
Organization: City of Toronto
Central Intake calls

If you are in need of emergency shelter space, please call the City of Toronto’s Central Intake line at 416-338-4766 or 1-877-338-3398.

This catalogue entry provides two data sets related to calls to Central Intake. 

Central Intake is a City-operated, 24/7 telephone-based service that offers referrals to emergency shelter and other overnight accommodation, as well as information about other homelessness services. These two data sets provide information about calls received by Central Intake, the outcomes of those calls, and the number of individuals who could not be matched to a shelter space each day.

The first, **Central Intake Service Queue Data**, provides counts of the number of unique individuals who contacted Central Intake to access emergency shelter but were not matched to a shelter space. Generated through Central Intake caseworkers' use of the City's Shelter Management Information System (SMIS), the data are reported as a count for every operational day.

The SMIS service queue for Central Intake records when a bed is requested for a caller seeking a shelter space. Those callers who could not be matched to an available space that suits their needs at the time of their call remain in the queue until they can be provided a referral or until the closeout process at the end of the night (i.e. 4:00 a.m.).

Service Queue data combines data exported from the Central Intake service queue at 4:00 a.m., with manually coded outcome data based on the review of each individual's SMIS records for the day. SSHA began collecting data on how many people remain unmatched in the service queue over a 24 hour period at the beginning of November 2020. Given the manual nature of the preparation of the data in this data set, this file will be updated on a monthly basis. Data will be reported separately for every operational day in that month.

The second data set, **Central Intake Call Wrap-Up Codes Data**, provides counts of calls answered by Central Intake, classified by the nature of the call.  When a call is handled by a caseworker at Central Intake, the caseworker assigns a wrap-up code to the call. This tracking allows for analysis of call trends.

Central Intake uses 13 distinct wrap-up codes to code the calls they receive. This data set provides a daily summary of the number of calls received by each call wrap-up code. The data are manually retrieved from the City's call centre database reports. Given the manual nature of the preparation of the data in this data set, this file will be updated on a monthly basis. Data will be reported separately for every operational day in that month.

Please note that while the wrap-up codes provide information related to the volume and type of calls answered by Central Intake, the data do not track requests made by unique individuals nor the ultimate outcomes of referrals.

Please also note that the previews and Data Features below only show information pertaining to the Central Intake Call Wrap-Up Codes Data dataset.


Tags: shelter
Organization: City of Toronto
Public Art

This map shows over 400 works of public art throughout the City of Toronto. The inventory is a record of public art from two City programs: the [Public Art & Monuments Collection](https://www.toronto.ca/explore-enjoy/history-art-culture/public-art/public-art-monuments-collection/) and the [Percent for Public Art Program](https://www.toronto.ca/city-government/planning-development/official-plan-guidelines/design-guidelines/percent-for-public-art-inventory/).

Tags: art, monuments, planning, public
Organization: City of Toronto
Parking Tickets

See Parking Ticket Data Readme file

Approximately 2.8 million parking tickets are issued annually across the City of Toronto. This dataset contains non-identifiable information relating to each parking ticket issued for each calendar year. The tickets are issued by Toronto Police Services (TPS) personnel as well as persons certified and authorized to issue tickets by TPS.

This data set contains complete records only. Incomplete records in the City database are not included in the data set. Incomplete records may exist due to a variety of reasons e.g. the vehicle registration is out-of-province, tickets paid prior to staff entering the ticket data, etc.The volume of incomplete records relative to the overall volume is low and therefore presents insignificant impact to trend analysis.

The columns in this data are defined as follows:

- **tag_number_masked**:  Parking Violation Notice number or Violation/Ticket Number, used to create the record in city systems

- **date\_of\_infraction**:  Violation Date or the date the offence was committedfield name to Date of Violation.

- **infraction\_code**:  Violation Code that refers to the parking bylaw that the vehicle has violated.

- **infraction\_description**: Short description of the Violation Code

- **set\_fine\_amount**:  Penalty Amount prescribe in the bylaw for the Violation Code

- **time\_of\_infraction**:  Violation Time in which the offence was committed, and ticket issued

- **location1**:  First part of the location of the violation where the offence was committed. This field is used to capture the proximity of the location and only captures the following information, NR=near, AT=at, OPP=opposite, S/S=south side, E/O=east of, etc

- **location2**:  Second part of the location of the violation where the offence was committed, used to capture the street name or address of the location

- **location3**:  Used in the same manner as the first location. This field is not always used, only in the event that the officer issues the violation near a corner

- **location4**:  Used in the same manner as the second location, also only used when the officer issues the violation near a corner

- **province**:  Province where the licence plate associated with the violation is registered


Please note: for certain years, you will need to split the files yourself if you plan on reading the data in Microsoft Excel.


Tags: parking, parking ticket
Organization: City of Toronto
Business Improvement Areas

A Business Improvement Area (BIA) is an association of commercial property
owners and tenants within a defined area who work in partnership with the City
to create thriving, competitive, and safe business areas that attract
shoppers, diners, tourists, and new businesses.  The BIA layer represents the
active BIAs in the City of Toronto that has been enacted by Council.  Each BIA
has been defined by a by-law and is represented by a Board of Management.  The
layer is updated as BIAs are created, amended or deleted by Council. This file
is a polygon file and is best utilized with the Toronto Street Centreline
Dataset.



Tags: bia, business improvement area
Organization: City of Toronto
Green Spaces

Green Spaces is a geospatial dataset of polygons that is a point-in-time generalized representation of existing parks and open spaces within the City of Toronto. Green Spaces includes public parks, beaches, parts of ravines, golf courses, cemeteries, and other open space areas such as those offered by various private institutions. These spaces may or may not be publicly accessible and are either publicly owned/maintained or they are privately owned/maintained. Green Spaces is not an exhaustive dataset of all the public and private parks and open spaces within the City. It does not encompass all areas protected by the Ravine and Natural Feature Protection By-Law, by Environmentally Significant Areas or by Natural Heritage Areas.  

Green Spaces is primarily intended to visualize our existing overall parks and open space system. It is used to symbolize the green coloured areas in many of the City's mapping products such as Toronto's Interactive Map or the Toronto Parkland Strategy[^1]. 

This dataset is jointly maintained by the Geospatial Competency Centre (GCC) and the Parks, Forestry & Recreation division (PFR). The attribute field in this dataset titled "AREA_CLASS" indicates whether the GCC or PFR maintain the data and the type of green space it is.

**PFR Green Spaces**  

PFR Green Spaces are owned and/or operated by the City of Toronto and are derived from PFR's Parkland Asset Repository. They include the area classes: Park, Golf Course, Cemetery, Hydro Field/Utility Corridor, and others. Representation of Green Spaces can change overtime – due to new park acquisitions, development/reconfiguration of land etc. – PFR works to continuously improve the City-PFR-owned portions of this dataset as new information arises. 

**GCC Green Spaces**  

All other Green Spaces were created by the GCC and include area classes with the prefix of "OTHER_". These green spaces are derived through city-wide parcel analysis.

[^1]This Green Spaces layer cannot be used to reproduce the results of the [2019 Parkland Strategy](https://www.toronto.ca/city-government/accountability-operations-customer-service/long-term-vision-plans-and-strategies/parkland-strategy/), however the GCC Green Spaces portions of the dataset was used to help visualize Other Open Spaces in "Figure 06: Toronto’s Parks and Open Space Network" of the report. The Toronto Parkland Strategy is currently in the process of being updated and new parkland data is not yet finalized.


Organization: City of Toronto
Bridge Structures

Like all infrastructure, bridges and structures require ongoing maintenance. Regular inspections help the City ensure that its bridges and structures are well maintained and are in a state of good repair.

The bridge structure dataset provides information about bridges and structures managed by the City of Toronto, the Province of Ontario-Ministry of Transportation (MTO), Toronto Transit Commission (TTC) and Metrolinx (MX). The dataset is limited to the City of Toronto geographical boundary. The structures included in this dataset are bridges with a span of three metres or more, culverts with an opening of three metres or more and the elevated section of the F.G. Gardiner Expressway.

Information is updated annually after each inspection cycle every two years. By clicking a bridge or structure location on the map, you are able to obtain information about the bridge or structure including the location, usage, age, year of last inspection, inspection results and next inspection year of the bridge or structure. Bridges or structures that are not identified on the map are likely managed by other parties than the ones listed above.

The dataset also includes locations of some privately managed bridges, Canadian National Railway (CNR) bridges and Canadian Pacific Railway (CPR) bridges. MTO, TTC, MX, CNR, CPR and private owners follow their own inspection routines to maintain their bridges in a state of good repair. Information on those bridges and structures is provided by their owners and has not been verified for its currency, completeness or accuracy.


Tags: bridges, culverts, elevated roadways
Organization: City of Toronto
Municipal Licensing and Standards - Toronto Animal Shelter Activity

Toronto Animal Services (TAS) operates three Animal Shelters, and cares for animals that are lost or surrendered by owners and animals that are available for adoption to new homes. This dataset contains Shelter Activity statistics for the three TAS shelters. TAS also provides the following services:

- 24-hour emergency response to calls for animals that are injured, in distress or are jeopardizing the safety of the public 

- mobile spay/neuter clinic for pet owners in neighbourhood improvement areas  

- promotion of responsible pet ownership through programs, events and enforcement of the Municipal Code, Chapter 349 and other animal- related laws

 


Tags: animal services, animal shelter
Organization: City of Toronto
Properties Requiring a Cultural Heritage Evaluation Report Under OPA 720

The following dataset includes properties that have been identified by City Council through a City-led study as having potential cultural heritage value or interest, that are not included on the City’s Heritage Register, and properties that were formerly included on the City’s Heritage Register and are believed to hold cultural heritage value or interest.  Development applications submitted for these properties must include a Cultural Heritage Resource Assessment in accordance with [Schedule 3](https://www.toronto.ca/wp-content/uploads/2017/11/904d-cp-official-plan-Schedule-3.pdf) of the City’s Official Plan. This assessment will be used to assist the City in determining whether a property, collection of properties, or landscape feature has cultural heritage value.

Tags: Buildings
Organization: City of Toronto
Police Annual Statistical Report - Traffic Collisions

This dataset includes all Motor Vehicle Collision (MVC) occurrences by their occurrence date and related offences. The MVC categories include property damage (PD) collisions, Fail to Remain (FTR) collisions, injury collisions and fatalities. This data is provided at the occurrence level, therefore multiple offences and/or victims can be associated with each record. 

[Traffic Collisions Dashboard](https://data.torontopolice.on.ca/pages/b4c0db45de42476a94f72d1e650b9959)
[Download Documentation](https://torontops.maps.arcgis.com/sharing/rest/content/items/c0b17f1888544078bf650f3b8b04d35d/data)

In this dataset, a collision is defined as the contact resulting from the motion of a motor vehicle or streetcar or its load, which produces property damage, injury or death. The term collision indicates that the initial point of contact involved at least one motor vehicle or streetcar.

### Definitions:
**Fatal Collisions** occur when an individual’s injuries from a MVC result in a fatality within 30 days. Please note this category excludes:
(i)   Occurrences on private property
(ii)  Occurrences related to sudden death prior to collision (suicide or medical episode)
(iii) Occurrences where the individual has died more than 30 days after the collision

**Personal Injury Collisions** occur when an individual involved in a MVC suffers personal injuries. 

**Fail to Remain Collisions** occur when an individual involved in a MVC fails to stop and provide their information at the scene of a collision.

**Property Damage Collisions** occur when an individual’s property has been damaged in a MVC or the value of damages is less than $2,000 for all involved parties.

This data does not include occurrences that have been deemed unfounded. The definition of unfounded according to Statistics Canada is: “It has been determined through police investigation that the offence reported did not occur, nor was it attempted” (Statistics Canada, 2020).**

** Statistics Canada. 2020. Uniform Crime Reporting Manual. Surveys and Statistical Programs. Canadian Centre for Justice Statistics.


Tags: Annual Statistical Report
Organization: City of Toronto