AndreaBozzo/ceres-open-data-index huggingface dataset:
Scooter and Bike Availability 2024

Field Descriptions PollTime: The time the API was polled for a snapshot of available vehicles CompanyName: The name of the company polled NumberAvailable: The number of vehicles available on the street or trail centerline ID at poll time according to recent vehicle status ClosestCenterlineID: the closest street centerline GBSID or trail centerline Feature Unique ID. Refer to the Street Centerline dataset here: [https://opendata.minneapolismn.gov/datasets/mpls-centerline], and the trail centerline dataset here: [https://gisdata.mn.gov/dataset/us-mn-state-metrogis-trans-metro-colabtiv-trails-bike] ClosestCenterlineType: The type of centerline, either street or trail Neighborhood: The neighborhood the vehicle was located in
Motorized Foot Scooter and eBike Trips 2024

Field Descriptions TripID: a unique identifier for each trip created by the City of Minneapolis TripDuration: trip time in seconds TripDistance: trip distance in meters StartTime: time the trip started, rounded to the nearest half hour EndTime: time the trip ended, rounded to the nearest half hour StartCenterlineID: the street centerline GBSID or trail centerline Feature Unique ID the trip started on. Refer to the Street Centerline dataset here: [https://opendata.minneapolismn.gov/datasets/mpls-centerline], and the trail centerline dataset here: [https://gisdata.mn.gov/dataset/us-mn-state-metrogis-trans-metro-colabtiv-trails-bike] StartCenterlineType: The type of centerline the trip started on, either street or trail
Snow_Emergency_Bridge_Tags_2025

This is the information about the number and location of tags (parking tickets) during this snow emergency. Tag data will be retained for all Snow Emergencies in each snow season, until there is five full seasons of snow emergencies. Disclaimer: At this point we only have the tag data enclosed for day 2 and day 3 the snow emergencies. Day 1 tag data is collected manually and is not available at this time electronically.
Snow_Emergency_Glenwood_Tows_2025

This is the information about the number and location of tows during this snow emergency. Tow data will be retained for all Snow Emergencies in each snow season, until there is five full seasons of snow emergencies. Disclaimer: There is an expected address error rate of between 8 and 14 percent. Snow Emergency Tows – 2025/2026 Season #2 Glenwood (12/10/25 thru 12/12/25)
Snow_Emergency_Omega_Tows_2025

This is the information about the number and location of tows during this snow emergency. Tow data will be retained for all Snow Emergencies in each snow season, until there is five full seasons of snow emergencies. Disclaimer: There is an expected address error rate of between 8 and 14 percent. Snow Emergency Tows – 2022/2023 Season #2 Omega (2/8/25 thru 2/10/25)
Snow_Emergency_Omega_Tags_2025

Snow Emergency Tags – 2024/2025 Season #2 Omega (2/8/25 thru 2/10/25) This is the information about the number and location of tags (parking tickets) during this snow emergency. Tag data will be retained for all Snow Emergencies in each snow season, until there is five full seasons of snow emergencies. Disclaimer: At this point we only have the tag data enclosed for day 2 and day 3 the snow emergencies. Day 1 tag data is collected manually and is not available at this time electronically.
Snow_Emergency_Glenwood_Tags_2025

This is the information about the number and location of tags (parking tickets) during this snow emergency. Tag data will be retained for all Snow Emergencies in each snow season, until there is five full seasons of snow emergencies. Disclaimer: At this point we only have the tag data enclosed for day 2 and day 3 the snow emergencies. Day 1 tag data is collected manually and is not available at this time electronically. Snow Emergency Tags – 2025/2026 Season #2 Glenwood (12/10/25 thru 12/12/25)
Snow_Emergency_Jefferson_Tags_2025

This is the information about the number and location of tags (parking tickets) during this snow emergency. Tag data will be retained for all Snow Emergencies in each snow season, until there is five full seasons of snow emergencies. Disclaimer: At this point we only have the tag data enclosed for day 2 and day 3 the snow emergencies. Day 1 tag data is collected manually and is not available at this time electronically. Snow Emergency Tags – 2025/2026 Season #3 Jefferson (12/28/25 thru 12/30/25)
Public_311_2023

The data set is refreshed on a daily basis by 10:45 PM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
Police_Use_of_Force_Legacy

Disclaimer: *Please note that the responseDate is shown in UTC time, not local time. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
Fires_Reported_2023

The data set is refreshed on a daily basis by 10:45 PM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
Fires_Confirmed_2023

The data set is refreshed on a daily basis by 10:45 PM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
Fires_Confirmed_2022

The data set is refreshed on a daily basis by 10:45 PM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
Public_311_2022

The data set is refreshed on a daily basis by 10:45 PM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
Structural_Fires

*This is service is temporarily paused as the City is implementing a new reporting system. The data set is refreshed on a weekly basis on Fridays at 2:45 AM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
MPLS_Centerline

This centerline file is maintained by the GIS Office at the City of Minneapolis. These centerlines represent the center of pavement for all of the drivable streets in the City. The data set is refreshed on the last Friday of the month at 7:30 PM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
Off_Sale_Liquor

The data set is refreshed on the last Friday of the month at 7:30 PM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
On_Sale_Liquor

The data set is refreshed on the last Friday of the month at 7:30 PM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
NEIGHBORHOOD_CRIME_STATS

In February 2019, we updated the neighborhood assignment with regards to the new police record system. The data set is refreshed on the third day of the month at 8:45 AM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
Motorized Scooter and eBike Trips 2025

Field Descriptions TripID: a unique identifier for each trip created by the City of Minneapolis TripDuration: trip time in seconds TripDistance: trip distance in meters StartTime: time the trip started, rounded to the nearest half hour EndTime: time the trip ended, rounded to the nearest half hour StartCenterlineID: the street centerline GBSID or trail centerline Feature Unique ID the trip started on. Refer to the Street Centerline dataset here: [https://opendata.minneapolismn.gov/datasets/mpls-centerline], and the trail centerline dataset here: [https://gisdata.mn.gov/dataset/us-mn-state-metrogis-trans-metro-colabtiv-trails-bike] StartCenterlineType: The type of centerline the trip started on, either street or trail
Scooter and Bike Availability 2025

PollTime: The time the API was polled for a snapshot of available vehicles CompanyName: The name of the company polled NumberAvailable: The number of vehicles available on the street or trail centerline ID at poll time according to recent vehicle status ClosestCenterlineID: the closest street centerline GBSID or trail centerline Feature Unique ID. Refer to the Street Centerline dataset here: [https://opendata.minneapolismn.gov/datasets/mpls-centerline], and the trail centerline dataset here: [https://gisdata.mn.gov/dataset/us-mn-state-metrogis-trans-metro-colabtiv-trails-bike] ClosestCenterlineType: The type of centerline, either street or trail Neighborhood: The neighborhood the vehicle was located in
Officer_Conduct_Data

For questions about this data please contact [OpenData_IT@minneapolismn.gov] Column Descriptions Plaintiff – The name of the involved party Jurisdiction – the location the legal action occurred - Hennepin County District Court is under the laws of Minnesota - US District Court is under federal law Civil Process – the nature of the legal process - The City and the Plaintiff resolve claims - The Courts watch over Litigation Description – how the matter was resolved Lawsuit Settlement = the parties agreed to the payout amount before a trial is done Lawsuit Judgement = the payout amount was decided by a judge or jury Incident Date – the date of the event leading to the legal action Date Opened – the date the City Attorney’s office opens a file for the case Payout Date – the date the City pays the Plaintiff after the City Council officially approves the payout.
Active_Rental_Licenses

The data set is refreshed on a weekly basis on Fridays at 2:45 AM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
EAS_Addresses

The data set is refreshed on a weekly basis on Fridays at 2:45 AM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
Building_Inspection_Districts

The data set is refreshed on a weekly basis on Fridays at 2:45 AM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
HPC_Districts

The data set is refreshed on a weekly basis on Fridays at 2:45 AM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
HPC_Landmarks

The data set is refreshed on a weekly basis on Fridays at 2:45 AM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
Planning_Zoning_Built_Form

Built form – this column is the name of the built form district Abbrv – this column is the abbreviation of the name of the district Built form district information: The Interior 1 district is typically applied in parts of the city farthest from downtown, in the areas between transit routes. The Interior 2 district is typically applied in parts of the city that developed during the era when streetcars were a primary mode of transportation, in the areas in between transit routes, and on select streets with intermittent local transit service. It is also applied adjacent to the Corridor 4 and Corridor 6 districts, serving as a transition to lower intensity residential areas. The Interior 3 district is typically applied in parts of the city closest to downtown, in the areas in between transit routes. It is also applied adjacent to select corridors and near METRO stations, serving as a transition to lower intensity residential areas. The Corridor 3 district is typically applied along transit routes farther from downtown that are on narrower rights-of-way, and serves as a transition between lower intensity residential areas and areas immediately surrounding METRO stations. The Corridor 4 district is typically applied along high frequency transit routes farther from downtown, that are on narrower rights-of-way, and on select streets with local transit service. It is also applied near downtown in areas between transit routes, and serves as a transition between lower intensity residential areas and areas immediately surrounding METRO stations. The Corridor 6 district is typically applied along high frequency transit routes as well as in areas near METRO stations. The Transit 10 district is typically applied along high frequency transit routes, adjacent to METRO stations, in neighborhoods near downtown, and in downtown. The Transit 15 district is typically applied along high frequency transit routes, adjacent to METRO stations, in neighborhoods near downtown, and in downtown. The Transit 20 district is typically applied along high frequency transit routes, adjacent to METRO stations, in neighborhoods near downtown, and in downtown. The Transit 30 district is typically applied along high frequency transit routes, adjacent to METRO stations, in neighborhoods near downtown, and adjacent to the downtown office core. The Core 50 district is applied in the downtown central business district. The district supports the office core as the center of the region's economy by allowing the largest building types in the city. The Production district is typically applied in areas of the city that are intended for the long-term preservation of production, transportation, and job generating uses. The Parks district is typically applied in areas with the Parks and Open Space future land use designation.
Planning_Zoning_Overlay

The data set is refreshed on a weekly basis on Fridays at 2:45 AM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
Planning_Primary_Zoning

The data set is refreshed on a weekly basis on Fridays at 2:45 AM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
Small_Area_Plans

The data set is refreshed on a weekly basis on Fridays at 2:45 AM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
Snow_Emergency_Routes

The data set is refreshed on a weekly basis on Fridays at 2:45 AM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
Food_Inspections

The data set is refreshed on a weekly basis on Fridays at 2:45 AM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
Crime_Data

Field Descriptions Crime Dashboard Document - https://www.minneapolismn.gov/government/government-data/datasource/crime-dashboard/crime-dashboard-document/ The data set is refreshed on a daily basis by 9:30 AM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
Police_Incidents_Last_2Years

Police Incidents for the last 2 years. The reportedDateTime field is shown in UTC. The data set is refreshed on a daily basis by 9:30 AM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.
Shots_Fired

The data set is refreshed on a daily basis by 9:30 AM. The website will reflect the last time the data set was updated and the total count of rows. The grid on the “Data” tab will display the up to date data. However, in certain situations there is a delay in the refresh of the downloadable data file. Sometimes the downloadable file does not reflect the updates to the data in the portal. After a delay (duration has been variable; up to 30 minutes), the file will be updated on the server and then downloads will include the updated data.