Missouri Department of Transportation2007Missouri Department of TransportationMO 2007 July MoDOT Roads (SHP)vector digital datast_modotThe MoDOT roadway coverage is based on a Dynamic Segmentation model. Dynamic Segmentation models linear features using routes and events, associating multiple sets of attributes to any portion of a linear feature. The ARC feature class forms the basic linear infrastructure from which Dynamic Segmentation models or route-systems are built. NODES indicate the endpoints and intersections of ARCS. The 'from-node' is the first vertex of the arc; the 'to-node' is the last vertex. Together, they define the direction of the arc. Arc-node topology defines connectivity of Dynamic Segmentation models or route-systems. Route systems are built without modifying the underlying arc-node topology. A route represents a single linear feature, such as a city street or highway. Routes are linear features composed of one or more arcs or parts of an arc; for example, a highway may be composed of a number of connected arcs. A route, for Dynamic Segmentation purposes, is simply a linear feature with measure values attached to it. Each route is associated with a measurement system, a linear method consisting of a starting value and other measures along the route, which describe distance along them. The measures are used to locate data that describe parts of the route. Data along routes is modeled using events. Event data, such as accidents, signs, functional classification, pavement condition, pavement type, is based on the Dynamic Segmentation model, the foundation of which is the route system.
The state system network (IS, US, MO, RT) originated from 1980-DIME data, which was later updated with 1995 TIGER files from the US Census Bureau. Currently the coverage is updated monthly utilizing design plans, GPS, aerial imagery and county/city maps. All Census related fields have been removed, as they are not utilized nor updated by MoDOT. As of July 2007, approximately 87% of the state system network was matched to either imagery, gps or other improved data source. All Census related fields have been removed, as they are not utilized nor updated by MoDOT.Generally used for coarse geographic and environmental analysis. The Dynamic Segmentation model is used to reference specific data or events (accidents, pavement type, speed limit, signage, etc.) to locations along a route or travelway, allowing more specific analysis or modeling.en2007publication dateMonthly-95.771478-88.90749940.62018935.963217265451.148075846574.1010423986699.7892994496595.832920roadsstreetstransportationroutehighwayhighwayslinear referencingst_modotrds0707_utmtigersstatesMissouriNoneSpatial resolution of this data is generally considered 1:100,000, though updates are frequently made using much more accurate means (ex. GPS, DOQQ). As of July 2007, approximately 87% of the state system network was matched to either imagery, gps or other improved data sources.Jason EbersoleMissouri Department of TransportationIntermediate GIS Specialistphysical address
2217 St. Mary's Blvd
Jefferson CityMissouri65109mailing address
PO Box 270
Jefferson CityMO65102573-526-5860573-526-8052Jason.Ebersole@modot.mo.gov7:30am-4pm M-FUnclassifiedMicrosoft Windows 2000 Version 5.0 (Build 2195) Service Pack 4; ESRI ArcCatalog 9.2.1.1332ShapefileMissouri Department of TransportationVariousGlobal Positioning Systemvector digital dataGPS data is continuously collected for new and existing roadways that require adjustment of linework in the master road file. Data is acquired using vehicle-based units, either on passenger vehicles or the Automatic Road Analyzer (ARAN) vehicle. Accuracy is generally +/- 3 meters.
Source for GPS data is recorded in "SOURCE" in the AAT table.digital vector dataGPSProvides linework for new roadways, in addition to adjusting current linework. GPS is the prefered data source for linework edits, although imagery and design plans provide valuable information.Missouri Department of Transportation - Design DivisionVarious Engineering FirmsDesign PlansmapDesign plan sheets augment GPS data and DOQQs. Publication dates vary based on contract award dates. Some plan sheets are hardcopy, while many recent sheets are now scanned. Sheets scales vary, from broad overview maps down to individual road and bridge sections.variousscanned and hardcopy design sheetsplansUsed primarily in adjusting mileage along routes. Some lines are adjusted soley on design plans, but is generally restricted to smaller projects and edits. Design plans also provided information about route names.Natural Resource Conservation Service - US Dept. of AgricultureDigital Orthoquarterquadsraster digital dataDigital Orthoquarterquads (DOQQ)are used for adjustment of linework to match ground conditions. DOQQs are not always directly usable, as construction may have occurred after the acquisition of the imagery. The imagery is greyscale "leaf off," acquired during early spring or late fall.digital raster data19922001doqqDOQQs provide information about smaller, non-state system intersections. This imagery is also used for smaller edits, and is often used in conjunction with GPS and design plans. With the availability of 2003-vintage NAIP imagery, the older DOQQs will be less relied on.US Census Bureau1980, 1995Census TIGER - DIMEvector digital dataTIGER - DIME data formed the original base for the state road file. Since inception, this data has been continually adjusted based on other sources. Data is 1:100,000 scale.100000digital vector datacensusProvided initial linework for MoDOT. More current and accurate data is now replacing Census data. All Census-based attributes have been removed due to lack of updates.USDA Farm Service Agency - Aerial Photography Field OfficeNational Agriculture Imagery Programraster digital dataThe National Agriculture Imagery Program (NAIP) provides current and timely digital imagery to various service centers and cost-sharing partners. 2003 Imagery is one-meter resolution color infared aerial photography. 2004-2006 imagery is two-meter true color. Imagery was acquired during "leaf on" time periods, in constrast to the "leaf off" DOQQs.digital raster data20032006ground conditionnaip##Provides most current aerial imagery. Portions of the linework are adjusted based on imagery, primarily in smaller adjustments. NAIP imagery also provides more current information than the older greyscale DOQQs. ## represents last two digits of year acquired.US Geological SurveyDepartment of Planning - Saint Louis County, Missouri2002USGS Urban High Resolution Imageryraster digital dataThis imagery provides greater detail than any other available image source. Imagery is one-foot (.3 m) resolution true color, allowing identification of more features possible. Use is limited to St. Louis County and City. Imagery was provided by the St. Louis County Department of Planning.digital raster data2002publication datestlimgProvides detail imagery for the adjustment of linework within St. Louis County and City.MoDOTMicrostation Design Filevector digital datadigital vector dataDGNMicrostation CAD drawing file. Survey-grade linework obtain from construction. Differs from 'plans' source by using actual digital vector data. Source data converted and reprojected from modified State Plane DGN files into UTM coverages.Metadata imported.D:\st_modotrds\metadata.xml20070419Metadata imported.D:\st_modotrds\metadata.xml20070504Metadata imported.D:\st_modotrds\metadata.xml20070622Metadata imported.D:\st_modotrds\metadata.xml20070731VectorComplete chain518995Node, planar graph401180Point4Composite object270291SimpleArcTRUE518995FALSEFALSESimpleNodeTRUE401180FALSEFALSESimpleTicFALSE4FALSEFALSESimpleRouteTRUE270291FALSETRUEcoordinate pair0.0000000.000000metersUniversal Transverse Mercator150.999600-93.0000000.000000500000.0000000.000000North American Datum of 1983Geodetic Reference System 806378137.000000298.257222GCS_North_American_1983NAD_1983_UTM_Zone_15Nst_modot.aatThe '.aat' (Arc Attribute Table) stores descriptive data about the ARCS. There is one record in the '.aat' for each ARC in the coverage. The record is related to the feature by the internal sequence number stored for each ARC.MoDOTFeature Class518995FIDInternal feature number.ESRISequential unique whole numbers that are automatically generated.FIDOID400ShapeFeature geometry.ESRICoordinates defining the features.ShapeGeometry000FNODE#Internal node number for the beginning of an arc (from-node).ESRIWhole numbers that are automatically generated.45BinaryTNODE#Internal node number for the end of an arc (to-node).ESRIWhole numbers that are automatically generated.45BinaryLPOLY#Internal node number for the left polygon.ESRIWhole numbers that are automatically generated.45BinaryRPOLY#Internal node number for the right polygon.ESRIWhole numbers that are automatically generated.45BinaryLENGTHLength of feature in internal units.ESRIPositive real numbers that are automatically generated.818Float5ST_MODOT#Internal feature number.ESRISequential unique whole numbers that are automatically generated.45BinaryST_MODOT-IDUser-defined feature number.ESRI45BinaryARCSEGMENT_IDCalculated unique feature numberMoDOTAs needed99IntegerDISTMoDOT District NumberMoDOT110As needed22IntegerCNTY_NOCounty NumberMoDOT1115As needed33IntegerRTE_DESGA designation is a two or three letter code used to identify the type of travelway. IS - Interstate; US - US Numbered Routes; MO - Missouri Numbered Routes; RT - Missouri Lettered Routes; LP - Business Loop (Interstate); BU - Business Loop (non-interstate); AL - Alternate Routes; SP - Spur; RV - Reversible; OR - Outer Road; RP - Ramp (non-at-grade intersection); CO - Connector for Wye Leg and other at-grade connections; RA - Rest Area; WS - Weigh Station; CRD - County Road; CST - City Street; ALY - Alley; PVT - Private Road. Designations are listed in hierarchical order.MoDOTAs needed33CharacterROUTEProper name of the primary route. **NOTE** Primary route for state system is defined by the highest-ranking Route Designation (Rte_Desg), next numerically then alphabetically.MoDOTAs needed6060CharacterDIRDirection indicates the direction of travel on a travelway (S,N,E,W). Direction of travel on state maintained facilities (state-system) is defined by the route or travelway number; EVEN numbered travelways are designated as East/West and ODD numbered travelways are designated as North/South. **NOTE** Direction is only valid on divided facilities in the ARC feature.MoDOTAs needed11CharacterCHECK2Roadway NameMoDOTNone planned3535CharacterCHECK3Roadway NameMoDOTNone planned3535CharacterSECTIONS_IDIndicates presence/absence of route covering the arc.MoDOT0A route section is present on the arc.2No route section is present on the arc.As needed11IntegerOFFSETApplies only to Outer Roads - the offset direction is determined by the parent route. If parent direction is North/South the offset direction is East/West, and for parent routes which are East/West, the offset would be North/South.MoDOTAs needed11CharacterSOURCEEntity that produced source data. This does not indicate how data was collected.MoDOT08/2003As needed2525CharacterPOSITION_IDCalculated unique feature number. Serves as "master arc" indicator. Arcs having the same position_id are from the same parent arc.MoDOTAs needed99IntegerTIMEDate/time stamp of GPS data collection.MoDOT08/2004As needed2424CharacterRDS_DISTRoads District name, applies to county/city roads.MoDOT08/2004As needed5050CharacterCOLLMTHDDescribes collection method of data used for linework edits. Valid on line work edits from 08/2003 onwards. See "Data Quality - Source" for further explanation.MoDOTGPSGlobal Positioning SystemDOQQDigitial OrthoquarterquadsPLANSMoDOT Design PlansNAIP##National Agricultural Imagery Program (## indicates collection year)DGNComputer-aided Drafting Data (Microstation, AutoCAD)STLIMGUSGS Urban High Resolution Imagery08/2004As needed2525CharacterEDITDATE810DateDate on which segment was editedMoDOTst_modot.natThe '.nat' (Node Attribute Table) stores descriptive data about the NODES. There is one record in the '.nat' for each NODE in the coverage. The record is related to the NODE by the node's internal sequence.MoDOTFeature Class401180FIDInternal feature number.ESRISequential unique whole numbers that are automatically generated.FIDOID400ShapeFeature geometry.ESRICoordinates defining the features.ShapeGeometry000ARC#Internal sequence number of one of the arcs that connects at the node location.ESRI45BinaryST_MODOT#Internal feature number.ESRISequential unique whole numbers that are automatically generated.45BinaryST_MODOT-IDUser-defined feature number.ESRI45BinaryTW_INTERSECTCalculated Unique NumberMoDOTAs needed99IntegerX-COORDCalculated LongitudeMoDOTAs needed818Float5Y-COORDCalculated LatitudeMoDOTAs needed818Float5EXIT_NO55CharacterInterstate exit number. Only found on departure node and only on nodes associated with interstates (IS).MoDOTAs neededst_modot.rattwayThe 'Route.Tway' feature class is a Dynamic Segmentation model or route system built using the continuous log-mile system. The '.rattway' (ROUTE ATTRIBUTE TABLE.TWAY) stores descriptive data about the ROUTES of the continuous log-mile system. There is one record in the '.rattway' for each ROUTE in the feature class. The record is related to the feature by the internal sequence number stored for each ROUTE.MoDOTFeature Class270291FIDInternal feature number.ESRISequential unique whole numbers that are automatically generated.FIDOID400ShapeFeature geometry.ESRICoordinates defining the features.ShapeGeometry000TWAY#Internal feature number.ESRISequential unique whole numbers that are automatically generated.45BinaryTWAY-IDUser-defined feature number.ESRI45BinaryTRAVELWAY_IDA calculated, mutually exclusive number identifying a specific route or travelway.MoDOTAs needed99IntegerRTECHKProper name of the route or travelway.MoDOTAs needed7070CharacterRTEDSGA designation is a two or three letter code used to identify the type of travelway. IS - Interstate; US - US Numbered Routes; MO - Missouri Numbered Routes; RT - Missouri Lettered Routes; LP - Business Loop (Interstate); BU - Business Loop (non-interstate); AL - Alternate Routes; SP - Spur; RV - Reversible; OR - Outer Road; RP - Ramp (non-at-grade intersection); CO - Connector for Wye Leg and other at-grade connections; RA - Rest Area; WS - Weigh Station; CRD - County Road; CST - City Street; ALY - Alley; PVT - Private Road. Designations are listed in hierarchical order.MoDOTAs needed33CharacterOFFSETApplies only to Outer Roads - the offset direction is determined by the parent route. If parent direction is North/South the offset direction is East/West, and for parent routes which are East/West, the offset would be North/South.MoDOTAs needed11CharacterDIRDirection indicates the direction of travel on a travelway (S,N,E,W). Direction of travel on state maintained facilities (state-system) is defined by the route or travelway number; EVEN numbered travelways are designated as East/West and ODD numbered travelways are designated as North/South.MoDOTAs needed11CharacterROADSRoad Name, concatenated without spacesMoDOTUnknown77CharacterROADS2Concatenated rte_desg, rtechk, and dir (Route Designation, Route Name, Direction, and Offset for outer roads).MoDOTAs needed7676CharacterRAMPFROMThe primary route from which the ramp departs.MoDOTAs needed3535CharacterRAMPTOThe primary route to which the ramp connects.MoDOTAs needed3535CharacterCHECK3Road NameMoDOTIrregular3535CharacterCHECK5Road NameMoDOTIrregular3535CharacterDISTRICTMoDOT District NumberMoDOT110As needed22Number0ARCLENGTHThe length of the route in coverage units. This is computed by summing the lengths of the arcs and partial arcs that make up each route. Calculated by Arc Command 'RouteStats'.ESRI ArcInfo RouteStatsAs needed412Float3MEASURELENGTHThe length of the route in route measures (miles). This is computed by summing the differences of F-MEAS and T-MEAS of each section in a route.ESRI ArcInfo RouteStatsAs needed412Float3LOWMEASUREThe lowest measure value on the route (in miles).ESRI ArcInfo RouteStatsAs needed412Float3HIGHMEASUREThe highest measure value on the route (in miles).ESRI ArcInfo RouteStatsAs needed412Float3FIRSTSECTIONThe internal number of the first section in the route.ESRI ArcInfo RouteStatsAs needed45BinaryLASTSECTIONThe internal number of the last section in the route.ESRI ArcInfo RouteStatsAs needed45BinaryNUMSECTIONSThe number of sections in the route.ESRI ArcInfo RouteStatsAs needed45BinaryDEACT_DATEMonth and year when route was deactivated or flagged for deletion. Due to data maintenance issues, routes are currently flagged, but not deleted. Routes with deactivation dates should not be used if possible. Not currently used.MoDOTApril 200455Character
sectwayThe 'Section.Tway' table is a Dynamic Segmentation table built using the continuous log-mile system. The '.sectway' (SECTION ATTRIBUTE TABLE.TWAY) stores descriptive data about the SECTIONS of the continuous log-mile system. There is one record in the '.sectway' for each SECTION in the SECTION.TWAY object class. The record is related to the feature by the internal sequence number stored for each ROUTE. This table/feature class is only visible in ArcInfo Workstation.MoDOTOIDInternal object number (Only present in ArcMap).ESRISequential unique whole numbers that are automatically generated.ROUTELINK#Internal number identifying the route to which the section is linkedESRIARCLINK#Internal number identifying the arc which the section referencesESRIF-MEASBeginning log mile for the sectionMoDOTAs neededT-MEASEnding log mile for the sectionMoDOTAs neededF-POSBeginning position of section (generally 0), read as a percentage of section distanceESRIT-POSEnding position of section (generally 100), read as a percentage of section distanceESRITWAY#Internal feature number of the sectionESRITWAY-IDUser-defined feature number of the section (not to be confused with TRAVELWAY_ID)ESRITWSEGMENT_IDUnique identifier for each sectionMoDOTAs neededARCLENGTHLength of section in coverage unitsArcInfo RouteStatsAs neededMEASURELENGTHLength in route units (miles), calculated from F-MEAS and T-MEASArcInfo RouteStatsAs neededDELTAPOSITIONDifference between start and end position, %ArcInfo RouteStatsAs neededRATIOMeasure/arc length ratio of sectionArcInfo RouteStatsAs neededPREVSECTIONInternal number of previous sectionArcInfo RouteStatsAs neededF_NUMFrom NumberMoDOTAs neededT_NUMTo NumberMoDOTAs neededCNTY_NOCounty NumberMoDOTAs neededDISTRICTMoDOT District NumberMoDOTAs neededCNTY_F_MEASCounty FROM MeasureMoDOTAs neededCNTY_T_MEASCounty TO MeasureMoDOTAs neededTRAVELWAYIDA calculated, mutually exclusive number identifying a specific parent route or travelway of the section.MoDOTAs needed99IntegerThe ARC feature class forms the basic linear infrastructure from which Dynamic Segmentation models or route-systems are built. NODES indicate the endpoints and intersections of ARCS. The 'from-node' is the first vertex of the arc; the 'to-node' is the last vertex. Together, they define the direction of the arc. Arc-node topology defines connectivity of Dynamic Segmentation models or route-systems. Route systems are built without modifying the underlying arc-node topology. The routes and sections of a route-system are stored in two INFO data files. These tables are the route attribute table (RAT), which defines a route feature class and the section table (SEC), which defines a section feature class. Together, these feature classes define a route-system.
The '.aat' (Arc Attribute Table) stores descriptive data about the ARCS. There is one record in the '.aat' for each ARC in the coverage. The record is related to the feature by the internal sequence number stored for each ARC.
The '.nat' (Node Attribute Table) stores descriptive data about the NODES. There is one record in the '.nat' for each NODE in the coverage. The record is related to the NODE by the node's internal sequence.
The '.rattway' (Route Attribute Table.TWAY) stores descriptive data about the ROUTES of the continuous log-mile system. There is one record in the '.rattway' for each ROUTE in the feature class. The record is related to the feature by the internal sequence number stored for each ROUTE.
The '.sectway' (Section Attribute Table.TWAY) stores descriptive data about the SECTIONS of the continuous log-mile system. There is one record in the '.sectway' for each SECTION in the SECTION.TWAY object class. The record is related to the feature by the internal sequence number stored for each SECTION. Each section is also linked to the associated ROUTE and ARC by the internal number of each. A graphical representation of these relationships is contained in the associated cov_model.pdf.Offline Datano compression applied440.526440.52620070731Jason EbersoleMissouri Department of TransportationGIS Specialistphysical address
2217 St. Mary's Blvd.
Jefferson CityMissouri65109mailing address
P.O. Box 270
Jefferson CityMO65102573-526-5860573-526-8052Jason.Ebersole@modot.mo.gov7:30am-4pm M-FFGDC Content Standards for Digital Geospatial MetadataFGDC-STD-001-1998local timeenhttp://www.esri.com/metadata/esriprof80.htmlESRI Metadata Profile2007073109282700FALSE20070731093323002007073109332300{C51C3191-6C6F-43E3-B790-7BA2F2E18CC7}file://\\msdisweb-nn.col.missouri.edu\d$\Geoportal\GPpublish\Coverages\Converted\review\Hold Shapefiles\metadata without data\st_modotrds0707_utmLocal Area NetworkMicrosoft Windows 2000 Version 5.0 (Build 2195) Service Pack 4; ESRI ArcCatalog 9.2.1.1332MO 2007,July MoDOT Roads265451.148075846574.1010424496595.832923986699.7892991-95.771478-88.90749940.62018935.9632171ISO 19115 Geographic Information - MetadataDIS_ESRI1.0dataset002file://\\HA59563\D$\st_modotrds\st_modotLocal Area Network440.526ShapefileNAD_1983_UTM_Zone_15N518995401180427029120070731