If there are any issues with the data in this map, service, or shp file please contact the Minneapolis GIS office.

The attribute information for this layer includes links to the respective neighborhood associations. If there are questions regrading this data layer, you can either contact the City of Minneapolis Neighborhood & Community Relations office, or Minneapolis GIS.

This layer is a component of Natural resources interactive map.

The City of Minneapolis Police Department Precincts. For questions about this data please contact PoliceOpenData@minneapolismn.gov

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.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, stairways, and winter trails.

This data set includes all scooter trips for the month of October, within the City of Minneapolis for the pilot program that began in March 2019. 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: http://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: http://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.

This is the feature map service for the City of Minneapolis City Council Ward Boundaries that were redistricted and adopted in April of 2012. These boundaries took effect January 1, 2014.

This is the feature map service for the City of Minneapolis City Council Ward Boundaries that were redistricted and adopted on April 18th of 2002.

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 DescriptionsTripID: 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.

Vacant Building Categories: The City of Saint Paul requires a review of the sale of all vacant buildings. Requirements differ based on the category of vacancy. CATEGORY I: Payment of registration and fees Notify the City of new ownership Restore utilities and comply with orders for legal occupancy Obtain a Truth-in-Sale of Housing Report CATEGORY II (No sale without City approval): Registration of new ownership Payment of registration and fees Code compliance report Cost estimate from licensed contractor for all repairs A schedule for completion of the repairs Proof of financial capability to complete all repairs. CATEGORY III (No sale without City approval): No sale without a Certificate of Code Compliance or Certificate of Occupancy. For more information about Saint Paul's Vacant Building Program visit: https://www.stpaul.gov/departments/safety-inspections/rent-buy-sell-property/vacant-buildings/vacant-building-program

This data set includes all scooter trips for the month of July, within the City of Minneapolis for the pilot program that began in March 2019. 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: http://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: http://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.

Field DescriptionsTripID: a unique identifier for each trip created by the City of MinneapolisTripDuration: trip time in secondsTripDistance: trip distance in metersStartTime: time the trip started, rounded to the nearest half hourEndTime: time the trip ended, rounded to the nearest half hourStartCenterlineID: 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-bikeStartCenterlineType: 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-bikeEndCenterlineType: The type of centerline the trip ended on, either street or trail.

The major water bodies within the Minneapolis city limits. Includes polygons for the Mississippi River, major lakes, and streams. If there are any issues with the data in this map, service, or shp file please contact the Minneapolis GIS office.

For questions about this data please contact FireOpenData@minneapolismn.govConfirmed fires in the City of Minneapolis for 2014 Year-to-date.

For questions about this data please contact FireOpenData@minneapolismn.govReported fires in the City of Minneapolis for 2013.

For questions about this data please contact FireOpenData@minneapolismn.govConfirmed fires in the City of Minneapolis for the year 2013.

Exterior boundary, Annexation boundary, and County boundary coverages are examined to remove all overshoots, unwanted intersections; insure polygons are closed; and to see that there are no missing or duplicate polygon labels. Each symbolic layer is individually examined for completeness. There is no line duplication in exterior or annexation coverages. MCD's with detached or non-contiguous units (polygons) have the same polygon link/label code in each of their units. Completeness in the checking process is examined through the examination and comparison of all detail collected by County Staff. Sources used included: City Clerks, County Auditor's Office, Washington County Historical Courthouse, MN State Historical Society, Secretary of State, Minnesota Municipal Board, and MNDOT. https://www.co.washington.mn.us/1609/Municipal-Boundaries

About this itemUsing a few studies gathered by a contracted research team, I have created a Dashboard application that effectively shows the data collected about the pavement conditions of the bikeways and city streets in Blaine, MN. By looking towards the bottom of the screen, there are arrows that can be used to view the heavily arcade and HTML coded lists. Each list is selectable and will zoom to the specific selection on the map, and bring up a pop-up complete with the relevant attribute information. The list also is stylized to change as the PCI Score changes categories. On the header of the dashboard there are filter sliders that can filter out a range of scores from the map, lists, and overview statistics. The vector tile basemap used in this App was created by me while employed at the City of Blaine as a GIS intern. Roads not highlighted in the study can be selected and see a popup that tells the user that the "road was not included within the survey", and who it is owned by.Author/ContributorJohn RoeteringOrganizationCity of BlaineOrg Websitewww.blaine.mn.gov