Community Council Boundaries Survey Results

This data set contains input from the Community Council boundaries consultation held between May 3 and May 27, 2018 by the City of Toronto. The purpose of posting this dataset is to create a record of the consultation and the public's views, in a respectful way without offensive or otherwise inappropriate content, and to protect the City from legal liability.

The data set has been reviewed to ensure that the content does not:

1. Contravene the City's policies or applicable laws related to anti-discrimination, human rights or privacy;

2. Include information that identifies an individual other than one acting in an official capacity, nor any comments that are personal attacks on someone's character, personal or business affairs, etc.;

3. Address an issue before the courts or outside of the City's jurisdiction, or comments on another organization or private company;

4. Contain unsubstantiated rumours or potentially libellous statements;

5. Contain obscenities, derogatory, insulting, offensive, violent or hateful language;

6. Include any email addresses, attachments, or web links.

In cases where such comments are found, only the language that contradicts the policy is removed by staff -- the remainder of the comments remains in the data set. The Community Council boundary feedback survey received 619 partial and complete responses and an additional four submissions by email. The purpose of the survey was to collect input on an Options Paper, which was developed by staff and provided information on Community Councils, highlighted three primary, and five alternative models, and asked what issues or considerations would support the selection of a final model for Council's consideration.

In addition to collecting information on a preferred model, the consultation sought public input on why one model was thought to be better than another, what geographic considerations would contribute to an effective Community Council, the impact changing the boundaries would have on respondents, and whether or not respondents had previously attended a Community Council meeting.

This survey is not a vote. Public and stakeholders opinions, along with technical and policy considerations will all be used to inform City staff recommendations and decisions to be made by City Council. The survey was available in English, Spanish, French, Italian, Portuguese, Urdu, Korean, Chinese Simplified, Panjabi, Tagolog and Tamil.

A small number of survey responses (25) were received on paper and entered in by City staff. One Tamil response was received and translated into English for analysis. The data published here includes both complete and incomplete surveys.

Further explanation in the readme file and available on request.

For more information: https://www.toronto.ca/city-government/accountability-operations-customer-service/city-administration/city-managers-office/key-intiatives/views-on-new-community-council-boundaries-for-the-city-of-toronto-2/

Datasets available for download

Additional Info

Field Value
Last Updated October 4, 2024, 04:48 (UTC)
Created October 4, 2024, 02:37 (UTC)
Domain / Topic
Domain or topic of the dataset being cataloged.
City government
Format (CSV, XLS, TXT, PDF, etc)
File format of the dataset.
.xlsx - application/vnd.openxmlformats-officedocument.spreadsheetml.sheet, .xla, .xlb, .xlc, .xlm, .xls, .xlt, .xlw - application/vnd.ms-excel
Dataset Size
Dataset size in megabytes.
Metadata Identifier
Metadata identifier – can be used as the unique identifier for catalogue entry
Published Date
Published date of the dataset.
2019-07-23
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
Access category
Type of access granted for the dataset (open, closed, service, etc).
Limits on use
Limits on use of data.
Location
Location of the dataset.
https://open.toronto.ca/dataset/community-council-boundaries-survey-results
Data Service
Data service for accessing a dataset.
Owner
Owner of the dataset.
Strategic & Corporate Policy, cityplanning@toronto.ca
Contact Point
Who to contact regarding access?
Publisher
Publisher of the dataset.
Publisher Email
Email of the publisher.
cityplanning@toronto.ca
Author
Author of the dataset.
cityplanning@toronto.ca
Author Email
Email of the author.
cityplanning@toronto.ca
Accessed At
Date the data and metadata was accessed.
Field Value
Identifier
Unique identifier for the dataset.
Language
Language(s) of the dataset
Link to dataset description
A URL to an external document describing the dataset.
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?
Field Value
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.
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.
Number of data columns
If tabular dataset, total number of unique columns.
Number of data cells
If tabular dataset, total number of cells with data.
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

Please login or register to comment.