Statewide All Roads Layer Michigan Geographic Framework Field Definitions

Similar documents
Appendix D: Functional Classification Criteria and Characteristics, and MnDOT Access Guidance

Michigan Geographic Framework (MGF)

Functional Classification Comprehensive Guide. Prepared by

TRANSPORTATION IMPACT STUDIES

APPENDIX B. Public Works and Development Engineering Services Division Guidelines for Traffic Impact Studies

FAIRFAX COUNTY PARK-AND-RIDE DEMAND ESTIMATION STUDY

APPENDIX H: TRAVEL DEMAND MODEL VALIDATION AND ANALYSIS

PIMA COUNTY REGIONAL ACCESS MANAGEMENT PLAN (RAMP) LOCAL AND NON-LOCAL ACCESS MANAGEMENT PROGRAMS DELIVERABLE 1B

Authority: N.J.S.A. 27:1A-5, 27:1A-6 and 27:7-44.1, and 27:7-89 et seq., specifically 27:7-91. Expires on February 27, 2021.

NYSDOT Roadway Inventory. Both On and Off the State System

3.0 TRANSPORTATION AND CIRCULATION

1RUWKZHVW#:LFKLWD 0DMRU#,QYHVWPHQW#6WXG\

Woodburn Interchange Project Transportation Technical Report

Transit Signal Priority in the Denver Metro. Bart Przybyl, P.E., PTOE

The Folded Interchange: An Unconventional Design for the Reconstruction of Cloverleaf Interchanges

HB2 Implementation Policy Guide

The Policies section will also provide guidance and short range policies in order to accomplish the goals and objectives.

ROSEMOUNT TRANSPORTATION PLAN

NATMEC June 30, 2014 Anita Vandervalk, PE, PMP

Oregon Theodore R. Kulongoski, Governor

September Public Meetings. Developing a Blueprint for the Corridor

San Francisco Freeway Corridor Management Study (SF FCMS)

Preparing for the Future in Troup County, Georgia

CHAPTER 4 GRADE SEPARATIONS AND INTERCHANGES

TRAFFIC PROGRAM ACCESS MANUAL Edition WYDOT ACCESS MANUAL 0

Highway Functional Classification: Concepts, Criteria and Procedures TABLE OF CONTENTS

TRAFFIC STUDY GUIDELINES

FHWA Functional Classification Guidelines

Access Management Manual December 2003

Niagara s Transportation Strategy 1. Introduction:

HORIZON 2030: Plan Projects November 2005

PLAN 2040 Regional Transportation Plan Update. Final Recommendations. Transportation and Air Quality Committee March 13, 2014

MAP 21 Freight Provisions and Seaports

Technical Memorandum MULTIMODAL NEEDS. Prepared for: Oklahoma Department of Transportation. Prepared by:

Greenhouse Gas Emission Reduction Strategies

Transportation Improvement Program (TIP)

New Jersey Pilot Study

Tier 1 Recommendations October 30, 2017

GIS-BASED NON-SIGNALIZED INTERSECTION DATA INVENTORY TOOL TO IMPROVE TRAFFIC SAFETY

Most Frequently Asked Questions

FLORIDA DEPARTMENT OF TRANSPORTATION Planning and Environmental Management Office INTERCHANGE MODIFICATION REPORT

3.14 TRANSPORTATION AND TRAFFIC

500 Interchange Design

AMPO Annual Conference Session: Performance (Part 1) October 18, 2017 Savannah, GA

REGIONAL SOLICITATION ROADWAY APPLICATIONS: POTENTIAL CHANGES. TAB September 20, 2017

ATTACHMENT A. Detailed Study Scope. I-66 (Inside) Multi-modal Study Scope

MnDOT GREATER MN STAND ALONE NOISE BARRIER PROGRAM

2030 Transportation Policy Plan SUMMARY PRESENTATION. Land Use Advisory Committee November 15, 2012

Cass County Soil Erosion & Sedimentation Control Program

CITY OF CLOVIS Traffic Impact Study Guidelines

ITEM 8 Action May 17, 2017

