| - Full Metadata - | - View Attributes - | - View Sample - | - Get Data - |
This page last updated: 04/06/2007
Metadata created using Minnesota Geographic Metadata Guidelines
| Originator | Minnesota Department of Transportation (MNDOT) | |||
| Abstract | The regional bikeways dataset was created by the Minnesota Dept of Transportation (MNDOT) in 2003. It has been maintained and updated by the Land Management Information Center (LMIC) through contract with the Metropolitan Council. Dataset includes bicycle routes within nine Twin Cities metropolitan counties: Anoka, Carver, Chisago, Dakota, Hennepin, Ramsey, Scott, Washington, and Wright. The bikeways are from a number of sources including the Metro Bicycle Network map book (2001), supplemented by information from maps published by city, state, county and regional government agencies, and city and county planning maps. The map shows on-road and off-road bikeways, proposed and existing bikeways, and includes bike lanes, bike-able road shoulders, and trails. The majority of the bikeways follow road centerlines of the MNDOT BaseMap 2002-Roads. A description of the bikeways attributes and sources of data are included in Section 5 of this document - Entity and Attribute Overview. |
|||
| Browse Graphic | View a sample of the data. | |||
| Time Period of Content Date | 04/06/2007 | |||
| Currentness Reference | The bikeways maps for the nine-county metro area represent route information from 2001 to 2007. The initial bikeways data set was digitized in 2003. Additional bikeways were digitized 2004 through 2007. MNDOT BaseMap road centerlines were used for the location of the majority of bikeways. MNDOT did the original digitization of road centerlines during the 1990-1995 time period. Roads were updated in January 2001 and again in 2002 using the most up-to-date available information. MNDOT BaseMap centerline information varies in currentness for the nine counties. For example, Washington was updated in 2003, Hennepin and Ramsey were updated in 2004. Bikeways were identified and classified based on the information from the following sources: The Metro Bicycle Network Map Book: 2001-02 City comprehensive plans and bike maps: variable through 2006 County bike data: variable through 2003 Published maps: variable Aerial Express color commercial aerial photography: 2002 Farm Service Agency air photos: Summer 2003 National Geospatial-Intelligence Agency air photos for St. Paul/Minneapolis: Spring 2004 |
|||
| Access Constraints | None | |||
| Use Constraints | None | |||
| Distributor Organization | Metropolitan Council | |||
| Ordering Instructions | This dataset is distributed on the internet by clicking below after 'Online Linkage'. Doing so will tell your browser to download a 'ZIP' file which will contain the following: - ArcView shape files - metadata for the dataset (.htm) - NOTICE.RTF, an important notice about this dataset that can be read by any word processing software. Additionally, this dataset is available for direct use via one or more map services. More information about what a web mapping service is can be found at http://www.datafinder.org/services/ . The specific map service and layer name for this dataset can be found by clicking the blue or green boxes under the map service column of the DataFinder Catalog at http://www.datafinder.org/catalog/ . |
|||
| Distribution Liability | NOTICE: The Geographic Information System (GIS) Data to which this notice is attached are made available pursuant to the Minnesota Government Data Practices Act (Minnesota Statutes Chapter 13). THE GIS DATA ARE PROVIDED TO YOU AS IS AND WITHOUT ANY WARRANTY AS TO THEIR PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. The GIS Data were developed by the Metropolitan Council for its own internal business purposes. The Metropolitan Council does not represent or warrant that the GIS Data or the data documentation are error-free, complete, current, or accurate. You are responsible for any consequences resulting from your use of the GIS Data or your reliance on the GIS Data. You should consult the data documentation for this particular GIS Data to determine the limitations of the GIS Data and the precision with which the GIS Data may depict distance, direction, location, or other geographic features. If you transmit or provide the GIS Data (or any portion of it) to another user, it is recommended that the GIS Data include a copy of this disclaimer and this metadata. | |||
| Online Linkage | I AGREE to the notice in "Distribution Liability" above. Clicking to agree will begin the download process (See Ordering Instructions above for details.) | |||
Go to Section:
1. Identification Information
2. Data Quality Information
3. Spatial Data Organization Information
4. Spatial Reference Information
5. Entity and Attribute Information
6. Distribution Information
7. Metadata Reference Information
| Section 1 | Identification Information | Top of page | ||
| Originator | Minnesota Department of Transportation (MNDOT) | |||
| Title | Bikeways | |||
| Abstract | The regional bikeways dataset was created by the Minnesota Dept of Transportation (MNDOT) in 2003. It has been maintained and updated by the Land Management Information Center (LMIC) through contract with the Metropolitan Council. Dataset includes bicycle routes within nine Twin Cities metropolitan counties: Anoka, Carver, Chisago, Dakota, Hennepin, Ramsey, Scott, Washington, and Wright. The bikeways are from a number of sources including the Metro Bicycle Network map book (2001), supplemented by information from maps published by city, state, county and regional government agencies, and city and county planning maps. The map shows on-road and off-road bikeways, proposed and existing bikeways, and includes bike lanes, bike-able road shoulders, and trails. The majority of the bikeways follow road centerlines of the MNDOT BaseMap 2002-Roads. A description of the bikeways attributes and sources of data are included in Section 5 of this document - Entity and Attribute Overview. |
|||
| Purpose | The Bicycle and Pedestrian Section, Office of Transit, developed the electronic bikeways map and GIS database to fill the need for a comprehensive inventory of bicycle routes in the Twin Cities metro area. The bike route data layer represents an interconnected regional network of bikeways that meet basic standards as developed by the Metro Bikeway Mapping Advisory Committee and helps to meet the region's goal of increased and safe transportation options. The map will serve to show existing inventory of bikeways and identify cost-effective bicycle infrastructure opportunities that will interface with local projects. The goal is to provide planning guidance to build a bicycle transportation network for the Twin Cities metro area. |
|||
| Time Period of Content Date | 04/06/2007 | |||
| Currentness Reference | The bikeways maps for the nine-county metro area represent route information from 2001 to 2007. The initial bikeways data set was digitized in 2003. Additional bikeways were digitized 2004 through 2007. MNDOT BaseMap road centerlines were used for the location of the majority of bikeways. MNDOT did the original digitization of road centerlines during the 1990-1995 time period. Roads were updated in January 2001 and again in 2002 using the most up-to-date available information. MNDOT BaseMap centerline information varies in currentness for the nine counties. For example, Washington was updated in 2003, Hennepin and Ramsey were updated in 2004. Bikeways were identified and classified based on the information from the following sources: The Metro Bicycle Network Map Book: 2001-02 City comprehensive plans and bike maps: variable through 2006 County bike data: variable through 2003 Published maps: variable Aerial Express color commercial aerial photography: 2002 Farm Service Agency air photos: Summer 2003 National Geospatial-Intelligence Agency air photos for St. Paul/Minneapolis: Spring 2004 |
|||
| Progress | In work | |||
| Maintenance and Update Frequency | To be determined | |||
| Spatial Extent of Data | Anoka County, Carver County, Chisago County, Dakota County, Hennepin County, Ramsey County, Scott County, Washington County, Wright County | |||
| Bounding Coordinates | -94.50 -92.70 45.80 44.40 |
|||
| Place Keywords | Minnesota, Minneapolis, St. Paul, Anoka, Carver, Chisago, Dakota, Hennepin, Ramsey, Scott, Washington, Wright, Twin Cities | |||
| Theme Keywords | Transportation, Bicycle facility, bikepath, bikeway, bike route, trail, trails, bike trails, bike paths, recreation, biking, cycling | |||
| Theme Keyword Thesaurus | ||||
| Access Constraints | None | |||
| Use Constraints | None | |||
| Contact Person Information | David Vessel,
Transportation Planner Metropolitan Council 390 Robert St North St. Paul, MN 55101-1805 Phone: 651-602-1646 FAX: 651-602-1739 E-mail: david.vessel@metc.state.mn.us | |||
| Browse Graphic | View a sample of the data. | |||
| Browse Graphic File Description | Map of 9 county area showing Bikeways layer | |||
| Associated Data Sets | Regional Trails |
|||
| Section 2 | Data Quality Information | Top of full metadata | Top of page | |
| Attribute Accuracy | Variable. Existing and proposed trails were attributed according to source information, which vary in accuracy and currentness. Many attributes were unknown and so were left blank. During bikeway digitization, the Metro Bicycle Network (MBN) map book was used as the primary source for bike route entry where associated information from the MBN was assigned to each bikeway. Other map sources were used for substantiation. In addition, city and county data were used to corroborate and/or update the MBN layer. Datasets will be sent to individual cities for review and correction as the mapping continues. LMIC converted the data set to a geodatabase format with constrained picklists for many attributes; this change will help to standardize future updates. NOTE: A single line may represent either an on-street bikeway or an off-street bikeway or both. Both single and/or multiple bikeways that follow the same road centerline are represented by a single line and are distinguished by attribute code values - see Entity and Attribute Section. |
|||
| Logical Consistency | The arcs were not created to support network analysis. Most bikeway arcs are unbroken where they cross roads, however, some areas, such as the city of Woodbury, broke the bikeway arc where it crossed a road. | |||
| Completeness | The bikeways layer is complete in that there are bicycle route data recorded for each of the nine metropolitan counties. To the extent that all existing bikeways have been located and included, the dataset is incomplete. Data current to April 2007 (for specific municipalities); bikeways will be updated as new/corrected information is made available. |
|||
| Horizontal Positional Accuracy | Trails are aligned to MNDOT BaseMap Roads where appropriate. The positional accuracy of the data set has not been tested under the National Standards for Spatial Data Accuracy. Trails were placed according to source information, which varied in accuracy. Location accuracy for most of the bikeways depends on the location accuracy of the road centerlines. MNDOT derived the road centerline features from USGS 7.5-minute quadrangles and their accuracy cannot be assumed to exceed National Map Accuracy Standards for 1:24,000 scale maps (+/- 40 feet or 12 meters). If an off-street bikeway followed along road centerlines within proximity of approximately 10-50 feet of the road centerline, the centerline was used as the source. |
|||
| Vertical Positional Accuracy | Not applicable | |||
| Lineage | Processing steps: Phase 1 Metropolitan Bikeways Network maps were created in 2000-2002 by having city and county staff representatives code streets on a laminated street map by placing colored tape on streets or parks where some form of bike route was known. Phase 2 The Bikeways data layer was digitized in 2003 from the Metropolitan Bikeways Network (MBN) using ArcView 3.2 and the Bikeways Extension. MNDOT staff developed this extension. It is a tool for automating the bikeways creation procedure. Bikeways were digitized using two methods: a) bikeways identified on the MBN (or city or county-supplied maps) were digitized by selecting the road centerline and the Bikeways extension entered it into the database; b) heads-up digitization was employed when a bikeway did not follow a road centerline. Background aerial photography was used to place the bikeway alignment as close to the source data as possible. Bikeways were located on the most current version of MNDOT road centerlines and converted in a separate layer using the MNDOT Bikeway mapping tool. Each line segment was coded to reflect the bikeway classification type, its position in relation to the road, if known, and the source of information. Primarily existing bikeways were entered during this phase. Phase 3 In 2004 digitization continued in the manner described above, with 'proposed' bikeways being entered in addition to 'existing'. Phase 4 The Land Management Information Center updated the data set for the following cities, townships and county: Albertville, Brooklyn Park, Buffalo, Burns Township, Deephaven, Edina, Excelsior, Medicine Lake, Monticello, Mounds View, Oakdale, Vadnais Heights, White Bear Township, Washington County and Woodbury. Phase 5 In late 2006, LMIC updated the dataset. Cities added or updated: Clearwater, Corcoran, Delano, Hastings, Hugo, Minneapolis, Otsego, Rockford, St. Louis Park, St. Michael, St. Paul, Wayzata, Three Rivers District. Phase 6 In early 2007, Minneapolis and Ramsey County data were updated. Source Materials: 1. Bikeways locations and attributes came from the cities and townships. For Brooklyn Park, Eden Prairie and Woodbury, the source data was submitted as shapefiles; for the remaining updated areas, the source data was submitted as printed maps or PDFs. The date that the map was received from each city or township is recorded in the DATE attribute. 2. Farm Service Agency natural color, 1-meter air photos, summer 2003, were available for the entire 9-county area. http://www.lmic.state.mn.us/chouse/airphoto_usda.html#fsa 3. National Geospatial-Intelligence Agency natural color, 0.3-meter air photos, spring 2004, were available for the St. Paul/Minneapolis city area. http://www.lmic.state.mn.us/chouse/airphoto_usgs.html#high-res 4. Communities that responded to 4/8/05 request for information. Anoka County: Burns Township - PDF Hennepin County: Brooklyn Park - Shapefile Deephaven - Paper map Eden Prairie -Shapefile Edina - Paper map Excelsior Medicine Lake - Paper map Ramsey County: Mounds View - Paper map Vadnais Heights - PDF White Bear Township - Paper map Washington County: Oakdale - PDF Woodbury - Shapefile Wright County: Albertville - Paper map Buffalo - DWG Cokato Monticello - Paper map South Haven - No bikeways 5. Bikeways in all updated cities, except St. Paul, were added by digitizing from a map submitted in PDF form. St. Paul submitted a bikeways shapefile. Aerial Photos (2004 National Geospatial-Intelligence Agency (NGA) 1 foot and 2003 National Agriculture Imagery Program (NAIP) 1 meter images) were used as references. 6. Minneapolis and Ramsey County submitted shapefiles which were transferred into the existing bikeways dataset. Data and attributes were verified. The addition of Ramsey County data corrupted some planned/proposed St. Paul bikeways. Metropolitan Council staff verified segments within St. Paul against existing and planned St. Paul bikeways files from 2006. Data is correct as of April 2007. Processing Steps: Shapefiles: All the arcs that were not already included in the Bikeways data set were copied and pasted into the data set. The lines were not altered, however, NGA air photos were used to determine whether the trails were paved or unpaved if that attribute was not specified in the submitted shapefile. Maps: Printed maps were scanned and georectified using ArcGIS software. Bikeways were then digitized using air photos (either FSA 2003 or NGA 2004); if a bikeway was not visible on the photos (usually in the case of proposed trails), then the line was digitized from the georeferenced map image. Trails along roadways follow MNDOT road line segments; the Trace tool was used to follow the segments exactly. Near the end of the project, the data was converted from shapefiles to an ArcGIS 8.3 geodatabase with constrained picklists in order to standardize entry of many of the attributes. |
|||
| Source Scale Denominator | ||||
| Section 3 | Spatial Data Organization Information | Top of full metadata | Top of page | |
| Native Data Set Environment | ArcGIS 8x | |||
| Geographic Reference for Tabular Data | ||||
| Spatial Object Type | Vector | |||
| Vendor Specific Object Types | Arc, Node | |||
| Tiling Scheme | 9-county region | |||
| Section 4 | Spatial Reference Information | Top of full metadata | Top of page | |
| Horizontal Coordinate Scheme | UTM | |||
| Ellipsoid | GRS80 | |||
| Horizontal Datum | NAD83 | |||
| Horizontal Units | Meters | |||
| Distance Resolution | ||||
| Altitude Datum | Not applicable | |||
| Depth Datum | Not applicable | |||
| UTM Zone Number | 15 | |||
| Section 5 | Entity and Attribute Information | Top of full metadata | Top of page | |
| Entity and Attribute Overview | Bikeways arcs are coded for Source, Side, Type, Jurisdiction, Active |
| Entity and Attribute Detailed Citation | Bikeway Attributes: SOURCE - 20 character string * Sample Values: MNDOT Bike Map Book, County (or county name), City (or city name), Township name, or Aerial Photo. SIDE - 13 character string * Both * North or East * South or West * Unknown * NA. TYPE - 50 character string * Paved Trail - Paved, off-street, 8 feet or more in width. * Non-paved Trail - Off-street, 8 feet or more in width, packed gravel, crushed limestone or natural. * Bike Lane - On-street, designated, 4 feet or more in width, with striped lane, bike symbol, and signs noting for bikes only. * Paved Shoulder >= 5 feet - Paved, 5 feet to 8 feet in width, not including gutter width, parking prohibited OR 8 feet or greater in width not including gutter width, parking allowed. * Low Volume Road with Shoulder < 5 feet - County roads only, 1000 AADT or less. Road with paved shoulder less than 5 feet, or no shoulder. * US/State Road with Paved Shoulder >= 5 feet - MNDOT roads only, 10,000 AADT or less. Paved shoulder 5 feet or more in width, not including gutter width, Parking prohibited or 8 feet or greater in width not including gutter width, parking allowed. * Paved Trail, one way direction - One-way. Paved, off-street, 8 feet or more in width. * Non-paved Trail, one way direction - One-way. Off-street, 8 feet or more in width, packed gravel or crushed limestone. * Bike Lane, one way direction - One-way. On-street, designated, 4 feet or more in width, with striped lane, bike symbol, and signs noting for bikes only. * Paved Shoulder >= 5 feet, one way direction - One-way. Paved shoulder 5 feet to 8 feet in width, not including gutter width, parking prohibited OR 8 feet or greater in width, not including gutter width, parking allowed. * Low Volume Road with Paved Shoulder < 5 feet, one way direction - County roads only, 1000 AADT or less. One-way. Road with paved shoulder less than 5 feet, or no shoulder. * US/State Road with Paved Shoulder >= 5 feet, one way direction - MNDOT roads only, 10,000 AADT or less. One-way. Paved shoulder 5 feet or more in width, not including gutter width, Parking prohibited or 8 feet or greater in width not including gutter width, parking allowed. * Other - * Sub-Standard - JURISDICTI - 10 character string * Sample Values: City, County, Municipal, Regional, State, University, and Unknown. ACTIVE - 1 short integer * 0 = FALSE - proposed/planned trail * 1 = TRUE - existing trail. NOTES - 250 character string * Notes, comments or questions about the bikeway. NAME - 50 character string * Trail name. FAC_ID - 50 character string * Trail identification used by local administrator. MILES - 4 point float * Trail length in miles (to nearest 10th of mile). WIDTH - 2 short integer * Bike lane width in feet. DIRECTION - 10 character string * Bike lane direction ex. one way, two way. GRADE - 1 character string * Portion of bike lane increased grade (Y or N). SPEED - 2 short integer * Speed limit on bikeway in miles per hour (mph). FAC_QUAL - 50 character string * Quality of bikeway facilities ex. substandard. LIGHTED - 1 character string * Bikeway is lighted (Y or N). OPERATION - 50 character string * Hours of operation / dates open. PROPOSED - 1 character string * Proposed bikeway (Y or N) * Note: supersedes ACTIVE ARTERIAL - 1 character string * 'Y' - Main arterial bikeway 'N' - non-arterial bikeway CONN_GAP - 1 character string * Bikeway connector / gap (Y or N). A record with 'Y' designation is a non-bikeways segment added to complete / connect an arterial network. STOPS - 2 character string * Number of stops per mile (added 6/13/05). CLASS - 12 character string * Simplified bikeway classification: GAP, Paved Trail, Road, Trail, or blank ROAD_NAME - 35 character string * From MNDOT roads by county: STREET_NAM. ROAD_NUMB - 10 character string * From MNDOT roads by county: ROAD_NUM. ROAD_CODE - 2 character string * From MNDOT roads by county: CODE. ROAD_SPEED - 2 short integer * Road speed limit in miles per hour (mph). * 30 - 70 at five mile/hr increments ROAD_COMM - 1 character string * Heavy commercial traffic (Y or N). LANE_NUMB - 1 short integer * Number of lanes. * Sample Values*: 2, 3, 4, 5, 6 LANE_WIDTH - 3 short integer * Width of traffic lane in feet. * Sample Values*: 0 - 12 LANE_DIR - 10 character string * Lane direction ex. one way, two way. LANE_TYPE - 24 character string * Lane type ex. freeway, divided, channelized. SHLD_WIDTH - 4 single * Shoulder width. * Sample Values*: 0 - 16 SHLD_TYPE - 50 character string * Shoulder surface type ex. none, aggregate, bituminous. SHLD_RUMB - 1 character string * Shoulder rumble stripped (Y or N). SHLD_PARK - 24 character string * Shoulder motor vehicle parking ex. Unrestricted, No Parking - Anytime. SHLD_BUS - 1 character string * Shoulder bus only (Y or N). Shape_Length - ESRI Attribute - 8 double MAINTAINER - 35 character string * Maintaining Organization INSTALL_YR - 16 character string * Year of installation INSTALL_OR - 32 character string * Organization which installed bikeways SUITABLITIY - 24 character string * Suitability is composite of several attributes to derive a score of safety and ease of a bikeway. Attributes included may include: striping, traffic volumes, pavement conditions, traffic speed, lane width. In this data set SUITABILITY is incomplete. SHLD_DATE - 8 character date * Date of road shoulder installation. SHLD_PLOW - 3 character string * (Y or N) if shoulder is plowed clear. SHLD_DRAIN - 3 character string * (Y or N) if the shoulder has a drainage system. ROAD_AADT - 2 short * the measured annual average daily traffic of the road. ROAD_HCADT - 1 character string * Heavy Commercial Traffic (Y or N) SURF_TYPE - 25 character string * Surface Type - ex. Concrete, Gravel, Stone, Crushed Rock SURF_QUAL - 25 character string * Surface Quality - Critical, Excellent, Good, Poor, NULL Categories reflect perceived surface quality and are not decided with specific criteria. |
|||
| Section 6 | Distribution Information | Top of full metadata | Top of page | |
| Publisher | Metropolitan Council | |||
| Publication Date | Periodically revised | |||
| Contact Person Information | Mark Kotz GIS Database Administrator Metropolitan Council 390 Robert Street North St. Paul, MN 55101-1805 Phone: 651-602-1644 FAX: 651-602-1674 E-mail: mark.kotz@metc.state.mn.us |
|||
| Distributor's Data Set Identifier | Bikeways | |||
| Transfer Format Name | Shapefile | |||
| Transfer Format Version Number | ArcGIS 9x | |||
| Transfer Size | ||||
| Ordering Instructions | This dataset is distributed on the internet by clicking below after 'Online Linkage'. Doing so will tell your browser to download a 'ZIP' file which will contain the following: - ArcView shape files - metadata for the dataset (.htm) - NOTICE.RTF, an important notice about this dataset that can be read by any word processing software. Additionally, this dataset is available for direct use via one or more map services. More information about what a web mapping service is can be found at http://www.datafinder.org/services/ . The specific map service and layer name for this dataset can be found by clicking the blue or green boxes under the map service column of the DataFinder Catalog at http://www.datafinder.org/catalog/ . |
|||
| Distribution Liability | NOTICE: The Geographic Information System (GIS) Data to which this notice is attached are made available pursuant to the Minnesota Government Data Practices Act (Minnesota Statutes Chapter 13). THE GIS DATA ARE PROVIDED TO YOU AS IS AND WITHOUT ANY WARRANTY AS TO THEIR PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. The GIS Data were developed by the Metropolitan Council for its own internal business purposes. The Metropolitan Council does not represent or warrant that the GIS Data or the data documentation are error-free, complete, current, or accurate. You are responsible for any consequences resulting from your use of the GIS Data or your reliance on the GIS Data. You should consult the data documentation for this particular GIS Data to determine the limitations of the GIS Data and the precision with which the GIS Data may depict distance, direction, location, or other geographic features. If you transmit or provide the GIS Data (or any portion of it) to another user, it is recommended that the GIS Data include a copy of this disclaimer and this metadata. | |||
| Online Linkage | I AGREE to the notice in "Distribution Liability" above. Clicking to agree will begin the download process (See Ordering Instructions above for details.) | |||
| Section 7 | Metadata Reference Information | Top of full metadata | Top of page | |
| Metadata Date | 04/06/2007 | |||
| Contact Person Information | Rachel Wiken,
GIS Technician Metropolitan Council 390 Robert St North St. Paul, MN 55101-1805 Phone: 651-602-1572 FAX: 651-602-1739 E-mail: rachel.wiken@metc.state.mn.us |
|||
| Metadata Standard Name | Minnesota Geographic Metadata Guidelines | |||
| Metadata Standard Version | 1.2 | |||
| Metadata Standard Online Linkage | http://www.gis.state.mn.us/stds/metadata.htm | |||
This page last updated: 04/06/2007
