Missouri Department of Transportation2008MO 2008 August MoDOT Roads - Arcs (SHP)vector digital dataftp://msdis.missouri.edu/pub/Transportation_Networks/MO_2008_August_MoDOT_Roads_Arcs_shp.zipst_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.en2008publication dateMonthly-95.771478-88.90749940.62018935.963225265451.148075846574.1010423986700.6616874496595.832920roadsroadstreetsTransportation Networksroutehighwayhighwayslinear referencingTransportationst_modotrds0809_arc_shptigersstatesMissouriNoneMissouri Department of Transportation makes no warranties or guaranties on this data for any use beyond its original purpose for linear referencing of transportation data. Data is provided for general reference and is not intended as a sole source for analysis or cartography requiring very high levels of precision and accuracy.
Spatial 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 highway network was matched to either imagery, gps or other improved data sources.Jason EbersoleMissouri Department of TransportationSenior 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.2.1350ShapefileMissouri 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 "COLLMTHD" 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 infrared aerial photography. 2004-2006 imagery is two-meter true color. 2007 imagery is1-meter true color. Imagery was acquired during "leaf on" time periods, in constrast to the "leaf off" DOQQs.digital raster data20032007ground 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 image collection year.US Geological SurveyDepartment of Planning - Saint Louis County, Missouri2002, 2006USGS 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. 2002 imagery was provided by the St. Louis County Department of Planning. 2006 imagery acquired from USGS National Map Seamless Data Server.digital raster data20022006publication datestlimg##Provides detail imagery for the adjustment of linework within St. Louis County and City. ## represents last two digits of image collection year.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.E:\st_modotrds\metadata.xml20080227Digital Orthoquarterquads (2-foot)State of Missouri2007Digital Orthoquarterquads (DOQQ) are used for adjustment of linework to match ground conditions. The imagery is two-foot (.6m) true-color "leaf off," acquired during early spring or late fall, allowing identification of more features possible. 2007 imagery covers the eastern portion of the state. 2008 imagery will cover the western portion.digital raster data2007doqq##Provides current, detail imagery for the adjustment of linework. ## represents last two digits of image collection year. Metadata imported.E:\st_modotrds\meta_ref0208.xml20080425Metadata imported.E:\st_modotrds\metadata.xml20080625Metadata imported.E:\st_modotrds\metadata.xml20080801Dataset copied.E:\st_modotrds\metadata20080910Metadata imported.E:\st_modotrds\metadata.xml20080925Metadata imported.E:\st_modotrds\metadata.xml20080925VectorSimple3FALSE0FALSEFALSEcoordinate pair0.0000000.000000metersNorth American Datum of 1983Geodetic Reference System 806378137.000000298.257222GCS_North_American_1983NAD_1983_UTM_Zone_15Nst_modot0_arcThe '.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 Class0FIDInternal feature number.ESRISequential unique whole numbers that are automatically generated.FIDOID400ShapeFeature geometry.ESRICoordinates defining the features.ShapeGeometry000FNODE_FNODE_Integer990TNODE_TNODE_Integer990LPOLY_LPOLY_Integer990RPOLY_RPOLY_Integer990LENGTHLength of feature in internal units.ESRIPositive real numbers that are automatically generated.1918DoubleLENGTH00ST_MODOT0_ST_MODOT0_Integer990ST_MODOT01ST_MODOT01Integer990ARCSEGMENTARCSEGMENTInteger990DISTMoDOT District NumberMoDOT1Northwest2North Central3Northeast4Kansas City5Central6Saint Louis Area7Southwest8Springfield Area9South Central10SoutheastAs needed22SmallIntegerDIST20CNTY_NOCounty Number (not FIPS number)MoDOT
-
- 1Adair
- 2Andrew
- 3Atchison
- 4Audrain
- 5Barry
- 6Barton
- 7Bates
- 8Benton
- 9Bollinger
- 10Boone
- 11Buchanan
- 12Butler
- 13Caldwell
- 14Callaway
- 15Camden
- 16Cape Girardeau
- 17Carroll
- 18Carter
- 19Cass
- 20Cedar
- 21Chariton
- 22Christian
- 23Clark
- 24Clay
- 25Clinton
- 26Cole
- 27Cooper
- 28Crawford
- 29Dade
- 30Dallas
- 31Daviess
- 32Dekalb
- 33Dent
- 34Douglas
- 35Dunklin
- 36Franklin
- 37Gasconade
- 38Gentry
- 39Greene
- 40Grundy
- 41Harrison
- 42Henry
- 43Hickory
- 44Holt
- 45Howard
- 46Howell
- 47Iron
- 48Jackson
- 49Jasper
- 50Jefferson
- 51Johnson
- 52Knox
- 53Laclede
- 54Lafayette
- 55Lawrence
- 56Lewis
- 57Lincoln
- 58Linn
- 59Livingston
- 60McDonald
- 61Macon
- 62Madison
- 63Maries
- 64Marion
- 65Mercer
- 66Miller
- 67Mississippi
- 68Moniteau
- 69Monroe
- 70Montgomery
- 71Morgan
- 72New Madrid
- 73Newton
- 74Nodaway
- 75Oregon
- 76Osage
- 77Ozark
- 78Pemiscot
- 79Perry
- 80Pettis
- 81Phelps
- 82Pike
- 83Platte
- 84Polk
- 85Pulaski
- 86Putnam
- 87Ralls
- 88Randolph
- 89Ray
- 90Reynolds
- 91Ripley
- 92Saint Charles
- 93Saint Clair
- 94Saint Francois
- 95Sainte Genevieve
- 96Saint Louis County
- 97Saline
- 98Schuyler
- 99Scotland
- 100Scott
- 101Shannon
- 102Shelby
- 103Stoddard
- 104Stone
- 105Sullivan
- 106Taney
- 107Texas
- 108Vernon
- 109Warren
- 110Washington
- 111Wayne
- 112Webster
- 113Worth
- 114Wright
- 115Saint Louis CityAs needed33SmallIntegerCNTY_NO30RTE_DESGA designation is a two or three letter code used to identify the type of travelway. Designations are listed in hierarchical order under attribute domain values. NFS, NPS, FWS and COE designations are future use values. Listed designation is from the most primary route on the arc.MoDOTAs needed33StringISInterstateUSUS Numbered HighwayMOState Numbered HighwayALAlternate RouteRTState Lettered RouteLPInterstate Business LoopBUNon-Interstate Business LoopSPSpur RouteRVReversible RouteOROuter RoadRPRampRARest AreaWSWeigh StationCOConnector for wye leg (at-grade connections)CSTCity StreetCRDCounty RoadNFSNational Forest Service roadNPSNational Park Service RoadFWSFish and Wildlife Service roadCOEUS Army Corps of Engineer roadDODDepartment of Defense roadPVTPrivate road, entrance or driveway (special use only)RRRailroad (generic designation)RTE_DESG00ROUTEProper 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. Railroad names are determined by the rail subdivision and not owner.MoDOTAs needed6060StringROUTE00DIRDirection 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 needed11StringDIR00CHECK2Road Name (Not for use)MoDOTNone planned3535StringCHECK200CHECK3Road Name (Not for use)MoDOTNone planned3535StringCHECK300SECTIONS_ISECTIONS_ISmallInteger110OFFSETApplies 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 needed11StringOFFSET00SOURCEEntity that produced source data. This does not indicate how data was collected.MoDOT08/2003As needed2525StringSOURCE00POSITION_IPOSITION_IInteger990TIMEDate/time stamp of GPS data collection.MoDOT08/2004As needed2424StringTIME00RDS_DISTRoads District name, applies to county/city roads.MoDOT08/2004As needed5050StringRDS_DIST00COLLMTHDDescribes 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 Orthoquarterquads (## indicates collection year, starting in 2007)PLANSMoDOT Design PlansNAIP##National Agricultural Imagery Program (## indicates collection year)DGNComputer-aided Drafting Data (Microstation, AutoCAD)STLIMG##USGS Urban High Resolution Imagery (## indicates collection year)DOQQ##Digitial Orthoquarterquads (## indicates collection year, starting in 2007)08/2004As needed2525StringCOLLMTHD00EDITDATE810DateDate on which segment was editedMoDOTEDITDATE00st_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 Class425334FIDInternal 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 neededTW_INTRSC_CLASS2020CharacterAT GRADERoadway intersects at the same grade or level. Also denoted pseudonodes or endpoints.MoDOTNOT AT GRADERoadway intersects at different grades or levels.MoDOTNULLPseudonode or endpoint (non-road intersection)MoDOTDesignates grade connection of an intersectionMoDOTNovember 2007As 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 Class291472FIDInternal 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. See AAT - RTE_DESG for attribute domain values.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.MoDOTIrregular3535CharacterRAMPTOThe primary route to which the ramp connects.MoDOTIrregular3535CharacterCHECK3Road Name (Not for use)MoDOTNone planned3535CharacterCHECK5Road Name (Not for use)MoDOTNone planned3535CharacterDISTRICTMoDOT 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 Number (see AAT for values)MoDOTAs neededDISTRICTMoDOT District Number (see AAT for values)MoDOTAs 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. Some route designations (NFS, NPS, FWS and COE) are not in current use, but are planned additions.
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.Downloadable Datano compression applied488.179488.179Local Area Networkftp://msdis.missouri.edu/pub/state/transportation/modot/st_modotrds0809.zipShapefileShapefile0.00020080925Jason EbersoleMissouri Department of TransportationSenior GIS 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 timeen2008092509552400FALSE20110524154608002011052415460800{D40B5C61-296A-4183-A771-5B2281A30A5C}st_modot0_arc0020.000file://\\msdisweb-nn.col.missouri.edu\d$\Geoportal\GPpublish\Coverages\Converted\Transportation_shapefiles\st_modot0_arc.shpLocal Area NetworkProjectedGCS_North_American_1983NAD_1983_UTM_Zone_15N<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.0'><WKT>PROJCS["NAD_1983_UTM_Zone_15N",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER["False_Easting",500000.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-93.0],PARAMETER["Scale_Factor",0.9996],PARAMETER["Latitude_Of_Origin",0.0],UNIT["Meter",1.0],AUTHORITY["EPSG",26915]]</WKT><XOrigin>-5120900</XOrigin><YOrigin>-9998100</YOrigin><XYScale>450445547.3910538</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.001</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>26915</WKID></ProjectedCoordinateSystem>CopyFeatures Z:\Geoportal\GPpublish\Coverages\Converted\Transportation_shapefiles\st_modot0\arc Z:\Geoportal\GPpublish\Coverages\Converted\Transportation_shapefiles\st_modot0_arc.shp # 0 0 0Microsoft Windows Server 2008 R2 Version 6.1 (Build 7601) Service Pack 1; ESRI ArcGIS 10.0.0.2414MO August 2008 MoDOT Roads Arc265451.148075846574.1010424496595.832923986700.6616871-95.771478-88.90749940.62018935.9632251002ISO 19115 Geographic Information - MetadataDIS_ESRI1.0dataset002file://\\HA59563\E$\st_modotrds\st_modotLocal Area Network488.179ArcInfo CoverageShapefile0.000NAD_1983_UTM_Zone_15NEPSG7.4.10546556425334429147220110524