TABLE OF CONTENTS SECTION

WELCOME IL 47. Community Advisory Group Meeting #5 Waubonsee Community College Wednesday, May 31, 2017

Jacksonville Urban Area Metropolitan Planning Organization LONG RANGE TRANSPORTATION PLAN. Draft

INTERACTIVE HIGHWAY SAFETY DESIGN MODEL (IHSDM)

Roadway Data Extraction Technical Assistance Program (RDETAP) Traffic Safety Conference College Station, June 2016

LMPO 2040 Metropolitan Transportation Plan. Table of Contents

Critical Rural and Urban Freight Corridors August 2016

Canadian Guidelines for Establishing Posted Speed Limits

TRANSPORTATION IMPACT ANALYSIS GUIDELINES

CITY OF AMES, IOWA ADMINISTRATIVE PROGRAM FOR STREET NAMING AND ADDRESSING

Tri-Cities Transportation Study Area Congestion Management System Operations Plan

CODE CONSOLIDATION PHASE II SUMMARY OF CHANGES Effective February 1, 2011, Ordinance s

The Secrets to HCM Consistency Using Simulation Models

Part 11: Lighting. Contents. Tables. Part 11: Lighting. Christchurch City Council Infrastructure Design Standard 11-1

CITY OF JACKSONVILLE 2030 MOBILITY PLAN STUDY UPDATE GOALS, OBJECTIVES, AND PERFORMANCE MEASURES PREPARED FOR: CITY OF JACKSONVILLE

NW La Center Road/I-5 Interchange Improvement Project (MP 16.80)

OVERVIEW ORDINANCE: ORD # APPLICATION: 2014C-002

CIVIL, CONSTRUCTION, AND ENVIRONMENTAL ENGINEERING

FERRY COUNTY COUNTY-WIDE PLANNING POLICIES

Metro Board Action: Motion 22.1

Section 3-01 General Concepts, Design Standards and Design Exceptions TABLE OF CONTENTS

The New Highway Capacity Manual 6 th Edition It s Not Your Father s HCM

CHAPTER COMMERCIAL ZONES

Mega Projects at WSDOT

OPEN DATA & PROJECT TRACKER. Michael Chamberlain TPP, Data Management

Region of Waterloo Stage 1 Light Rail Transit Project. Definitions, Acronyms, Cited References Article 1 Definitions.

IX. STRATEGIC PLAN ELEMENT

An Introduction to the. Safety Manual

ENVIRONMENTAL ASSESSMENT INTERSTATE HIGHWAY 35W FROM INTERSTATE HIGHWAY 820 TO INTERSTATE HIGHWAY 30 CITY OF FORT WORTH TARRANT COUNTY, TEXAS

A Network Demand Model for Rural Bypass Planning. Paper Number

LOCATION AND DESIGN DIVISION

Governor Baldacci s Transportation Bond Proposal

I-70 East ROD 1: Phase 1 (Central 70 Project) Air Quality Conformity Technical Report

City of Brantford Chapter 3 TABLE OF CONTENTS

One Maryland One Centerline. GIS-T 2014 May 7, 2014

Overall project. The $288 million Phase 2 DesignBuild project starts construction. this spring, with completion by December 31, 2016

Transportation and Works Department The Regional Municipality of York Yonge Street Newmarket, Ontario L3Y 6Z1

Traffic Safety Analysis of Utah County Highways using SafetyAnalyst. Peter Crawford Kelly

APPENDIX A: SHORT-TERM PROJECT DEPLOYMENTS

Houston Galveston Area Council Congestion Management Process

Annual CSAH Needs Update for 2017

TxDOT Houston District Permit Requirements (Information contained herein is subject to change)

PINELLAS COUNTY MOBILITY PLAN SUMMARY REPORT

Final Recommendations Identification of Improvements, Strategies, and Solutions

Developing Dwelling Unit Equivalent (DUE) Rates Using an Activity Based Travel Demand Model

Regional Transportation Studies Regional Council

November 8, RE: Harrah s Station Square Casino Transportation Analysis Detailed Traffic Impact Study Review. Dear Mr. Rowe:

