- API
Energy Usage 2010 API
data.cityofchicago.org | Last Updated 2018-07-11T20:42:12.000ZDisplays several units of energy consumption for households, businesses, and industries in the City of Chicago during 2010. The data was aggregated from ComEd and Peoples Natural Gas by Accenture. Census blocks with less than 4 accounts is displayed at the Community Area without further geographic identifiers. This dataset also contains selected variables describing selected characteristics of the Census block population, physical housing, and occupancy.
- API
Crimes - 2020
data.cityofchicago.org | Last Updated 2024-08-13T11:06:34.000ZRecords from the Crimes - 2001 to Present dataset for the indicated year. Please see the description section of the full dataset for further information about the data.
- API
Crimes - 2002
data.cityofchicago.org | Last Updated 2024-08-13T11:06:34.000ZRecords from the Crimes - 2001 to Present dataset for the indicated year. Please see the description section of the full dataset for further information about the data.
- API
Additional Dwelling Unit Preapprovals Issued
data.cityofchicago.org | Last Updated 2024-08-12T00:01:25.000ZThis filtered view contains applications for preapprovals for Additional Dwelling Units (ADUs) that have been successfully processed and have an "Issued" status. See the <a href="https://data.cityofchicago.org/d/xbwc-ntpx">full dataset</a> for all applications and more information about the ADU program.
- API
Chicago Energy Benchmarking - 2018 Data Reported in 2019
data.cityofchicago.org | Last Updated 2024-02-09T19:21:58.000ZThe Chicago Building Energy Use Benchmarking Ordinance calls on existing municipal, commercial, and residential buildings larger than 50,000 square feet to track whole-building energy use, report to the City annually, and verify data accuracy every three years. The law, which phases in from 2014-2017, covers less than 1% of Chicago’s buildings, which account for approximately 20% of total energy used by all buildings. For more details, including ordinance text, rules and regulations, and timing, please visit www.CityofChicago.org/EnergyBenchmarking The ordinance authorizes the City to share property-specific information with the public, beginning with the second year in which a building is required to comply. This view shows data for a single year.
- API
311 Service Requests - Street Lights - All Out - Historical
data.cityofchicago.org | Last Updated 2024-07-26T18:43:33.000ZAs described in https://data.cityofchicago.org/stories/s/311-Dataset-Changes-12-11-2018/d7nq-5g7t, the function of this dataset was replaced by https://data.cityofchicago.org/d/v6vf-nfxy. This dataset is historical-only. All open reports of "Street Lights - All Out" (an outage of 3 or more lights) made to 311 and all requests completed since January 1, 2011.The Chicago Department of Transportation (CDOT) oversees approximately 250,000 street lights that illuminate arterial and residential streets in Chicago. CDOT performs repairs and bulb replacements in response to residents’ reports of street light outages. Whenever CDOT receives a report of an “All Out” the electrician assigned to make the repair looks at all the lights in that circuit (each circuit has 8-16 lights) to make sure that they are all working properly. If a second request of lights out in the same circuit is made within four calendar days of the original request, the newest request is automatically given the status of “Duplicate (Open).” Since CDOT's electrician will be looking at all the lights in a circuit to verify that they are all working, any “Duplicate (Open)” address will automatically be observed and repaired. Once the street lights are repaired, the status in CSR will read “Completed” for the original request and “Duplicate (Closed)” for any duplicate requests. A service request also receives the status of “Completed” when the reported lights are inspected but found to be in good repair and functioning; when the service request is for a non-existent address; or when the lights are maintained by a contractor. Data is updated daily.
- API
Arrests
data.cityofchicago.org | Last Updated 2024-08-13T11:37:05.000ZEach record in this dataset shows information about an arrest executed by the Chicago Police Department (CPD). Source data comes from the CPD Automated Arrest application. This electronic application is part of the CPD CLEAR (Citizen Law Enforcement Analysis and Reporting) system, and is used to process arrests Department-wide. A more-detailed version of this dataset is available to media by request. To make a request, please email <a href="mailto:dataportal@cityofchicago.org?subject=Arrests Access Request">dataportal@cityofchicago.org</a> with the subject line: <b>Arrests Access Request</b>. Access will require an account on this site, which you may create at https://data.cityofchicago.org/signup. New data fields may be added to this public dataset in the future. Requests for individual arrest reports or any other related data other than access to the more-detailed dataset should be directed to <a href="https://home.chicagopolice.org/services/adult-arrest-search/">CPD</a>, through contact information on that site or a <a href="http://www.chicago.gov/foia">Freedom of Information Act (FOIA)</a> request. The data is limited to adult arrests, defined as any arrest where the arrestee was 18 years of age or older on the date of arrest. The data excludes arrest records expunged by CPD pursuant to the Illinois Criminal Identification Act (20 ILCS 2630/5.2). Department members use charges that appear in Illinois Compiled Statutes or Municipal Code of Chicago. Arrestees may be charged with multiple offenses from these sources. Each record in the dataset includes up to four charges, ordered by severity and with CHARGE1 as the most severe charge. Severity is defined based on charge class and charge type, criteria that are routinely used by Illinois court systems to determine penalties for conviction. In case of a tie, charges are presented in the order that the arresting officer listed the charges on the arrest report. By policy, Department members are provided general instructions to emphasize seriousness of the offense when ordering charges on an arrest report. Each record has an additional set of columns where a charge characteristic (statute, description, type, or class) for all four charges, or fewer if there were not four charges, is concatenated with the | character. These columns can be used with the Filter function's "Contains" operator to find all records where a value appears, without having to search four separate columns. Users interested in learning more about CPD arrest processes can review current directives, using the CPD Automated Directives system (http://directives.chicagopolice.org/directives/). Relevant directives include: • Special Order S06-01-11 – CLEAR Automated Arrest System: describes the application used by Department members to enter arrest data. • Special Order S06-01-04 – Arrestee Identification Process: describes processes related to obtaining and using CB numbers. • Special Order S09-03-04 – Assignment and Processing of Records Division Numbers: describes processes related to obtaining and using RD numbers. • Special Order 06-01 – Processing Persons Under Department Control: describes required tasks associated with arrestee processing, include the requirement that Department members order charges based on severity.
- API
Crimes - 2008
data.cityofchicago.org | Last Updated 2024-08-13T11:06:34.000ZRecords from the Crimes - 2001 to Present dataset for the indicated year. Please see the description section of the full dataset for further information about the data.
- API
Strategic Subject List - Historical
data.cityofchicago.org | Last Updated 2020-09-25T21:57:26.000ZThe program described below ended in 2019. This dataset is being retained for historical reference. The information displayed represents a de-identified listing of arrest data from August 1, 2012 to July 31, 2016, that was used by the Chicago Police Department’s Strategic Subject Algorithm, created by the Illinois Institute of Technology and funded through a Department of Justice Bureau of Justice Assistance grant, to create a risk assessment score known as the Strategic Subject List or “SSL.” These scores reflect an individual’s probability of being involved in a shooting incident either as a victim or an offender. Scores are calculated and placed on a scale ranging from 0 (extremely low risk) to 500 (extremely high risk). Based on this time frame’s version of the Strategic Subject Algorithm, individuals with criminal records are ranked using eight attributes, not including race or sex. These attributes are: number of times being the victim of a shooting incident, age during the latest arrest, number of times being the victim of aggravated battery or assault, number of prior arrests for violent offenses, gang affiliation, number of prior narcotic arrests, trend in recent criminal activity and number of prior unlawful use of weapon arrests. Please note that this data set includes fields that are not used to calculate SSL, for example, neither race nor sex are used in the Strategic Subject Algorithm. Portions of the arrest data are de-identified on the basis of privacy concerns. The attributes used in the Strategic Subject Algorithm were revised on an ongoing basis during the lifetime of the program.
- API
CDPH Environmental Records Lookup Table
data.cityofchicago.org | Last Updated 2024-07-31T11:42:27.000ZThis dataset serves as a lookup table to determine if environmental records exist in a Chicago Department of Public Health (CDPH) environmental dataset for a given address. Data fields requiring description are detailed below. MAPPED LOCATION: Contains the address, city, state and latitude/longitude coordinates of the facility. In instances where the facility address is a range, the lower number (the value in the “Street Number From” column) is used. For example, for the range address 1000-1005 S Wabash Ave, the Mapped Location would be 1000 S Wabash Ave. The latitude/longitude coordinate is determined through the Chicago Open Data Portal’s geocoding process. Addresses that fail to geocode are assigned the coordinates 41.88415000022252°, -87.63241000012124°.This coordinate is located approximately just south of the intersection of W Randolph and N LaSalle. COMPLAINTS: A ‘Y’ indicates that one or more records exist in the CDPH Environmental Complaints dataset. NESHAPS & DEMOLITON NOTICES: A ‘Y’ indicates that one or more records exist in the CDPH Asbestos and Demolition Notification dataset. ENFORCEMENT: A ‘Y’ indicates that one or more records exist in the CDPH Environmental Enforcement dataset. INSPECTIONS: A ‘Y’ indicates that one or more records exist in the CDPH Environmental Inspections dataset. PERMITS: A ‘Y’ indicates that one or more records exist in the CDPH Environmental Permits dataset. TANKS: A ‘Y’ indicates that one or more records exist in the CDPH Storage Tanks dataset. Each 'Y' is a clickable link that will download the corresponding records in CSV format.