Readme
Updated 7 months ago
‧ Indexed 3 hours ago
311 Service Requests for Fiscal Year 2020 - 2021 Bulk
There are over 400 service requests types that are reported in the 311 system that affect the quality of life of our citizens, neighborhoods, and communities. The most popular service requests include but are not limited to animal services requests, high weeds, junk motor vehicles, and a number of other code compliance-related issues. Requests regarding streets and mobility (such as street and pot hole repair) are also common as well as requests to address environmental issues such as water conservation and air quality concerns.
This dataset represents all Service Requests related to bulk trash City code compliance violations for the fiscal year time period of October 1, 2020 to September 30, 2021.
Columns
| Name | Socrata field name | Column name in sgr mount | Data type | Description |
|---|---|---|---|---|
| UPDATED_DATE | updated_date | updated_date | Calendar date | The last date an update was made to the request |
| METHOD_RECEIVED_DESC | method_received_desc | method_received_desc | Text | Describes the method the service request was received (I.E. Phone, Web, Mobile Device, etc.) |
| CITY_COUNCIL_DISTRICT | city_council_district | city_council_district | Number | The number of the City Council District where the service will take place |
| CREATED_DATE | created_date | created_date | Calendar date | The date the service request was submitted |
| OUTCOME | outcome | outcome | Text | A brief statement describing the outcome of the request for service |
| STATUS | status | status | Text | Describes the status of the request for service (I.E. New, In Progress, Closed) |
| ADDRESS | address | address | Text | The location where the service will take place |
| OVERALL_SERVICE_REQUEST_DUE_DATE | overall_service_request_due | overall_service_request_due | Calendar date | The date the request the department must have the service request completed by for the request to be on time. Requests completed after this date are considered late. |
| DEPARTMENT | department | department | Text | The City Department responsible to responding to the request for service |
| CLOSED_DATE | closed_date | closed_date | Calendar date | The date the request was completed and closed |
| UNIQUE_KEY | unique_key | unique_key | Text | Internal Key |
| SERVICE_REQUEST_TYPE | service_request_type | service_request_type | Text | The type of service being requested |
| LAT_LONG_VALUE | lat_long_value | lat_long_value | Text | The numeric value of the location's latitude and longitude coordinates |
| ERT(ESTIMATED_RESPONSE_TIME) | ert_estimated_response_time | ert_estimated_response_time | Text | The estimated amount of time it will take the City Department to begin their investigation/response to the request for service |
| PRIORITY | priority | priority | Text | Describes the priorty of the request (Standard, Urgent, Dispatch, etc.) |
| ERT_MEASURED_IN | ert_measured_in | ert_measured_in | Text | Defines the increments of time the ERT is measured in (I.E. Hours, Calendar Days, Business Days, Etc.) |
| SERVICE_REQUEST_NUMBER | service_request_number | service_request_number | Text | Tracking number associated with a service request beginning with the last two digits of the year the service request was created. |
Upstream Metadata