SR 29 Project Development & Environment Study. Presentation to SR 29 Stakeholders Advisory Committee. January 23, 2014

QLDC Council 8 November Report for Agenda Item: 1

Transcription:

Statewide All Roads Layer Michigan Geographic Framework Field Definitions (Shapefile Attribute Table) (June 27, 2011 Version 11a) The following field definitions make up the shapefile attribute table called Statewide All Roads. This shapefile consists of all road segments in the Michigan Geographic Framework. This Statewide All Roads shapefile consists of the total of the road segments found in the Statewide. All road layers are also available by individual county. The attribute table can be found in the file Allroads_MI_v11a.DBF. Please Note: If you have any questions about the framework data you have received, please contact Laura Blastic at the Michigan Center for Geographic Information. Phone: 517-373-7910, email: blasticl@michigan.gov Field Name Type Size Description Comments FCC C 3 Framework Classification Code See FCC Road Appendix at end of document. RDNAME C 60 This field contains a concatenated street name made up of the data contained in FEDIRP, NAME, FETYPE, and FEDIRS For further information, see info on FEDIRP, NAME, FETYPE, and FEDIRS below. FRADDL N 11 Left side from Address TOADDL N 11 Left side to Address FRADDR N 11 Right side from Address TOADDR N 11 Right side to Address Potential from and to address ranges. These ranges were originally transferred from TIGER. Some modifications have since been made. ZIPL ZIPR N N 5 5 Left side ZIP code Right side ZIP code ZIP codes as created by the Michigan Center for Geographic Information based on US Postal Service data. These zip code fields may contain incomplete data at this time. FEDIRP C 2 Feature Prefix Direction A pre-directional associated with an arc s street name (N, S, E, W, etc.). 1

Field Name Type Size Description Comments NAME C 30 Feature Name FETYPE C 4 Feature Type FEDIRS C 2 Feature Suffix Direction FEDIRP2 C 2 Secondary Feature Prefix Direction NAME2 C 30 Secondary Feature Name FETYPE2 C 4 Secondary Feature Type The street name assigned to the arc. * The street type (AVE, BLVD, RD, ST etc) assigned to the arc. A post-directional associated with an arc s street name component (N, S, E, W, etc.). Road name aliases (e.g., Ford Fwy for I-94 Fwy). FEDIRS2 C 2 Secondary Feature Suffix Direction FEDIRP3 C 2 Feature Direction Prefix 3 A pre-directional used by the Post Office in the Zip+4 associated with an arc s street name (N, S, E, W, etc.). This field will only be filled when some part of the Post Office street name is different from the corresponding part of any of the primary street name components (FEDIRP, NAME, etc.) NAME3 C 30 Feature Name 3 The name used by the Post Office in the Zip+4. This field will only be filled when some part of the Post Office street name is different from the corresponding part of any of the primary street name components (FEDIRP, NAME, etc.) FETYPE3 C 4 Feature Type 3 The street type of the Post Office/Zip+4 name (N, S, E, W, etc.). This field will only be filled when some part of the Post Office street name is different from the corresponding part of any of the primary street name components (FEDIRP, NAME, etc.) FEDIRS3 C 2 Feature Direction Suffix 3 A post-directional associated with an arc s Post Office/Zip+4 name (N, S, E, W, etc.). This field will only be filled when some part of the Post Office street name is different from the corresponding part of any of the primary street name components (FEDIRP, NAME, etc.) 2

