NYC 311 Complaint Data
About the dataset
The New York City 311 Service Requests Data provides information on requests to the city's complaint service from 2010 to the present.
NYC311 responds to thousands of inquiries, comments and requests from customers every single day. This dataset represents only service requests that can be directed to specific agencies. This dataset is updated daily and expected values for many fields will change over time. The lists of expected values associated with each column are not exhaustive. Each row of data contains information about the service request, including complaint type, responding agency, and geographic location. However the data does not reveal any personally identifying information about the customer who made the request.
This dataset describes site-specific non-emergency complaints (also known as “service requests”) made by customers across New York City about a variety of topics, including noise, sanitation, and street quality.
The columns have been renamed to lower_case_underscore
format for ease of typing. For more details on column data than below, see the associated data dictionary at that link above, in an Excel file.
column_name | column_type | null | description |
---|---|---|---|
unique_key | BIGINT | YES | Unique identifier of a Service Request (SR) in the open data set. Each 311 service request is assigned a number that distinguishes it as a separate case incident. |
created_date | TIMESTAMP | YES | The date and time that a Customer submits a Service Request. |
closed_date | TIMESTAMP | YES | The date and time that an Agency closes a Service Request. |
agency | VARCHAR | YES | Acronym of responding City Government Agency or entity responding to 311 Service Request. |
agency_name | VARCHAR | YES | Full agency name of responding City Government Agency, or entity responding to 311 service request. |
complaint_type | VARCHAR | YES | This is the first level of a hierarchy identifying the topic of the incident or condition. Complaint Type broadly describes the topic of the incident or condition and are defined by the responding agencies. |
descriptor | VARCHAR | YES | This is associated to the Complaint Type, and provides further detail on the incident or condition. Descriptor values are dependent on the Complaint Type, and are not always required in the service request. |
location_type | VARCHAR | YES | Describes the type of location used in the address information |
incident_zip | VARCHAR | YES | Zip code of the incident address |
incident_address | VARCHAR | YES | House number and street name of incident address |
street_name | VARCHAR | YES | Street name of incident address |
cross_street_1 | VARCHAR | YES | First Cross street based on the geo validated incident location. |
cross_street_2 | VARCHAR | YES | Second Cross Street based on the geo validated incident location |
intersection_street_1 | VARCHAR | YES | First intersecting street based on geo validated incident location |
intersection_street_2 | VARCHAR | YES | Second intersecting street based on geo validated incident location |
address_type | VARCHAR | YES | Type of information available about the incident location: Address; Block face; Intersection; LatLong; Placename |
city | VARCHAR | YES | In this dataset, City can refer to a borough or neighborhood. MANHATTAN, BROOKLYN, BRONX, STATEN ISLAND, or in QUEENS, specifc neighborhood name |
landmark | VARCHAR | YES | If the incident location is identified as a Landmark the name of the landmark will display here. Can refer to any noteworthy location, including but not limited to, parks, hospitals, airports, sports facilities, performance spaces, etc. |
facility_type | VARCHAR | YES | If applicable, this field describes the type of city facility associated to the service request: DSNY Garage, Precinct, School, School District, N/A |
status | VARCHAR | YES | Current status of the service request submitted: Assigned, Canceled, Closed, Pending |
due_date | TIMESTAMP | YES | Date when responding agency is expected to update the SR. This is based on the Complaint Type and internal Service Level Agreements (SLAs) |
resolution_description | VARCHAR | YES | Describes the last action taken on the service request by the responding agency. May describe next or future steps. |
resolution_action_updated_date | TIMESTAMP | YES | Date when responding agency last updated the service request. |
bbl | VARCHAR | YES | Parcel number that identifies the location of the building or property associated with the service request. The block is a subset of a borough. The lot is a subset of a block unique within a borough and block. |
borough | VARCHAR | YES | The borough number is: 1. Manhattan (New York County) 2. Bronx (Bronx County) 3. Brooklyn (Kings County) 4. Queens (Queens County) 5. Staten Island (Richmond County) |
x_coordinate_state_plane | VARCHAR | YES | Geo validated, X coordinate of the incident location. X coordinate of the incident location. For more information about NY State Plane Coordinate Zones: http://gis.ny.gov/gisdata/metadata/nysogs.statepln.html?nysgis= |
y_coordinate_state_plane | VARCHAR | YES | Geo validated, Y coordinate of the incident location. Y coordinate of the incident location. For more information about NY State Plane Coordinate Zones: http://gis.ny.gov/gisdata/metadata/nysogs.statepln.html?nysgis= |
open_data_channel_type | VARCHAR | YES | Indicates how the service request was submitted to 311: Phone, Online, Other (submitted by other agency) |
park_facility_name | VARCHAR | YES | If the incident location is a Parks Dept facility and service requests pertains to a facility managed by NYC Parks (DPR), the name of the facility will appear here |
park_borough | VARCHAR | YES | The borough of incident if the service request is pertaining to a NYC Parks Dept facility (DPR) |
vehicle_type | VARCHAR | YES | Data provided if service request pertains to a vehicle managed by the Taxi and Limousine Commision (TLC): Ambulette / Paratransit; Car Service; Commuter Van; Green Taxi |
taxi_company_borough | VARCHAR | YES | Data provided if service request pertains to a vehicle managed by the Taxi and Limousine Commision (TLC). |
taxi_pick_up_location | VARCHAR | YES | If the incident pertains a vehicle managed by the Taxi and Limousine Commision (TLC), this field displays the taxi pick up location |
bridge_highway_name | VARCHAR | YES | If the incident is identified as a Bridge/Highway, the name will be displayed here |
bridge_highway_direction | VARCHAR | YES | If the incident is identified as a Bridge/Highway, the direction where the issue took place would be displayed here. |
road_ramp | VARCHAR | YES | If the incident location was Bridge/Highway this column differentiates if the issue was on the Road or the Ramp. |
bridge_highway_segment | VARCHAR | YES | Additional information on the section of the Bridge/Highway were the incident took place. |
latitude | DOUBLE | YES | Geo based Latitude of the incident location in decimal degrees |
longitude | DOUBLE | YES | Geo based Longitude of the incident location in decimal degrees |
community_board | VARCHAR | YES | Community boards are local representative bodies. There are 59 community boards throughout the City, each representing a distinct geography. For more information on Community Boards: NYC government website |
To read from the sample_data
database, please refer to attach the sample datasets database
Example queries
The most common complaints in 2018
SELECT
UPPER(complaint_type),
COUNT(1)
FROM sample_data.nyc.service_requests
WHERE DATE_PART('year', created_date) = 2018
GROUP BY 1
HAVING COUNT(*) > 1000
ORDER BY 2 DESC;