Readme
Updated 9 months ago
‧ Indexed 5 hours ago
311 Service Requests for Fiscal Year 2013 - 2014
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 that deal with streets and mobility such as street and pot hole repair are also very common. 311 also receives requests to address environmental issues such as water conservation and air quality complaints.
This dataset represents all Service Requests for the fiscal year time period of October 1, 2013 to September 30, 2014.
Columns
| Name | Socrata field name | Column name in sgr mount | Data type | Description |
|---|---|---|---|---|
| Lat Long Location (state) | lat_long_location_state | lat_long_location_state | Text | |
| Lat Long Location (city) | lat_long_location_city | lat_long_location_city | Text | |
| Lat Long Location (zip) | lat_long_location_zip | lat_long_location_zip | Text | |
| Unique Key | unique_key | unique_key | Text | Internal Key |
| Lat Long Location (address) | lat_long_location_address | lat_long_location_address | Text | |
| Lat Long Location | lat_long_location | lat_long_location | Point | Denotes a location point on a longitude line (perpendicular to the equator) and latitude line (parallel to the equator) |
| Y Coordinate | y_coordinate | y_coordinate | Number | Denotes a point where vertical (y axis) lines intersect on a map |
| X Coordinate | x_coordinate | x_coordinate | Number | Denotes a point where (x axis) horizontal lines intersect on a map |
| Method Received Description | method_received_description | method_received_description | Text | Mode in which 311 receives the request for service |
| Outcome | outcome | outcome | Text | Documents the action taken on a service request |
| Closed Date | closed_date | closed_date | Calendar date | Date the service request was completed |
| Update Date | update_date | update_date | Calendar date | Date the service request was last updated with new information or activity |
| Created Date | created_date | created_date | Calendar date | Date the service request was created |
| Overall Service Request Due Date | overall_service_request_due_date | overall_service_request_due_date | Calendar date | The service request and all activities should be completed by the listed date |
| ERT (Estimated Response Time) | ert_estimated_response_time | ert_estimated_response_time | Number | The time allotted for the initial inspection and/or assessment. (There may be variance from department to department concerning calendar versus business days.) |
| Service Request Type | service_request_type | service_request_type | Text | Type of complaint submitted by customer or service offered by the City |
| Department | department | department | Text | City Departments and Offices |
| City Council District | city_council_district | city_council_district | Number | Geographical borderlines for legislative representation throughout the city |
| Address | address | address | Text | Street Address |
| Service Request Number | service_request_number | service_request_number | Text | Unique ID given to each documented request for a city service; the first two digits designate the last two digits of the calendar year the service request was created (e.g., 16 = 2016) |
| Counties | :@computed_region_28rh_izyk | :@computed_region_28rh_izyk | Number | |
| Zip Codes | :@computed_region_3qur_xvie | :@computed_region_3qur_xvie | Number | |
| City Councils | :@computed_region_at43_7y52 | :@computed_region_at43_7y52 | Number | |
| Status | status | status | Text | Denotes whether a service request is currently being actively worked or has been resolved |
| Priority | priority | priority | Text | Denotes the precedence of how a service request will be handled |
Upstream Metadata