Field Name Type Size Description Comments COUNTYL I 3 Left side County FIPS code County boundaries may be displayed by selecting COUNTYL <> COUNTYR. The county polygon boundary has been closed. All arcs have been assigned COUNTYL and COUNTYR values. COUNTYR I 3 Right side County FIPS code NFC N 2 MDOT National Functional Classification (NFC) code 1 Interstates 2 Other Freeways 3 Other Principal Arterials 4 Minor Arterials 5 Major Collectors 6 Minor Collectors 7 Local 0 or uncoded -- not a certified public road Uses United States Department of Transportation (USDOT) system classifying all roads by their transportation function. This system is called the National Functional Classification (NFC) system. There are three major types: (Arterial, Collector, and Local) Future NFC route locations are available in shapefile format. Please contact CGI to obtain a copy. OLD_NFC N 2 Old MDOT National Functional Classification (NFC) code 1 - Rural Interstate (principal arterial) 2 - Rural Other Principal Arterial 5 - Rural Other Freeway (principal arterial) 6 - Rural Minor Arterial 7 - Rural Major Collector 8 - Rural Minor Collector 9 - Rural Local 11 - Urban Interstate (principal arterial) 12 - Urban Other Freeway (principal arterial) 14 - Urban Other Principal Arterial 16 - Urban Minor Arterial 17 - Urban Collector 19 - Urban Local 0 or uncoded - not a certified public road These values have been replaced with the updated values found in the NFC field. 1-19 are the old equivalent values. There were three major types: (Arterial, Collector, and Local) The classification codes 1-9 are rural The classification codes 10-19 are urban Future NFC route locations are available in shapefile format. Please contact CGI to obtain a copy. RU_L I 1 Rural/Urban Designation Left Code Description 1 Rural Area 2 Small Urban Area (5,000 to 49,999) RU_R I 1 Rural/Urban Designation Right 3 Small Urbanized Area (Population 50,000 to 199,999) 4 Large Urbanized Area (Population 200,000 or More) 3

Field Name Type Size Description Comments LEGALSYST N 2 Indicates ownership of the road 1 State Trunkline 2 County Primary 3 County Local 4 City Major 5 City Minor 7 Uncertified with a Funclass The legal system defines the importance of the road and the unit of government that has jurisdiction over the road. This field may or may not be filled in this version of the file. PR N 7 Physical Road ID number Michigan Dept. of Transportation (MDOTs) standard for the Linear Referencing System requires that Physical Road (PRs) are continuous without gaps or overlaps in mile posting. BMP N 10,3 Beginning PR (Physical Road) segment Mile Point for linear referencing system EMP N 10,3 Ending PR (Physical Road) segment Mile Point for linear referencing system BPT C 8 Permanent, unique segment Beginning Point ID EPT C 8 Permanent, unique segment Ending Point ID This value is derived from the MALI database and may not match the GIS length. This value is derived from the MALI database and may not match the GIS length. Used along with PR as the fundamental key in identifying change transactions Used along with PR as the fundamental key in identifying change transactions LRS_LINK C 23 Linear Referencing System link field This field consists of the PR, BPT and EPT fields concatenated (PR, BPT and EPT defined above). This field uniquely identifies a road segment. It will be used to track changes made to road segments that have assigned PRs (Physical Road). LENGTH F 20,5 Arc Length Feature length in meters obtained from the ArcInfo AAT. OID F 20 Object Identification Number : Michigan Geographic Framework (MGF) Version 3.0 ID Unique ID VER C 3 Michigan Geographic Framework Version Number The VER field contains the Michigan Geographic Framework version from which the layer was created. 4

Field Name Type Size Description Comments MGF_HIST N 3 MGF Conflation History 0 Added since conflation 1 Matched TIGER to MIRIS 2 Original unmatched MIRIS 3 Appended unmatched TIGER 4 Ambiguous Static field representing original source of geography. Type: C F N Character Floating Point Numeric 5

