AndreaBozzo/ceres-open-data-index huggingface dataset:
Motorized Foot Scooter Trips 2020

This dataset includes all scooter trips for July – December within the City of Minneapolis for the pilot program in 2020. We have removed data when trips were over 7 hours and less than 0 miles or greater than 24 miles. 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. EndCenterlineID: the street centerline GBSID or trail centerline Feature Unique ID the trip ended 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] EndCenterlineType: The type of centerline the trip ended on, either street or trail.
Snow_Emergency_Newton_Tags_2020

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_Spruce_Tags_2020

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_James_Tags_2020

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_Oliver_Tags_2021

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_Newton_Tows_2020

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 – 2019/2020 Season #3 Newton (1/18/20 thru 1/20/20)
Snow_Emergency_Spruce_Tows_2020

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 – 2019/2020 Season #2 Spruce (2/9/20 thru 2/11/20)
Snow_Emergency_James_Tows_2020

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 – 2020/2021 Season #1 James (12/23/20 thru 12/25/20)
Snow_Emergency_Oliver_Tows_2021

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 – 2020/2021 Season #2 Oliver (1/24/21 thru 1/26/21)
Snow_Emergency_Ferry_Tags_2021

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_Ferry_Tows_2021

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 – 2021/2022 Season #1 Ferry (12/10/21 thru 12/12/21)
Scooter_Availability_2021

Field Descriptions PollTime: The time the API was polled for a snapshot of available scooters. CompanyName: The name of the company polled. NumberAvailable: The number of scooters available on the street or trail centerline ID at the time the API was polled. 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 centerline segment is located in.
Motorized_Foot_Scooter_Trips_2021

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. EndCenterlineID: the street centerline GBSID or trail centerline Feature Unique ID the trip ended 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] EndCenterlineType: The type of centerline the trip ended on, either street or trail.
Police_Incidents_2021

Police Incidents for 2021 from the Police Information Management System (PIMS). This data set is updated daily. *Please note that the responseDate is shown in UTC time, not local time. 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_2018_PIMS

Police Incidents for 2018 from the Police Information Management System (PIMS) starting in June 2018. The reportedDateTime field is shown in UTC. Field Descriptions * Begin Date: Date incident began. Time in the field is UTC not local, so a separate column is created for accurate time information. * Time: Begin date time field. * CCN: A concatenation of the 4 digit year in which the incident was created, followed by a dash and then a 6 digit number of sequence for the agency. The MP at the beginning signifies a report taken by Minneapolis Police. This is used because Minneapolis shares the record management system with the University of Minnesota Police * ControlNbr: A unique identifier for case. * Offense: Code of criminal act reported. * Description: Description of the criminal code of incident. * EnteredDate: The timestamp of when the incident was created in the system. * GBSID: The anonymized street centerline ID. * LastChanged: Date the record was last altered in system. * LastUpdateDate: Date the record was last moved to open data. * Lat: The anonymized latitude of the incident. * Long: The anonymized longitude of the incident. * Neighborhood: The neighborhood of the incident. Note that occasionally due to the anonymization process, if a point is on the boundary of a neighborhood, it may fall into either neighborhood. * OBJECTID: A unique identifier for open data portal. * Precinct: The police precinct of the incident. Note that occasionally due to the anonymization process, if a point is on the boundary of a precinct, it may fall into either precinct. * PublicAddress: Address of incident anonymized to the block. * ReportedDate: Date incident is reported to police. * UCRCode: Code that signifies the type of crime that was committed. * * 1 = MURDER * 3 = RAPE * 4 = ROBBERY * 5 = ASSAULT * 6 = BURGLARY * 7 = LARCENY * 8 = AUTO THEFT * 10 = ARSON
Snow_Emergency_Dover_Tags_2022

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_Jane_Tows_2022

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 Jane (12/15/22 thru 12/7/22)
Snow_Emergency_Jane_Tags_2022

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_Lourdes_Tags_2022

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_Northrop_Tows_2023

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 #4 Northrop (1/4/23 thru 1/6/23)
Snow_Emergency_Northrop_Tags_2023

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.
Police_Incidents_2022

Police Incidents for 2022 from the Police Information Management System (PIMS). This data set is updated daily. *Please note that the responseDate is shown in UTC time, not local time. 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.
Fires_Reported_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.
Snow_Emergency_Victory1_Tags_2023

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_Victory1_Tows_2023

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 #5 Victory1 (2/22/23 thru 2/24/23)
Snow_Emergency_Victory2_Tags_2023

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_Victory2_Tows_2023

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 #6 Victory2 (2/24/23 thru 2/24/23)
Motorized_Foot_Scooter_Trips_2022

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. EndCenterlineID: the street centerline GBSID or trail centerline Feature Unique ID the trip ended 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] EndCenterlineType: The type of centerline the trip ended on, either street or trail.
Scooter_and_Bike_Availability_2022

Field Descriptions PollTime: The time the API was polled for a snapshot of available scooters. CompanyName: The name of the company polled. NumberAvailable: The number of scooters available on the street or trail centerline ID at the time the API was polled. 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 centerline segment is located in.
Covid_Cases_Demographic

This dataset is no longer updated regularly. Last update was on 6/29/23. For additional information contact MHDepi@minneapolismn.gov. 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.
Covid_Cases_Geography

This dataset is no longer updated regularly. Last update was on 6/29/23. For additional information contact MHDepi@minneapolismn.gov. 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.
Covid_Cases

This dataset is no longer updated regularly. Last update was on 6/29/23. For additional information contact MHDepi@minneapolismn.gov. 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.
Hydrants

For questions about this dataset please contact PublicWorksOpenData@minneapolismn.gov The hydrant data is created using engineering drawings (as-builts), field measurements, GPS (survey shots-0.5 inch accuracy) or ortho photos (6 in accuracy). 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.
Police_Officer_Involved_Shootings

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.
Police_Incidents_2023

Police Incidents for 2023 from the Police Information Management System (PIMS). This data set is updated daily. *Please note that the responseDate is shown in UTC time, not local time. 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.
Motorized_Foot_Scooter_and_eBike_Trips_2023

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_2023

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
Snow_Emergency_Howard_Tags_2024

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_Howard_Tows_2024

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 – 2024/2025 Season #1 Howard (12/19/24 thru 12/21/24)