Description

Service Requests for 2022, generated through Metro311's reporting system. For over 30 years Metro311 has been the Louisville Metro customer service center. Metro311 is contacted with a question or concern. Questions are answered and denoted into the reporting system as a Non-Service Request (NSR). For concerns, a Service Request (SR) is entered into the system and based on the information provided, routed to the appropriate agency. The responsible agency handling the request will receive the report and inspect or investigate per their protocols. A SR number is generated and can be utilized to track the concern.

The city o f Louisville adheres to the Open311.org Data Standards

Data Dictionary
field name
field description
service_request_id
The unique ID of the concern created by the system.
requested_datetime
The date and time the SR was made.
probyear
The year the SR was made.
updated_datetime
The date and time the SR was last modified
closed_date
The date the SR was closed. This information only applies to the SR, not the associated cases or work orders. Responding agencies utilize cases or work orders for their investigations.
status_description
An indicator of the current state of the SR.
status_notes
This info is dynamic and will change as the responsible agency denotes.
source
How the SR was received.
service_name
The name of the SR type
description
A description of the SR submitted.
agency_responsible
The agency responsible for addressing the SR.
address
The location of the concern.
longitude
Longitude of the location, using the WGS84 projection.
latitude
Latitude of the location, using the WGS84 projection.
zip_code
Zip code of the location
council_district
council district of the location

Name	Format	Description	Link
	21		https://louisville-metro-opendata-lojic.hub.arcgis.com/datasets/LOJIC::louisville-metro-ky-metro-311-service-requests-2022-1
	3		https://services1.arcgis.com/79kfd2K6fskCAkyg/arcgis/rest/services/metro_call_311_service_requests_2022/FeatureServer/0
	8		https://louisville-metro-opendata-lojic.hub.arcgis.com/api/download/v1/items/13b8f65917ba45ceb1bae52cf64b428e/csv?layers=0
	57		https://louisville-metro-opendata-lojic.hub.arcgis.com/api/download/v1/items/13b8f65917ba45ceb1bae52cf64b428e/shapefile?layers=0
	15		https://louisville-metro-opendata-lojic.hub.arcgis.com/api/download/v1/items/13b8f65917ba45ceb1bae52cf64b428e/geojson?layers=0
	25		https://louisville-metro-opendata-lojic.hub.arcgis.com/api/download/v1/items/13b8f65917ba45ceb1bae52cf64b428e/kml?layers=0

field name	field description
service_request_id	The unique ID of the concern created by the system.
requested_datetime	The date and time the SR was made.
probyear	The year the SR was made.
updated_datetime	The date and time the SR was last modified
closed_date	The date the SR was closed. This information only applies to the SR, not the associated cases or work orders. Responding agencies utilize cases or work orders for their investigations.
status_description	An indicator of the current state of the SR.
status_notes	This info is dynamic and will change as the responsible agency denotes.
source	How the SR was received.
service_name	The name of the SR type
description	A description of the SR submitted.
agency_responsible	The agency responsible for addressing the SR.
address	The location of the concern.
longitude	Longitude of the location, using the WGS84 projection.
latitude	Latitude of the location, using the WGS84 projection.
zip_code	Zip code of the location
council_district	council district of the location