Appendix D Framework Classification Code: Field definitions and Valid Entries April 2, 2010 The Framework Classification Code (FCC) is a 3-character field in the framework coverage. The initial value in the FCC field is derived from data that is already associated with the feature. As additional editing takes place, the FCC value will be updated based on the definitions described in this document. New features added to framework will be given the appropriate FCC value based on these same definitions. New Classification Codes may also be created as needed. A00 Future road under construction A1* Limited access Interstates and non-interstates (aka Freeways) such as I 75, I 94, US 27, M 39 A11 Limited access Interstate A12 Limited access non-interstate A13 Ramp to or from a limited access highway A14 Feature associated with rest areas, weigh stations and MDOT garages that are accessible only from A11 or A12 roads A15 Collector/Distributor. Specialized ramp like feature that distributes traffic within complex interchanges. Must connect at both ends with a main line (A11 or A12). Must intersect at least 2 ramps. IE: I 94 and I 69 interchange in Calhoun County near Marshall. A16 Restricted use turnaround in a limited access highway. Normally a feature crossing the median. A2* US Highways & State Highways such as M 52, US 12. (Not limited access) A21 Unlimited access US Highways & State Highways A22 Unsigned State Trunkline Highways A23 Ramp to or from an unlimited access highway A24 Feature associated with non-limited access rest areas and roadside parks A25 State owned surface streets that act as service drives to limited access Freeways (A11 or A12) A26 State trunkline boulevard turnaround (Non-limited access) A29 Unlimited access end of the ramp between the barrels of the boulevard. A3* These roads are classified based on National Functional Classification (NFC). NFC is an attribute of the Framework coverage. The Michigan Department of Transportation assigned each NFC value. NFC is a planning tool which federal, state and local transportation agencies have used since the late 1960's. The Federal Highway Administration (FHWA) developed this system of classifying all streets, roads and highways according to their function. The FHWA publication, Highway Functional Classification: Concepts, Criteria and Procedures, provides the basis for much of the following information. Principal arterials are at the top of the NFC hierarchical system. Principal arterials generally carry long distance, through-travel movements. They also provide access to important traffic generators, such as major airports or regional shopping centers. 6

Minor arterials are similar in function to principal arterials, except they carry trips of shorter distance and to lesser traffic generators. Collectors tend to provide more access to property than do arterials. Collectors also funnel traffic from residential or rural areas to arterials. A31 - Principal Arterial roads (NFC other than 7) A32 - Minor Arterial roads (NFC = 7) A33 - Residential court or cul-de-sac A36 - Directional turnarounds A4* - Non-Certified Roads These are roads that have PR numbers. A41 - General non-certified The majority of non-certified roads fall into this category A42 - Turnarounds Feature that crosses a median. Normally used to facilitate a left-hand turn A43 - Non-certified residential court or cul-de-sac A44 - University owned roads A45 Forest roads within federal jurisdiction A46 Institutional roads within state jurisdiction A47 Roads to an airport A48 Roads to an airport A6* - Roads with special characteristics, these roads may or may not have been updated in the current framework version. A61 Unnamed, non PR (Physical Road Number) roads within Cemeteries. A62 Unnamed, non PR internal drives around malls, commercial sites, retail sites, industrial sites, office sites, schools, colleges, and universities. A63 Unnamed, non PR driveways. A driveway is defined as a road that serves only one residence. A64 Internal roads of Federal, State and Local parks and campgrounds. These roads may have names and PRs A65 Unnamed, non PR roads in residential areas. IE: apartment complexes, mobile home communities, and new developments. A66 Unnamed, non PR two-track roads or vehicular trails. A67 Boating Access Site (BAS) A68 Indian Reservation Roads (IRR) 7

A69 All other features that were originally classified as a road feature in TIGER or MIRIS but do not match any of the criteria used to classify framework roads. More research is needed to better classify these roads. A7* - Non-vehicular transportation features: These features may or may not have been updated in the current framework version. A71 - General Trails or Paths, these features may have multiple uses. IE: Biking, Hiking, Cross County Skiing, Horse, or Snowmobile A72 - Rail-to-trail, these features may have names and PRs A73 - Pedestrian overpasses, these features may have names and PRs A74 Ferry Routes A75 Transportation Structure, usually used to retain a structure identifier. A9* - Artificial road feature: These roads are not seen on a Digital Ortho Quad, but are needed to retain important attribute information. A90 - Certified road right-of-ways. These roads are owned by a local jurisdiction (Act 51 certified), but are not drivable. A91 - Road whose existence is strongly questioned, but have not been confirmed as not existing by a local jurisdiction. A92 Artificial roads that serve as control section break. A93 Artificial roads that serve as pseudo PR break. A94 Artificial roads that serve as PR break. 8