<?xml version="1.0" encoding="UTF-8" standalone="no"?><metadata xmlns:fn="http://www.w3.org/2005/xpath-functions" xmlns:xdt="http://www.w3.org/2005/xpath-datatypes" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <idinfo>
        <citation>
            <citeinfo>
                <origin>Commonwealth of Virginia</origin>
                <origin>Department of Transportation</origin>
                <pubdate>20190129</pubdate>
                <title>Overlapping Route Edges with Official State Mileage Measures - Linear Referencing System</title>
                <edition>Original</edition>
                <geoform>vector digital data</geoform>
                <pubinfo>
                    <pubplace>Richmond, Virginia</pubplace>
                    <publish>Spatial Intelligence Group | EDM | ITD | Virginia Department of Transportation</publish>
                </pubinfo>
                <onlink>withheld</onlink>
            </citeinfo>
        </citation>
        <descript>
            <abstract>
This feature class consists of approximately 1,750,000 features representing around 70,000 miles of Interstate, Primary, Secondary and Urban roads throughout the State of Virginia. The Linear Referencing System is based on the Virginia Department of Transportation's Source System of Record for road inventory, Roadway Inventory Management System (RIMS).  

Geometry and Attribution:
The Linear Referencing System (LRS) data contained within this feature class provides route centerline geometry that is segmented at each intersection and supplies key descriptive attribution for each segment (i.e. edge) record.  The feature class also depicts overlapping routes (e.g. Interstate 64 and Interstate 95) as two separate collinear features, one on top of the other.  Routes built in the prime and non-prime directions are included.  Each road centerline record has a master route record assigned.  In addition, local Virginia Geographic Information Network (VGIN) street names are attributed to each edge where possible.

Measures:
The linear reference is based on Official State Mileage (OSM) as derived from reference points at Roadway Inventory Management System (RIMS) roadway intersections (i.e. nodes/junctions).
Note: The overlap, non-prime measures and street names are for reference only. These measures and street names have not been fully validated for accuracy or completeness.
</abstract>
            <purpose>This linear referenced data layer represents roadways that are maintained by the Virginia Department of Transportation and provides the underlying spatially enabled geometric network to which all "events" (e.g. potholes, pavement type, vehicle accidents, traffic counts, culverts, etc...) can be located.</purpose>
            <supplinf>
Version Release Documentation:  
Contained within all Linear Referencing System data release packages are comprehensive release notes (e.g. “LRSx.x Release Notes.pdf”, where the x.x corresponds to the release version).  These notes outline pertinent information concerning the release and provide general reference about the LRS.  To determine which Linear Referencing layer will best suit your needs, see the appendix portion of the release notes for a Feature Class Application Matrix.
</supplinf>
        </descript>
        <timeperd>
            <timeinfo>
                <sngdate>
                    <caldate>20190129</caldate>
                </sngdate>
            </timeinfo>
            <current>publication date</current>
        </timeperd>
        <status>
            <progress>In work</progress>
            <update>Quarterly</update>
        </status>
        <spdom>
            <bounding>
                <westbc>-83.656310</westbc>
                <eastbc>-75.344460</eastbc>
                <northbc>39.440930</northbc>
                <southbc>36.536870</southbc>
            </bounding>
        </spdom>
        <keywords>
            <theme>
                <themekt>ISO 19115 Topic Category</themekt>
                <themekey>Transportation</themekey>
                <themekey>Virginia Department of Transportation</themekey>
                <themekey>VDOT</themekey>
                <themekey>Linear Referencing System</themekey>
                <themekey>LRS</themekey>
                <themekey>Roadway Network System</themekey>
                <themekey>RNS</themekey>
                <themekey>Roadway Inventory Management System</themekey>
                <themekey>RIMS</themekey>
                <themekey>Spatial Intelligence Group</themekey>
                <themekey>SIG</themekey>
                <themekey>Routes</themekey>
                <themekey>Roads</themekey>
                <themekey>Interstate</themekey>
                <themekey>Primary</themekey>
                <themekey>Secondary</themekey>
                <themekey>Frontage</themekey>
                <themekey>Ramp</themekey>
                <themekey>Edge</themekey>
                <themekey>Overlap</themekey>
                <themekey>Official State Mileage</themekey>
                <themekey>OSM</themekey>
            </theme>
            <place>
                <placekey>Virginia</placekey>
                <placekey>Commonwealth of Virginia</placekey>
            </place>
            <temporal>
                <tempkey>20190129</tempkey>
                <tempkey>LRS Release Version 19.1</tempkey>
            </temporal>
        </keywords>
        <useconst>
Disclaimer:  The Virginia Department of Transportation's digital data files are for use in performing the official business of the Commonwealth of Virginia.  Once the data are distributed outside of the agency, the Virginia Department of Transportation assumes no responsibility to maintain the data or metadata for the recipient in any manner or form.  The data and metadata are provided "as is" and in no event shall the Commonwealth of Virginia, or its agencies or representatives, be liable for any damages, including but not limited to: damages resulting from lost data, lost profits or revenue, the costs of recovering such data, the costs of substitute data, claims by third parties, other similar costs, or any special, incidental, punitive, or consequential damages arising out of the use of the data. 

Users of this data must credit the source(s). Use of these copyrightable files or data layers indicates agreements to abide by all copyright laws and restrictions regarding the files. The copyrightable files and hard-copy maps developed from the files may not be duplicated, sold or distributed without written permission from the Virginia Department of Transportation.

The representations of Virginia Department of Transportation business data contained within are believed to be correct.  This data is provided without any guarantee of accuracy, timeliness or completeness.  No business decisions should be made based on this data without validating its accuracy against the official source system of record.  Users of this data are solely responsible for determining if it is appropriate for their application.

Virginia Department of Transportation Divisions set all policy on the allowable uses of this data.  

Please report errors and omissions directly to the appropriate Virginia Department of Transportation Division data owner.
</useconst>
        <ptcontac>
            <cntinfo>
                <cntorgp>
                    <cntorg>Spatial Intelligence Group | EDM | ITD | Virginia Department of Transportation</cntorg>
                    <cntper>Spatial Intelligence Group | EDM | ITD | Virginia Department of Transportation</cntper>
                </cntorgp>
                <cntaddr>
                    <addrtype>mailing and physical address</addrtype>
                    <address>1401 East Broad Street</address>
                    <city>Richmond</city>
                    <state>Virginia</state>
                    <postal>23219-2052</postal>
                    <country>USA</country>
                </cntaddr>
                <cntvoice>804.786.1999</cntvoice>
                <cntemail>COITDSIG@VDOT.Virginia.Gov</cntemail>
                <hours>9am - 5pm EST/EDT, M-F</hours>
            </cntinfo>
        </ptcontac>
        <datacred>
This data was created as part of a joint effort between the Geographic Information System Program Office and the Roadway Network System  Program, both contained under the Information Technology Division of the Virginia Department of Transportation. It also includes street names from the Virginia Geographic Information Network Master Centerlines.

© Copyright 2019 Virginia Department of Transportation - All Rights Reserved
</datacred>
        <secinfo>
            <secsys>Internal VDOT Policy</secsys>
            <secclass>Unclassified</secclass>
        </secinfo>
        <native/>
        <crossref>
            <citeinfo>
                <pubdate>20190129</pubdate>
                <geoform>vector digital data</geoform>
                <pubinfo>
                    <pubplace>Richmond, Virginia</pubplace>
                    <publish>Virginia Department of Transportation</publish>
                </pubinfo>
            </citeinfo>
        </crossref>
    </idinfo>
    <dataqual>
        <attracc>
            <attraccr>
Business attribute components for all Virginia Department of Transportation maintained routes are derived and maintained within Roadway Inventory Management System (RIMS).  The attributes in Roadway Inventory Management System (RIMS) are field checked when a route is first created by the Maintenance Division or when modifications to existing routes are identified.
 
The Roadway Network System continually reviews business processes and works with the business units to ensure the proper attribution is maintained as changes occur.  Mechanisms developed for the business unit allows them to identify attribute incontinences if they should occur.
</attraccr>
        </attracc>
        <logic>The Linear Referencing System build process analyzes constructed routes determining if they are topologically continuous.  Internal business rules dictate all necessary deviation from the aforementioned determination.</logic>
        <complete>
The Roadway Inventory Management System (RIMS) is the source system of record for this layer. The Roadway Network System (RNS) will replace Roadway Inventory Management System (RIMS) and become the source system of record for this layer.  The Roadway Inventory Management System (RIMS) source data is split into two components, a business attribute component and a location component.  
 
Business Component: The business attribute component contains all records in the Roadway Inventory Management System (RIMS). 
 
Location Component: There is currently a lag between the time a roadway is physically constructed and when it is entered into Roadway Inventory Management System (RIMS) and then ultimately depicted the Geographic Information System Centerline.  Computer-Aided Design files and local data are used where necessary.  Ortho-rectified imagery is used in the creation and update process to ensure alignment. The Roadway Network System models Roadway Inventory Management System (RIMS) and contains all location information, additional non-prime centerlines for divided primary and secondary routes and urban and street named networks. Currently the Roadway Network System contains most Roadway Inventory Management System (RIMS) routes with a high degree of completeness for each route (95%+).  Comparisons between the Roadway Inventory Management System (RIMS) and the Roadway Network System networks will attempt to address all inconsistencies before the Roadway Network System becomes the source system of record. The Roadway Network System is based on creating a measured anchor section for each segment of the route.  Detailed comparisons were done in the automated data conversion processes between the Roadway Inventory Management System (RIMS) Link and Node based system and the Roadway Network System Anchor Section and Anchor Point based system to ensure completeness. Manual steps are being developed to handle special cases such as loop and loop back routes that were not possible to automate.
</complete>
        <posacc>
            <horizpa>
                <horizpar>Horizontal accuracy for this layer can be defined as the probable error as measured along the linearly referenced route between reference calibration points. Such errors are largely dependent upon the degree of polyline resolution and the spatial alignment of the roadway with the actual centerline. Known reference point locations with known Official State Mileage values are used to ensure calibration of routes.</horizpar>
                <qhorizpa>
                    <horizpav>53 feet +/- 0.01 miles</horizpav>
                    <horizpae>Precision of the mile points in the Roadway Inventory Management System (RIMS) is 53 feet (+/- 0.01 miles).  Conversely location information may not have been recorded in the source system of record accurately such that errors of &gt;0.1 miles can exist.</horizpae>
                </qhorizpa>
            </horizpa>
            <vertacc/>
        </posacc>
        <lineage>
            <srcinfo>
                <srccite>
                    <citeinfo>
                        <origin>Spatial Intelligence Group | EDM | ITD | Virginia Department of Transportation</origin>
                        <title>GISE.GIS_DATA.ROAD</title>
                        <geoform>vector digital data</geoform>
                        <pubinfo>
                            <pubplace>Richmond, Virginia</pubplace>
                            <publish>Spatial Intelligence Group | EDM | ITD | Virginia Department of Transportation</publish>
                        </pubinfo>
                    </citeinfo>
                </srccite>
                <srcscale>6000</srcscale>
                <typesrc>ArcSDE data layer</typesrc>
                <srctime>
                    <timeinfo>
                        <sngdate>
                            <caldate>20190129</caldate>
                        </sngdate>
                    </timeinfo>
                    <srccurr>publication date</srccurr>
                </srctime>
                <srccitea>GISE.GIS_DATA.ROAD</srccitea>
                <srccontr>
This feature class provides geometric shapes and basic route attribution for all roadway centerlines. 

This layer is updated continuously, therefore any rebuild of the linearly referenced features will utilize the latest available data.
</srccontr>
            </srcinfo>
            <srcinfo>
                <srccite>
                    <citeinfo>
                        <origin>Spatial Intelligence Group | EDM | ITD | Virginia Department of Transportation</origin>
                        <pubdate>20190129</pubdate>
                        <title>GISE.GIS_DATA. INTERSECTIONS</title>
                        <geoform>vector digital data</geoform>
                        <pubinfo>
                            <pubplace>Richmond, Virginia</pubplace>
                            <publish>Spatial Intelligence Group | EDM | ITD | Virginia Department of Transportation</publish>
                        </pubinfo>
                    </citeinfo>
                </srccite>
                <srcscale>12000</srcscale>
                <typesrc>ArcSDE data layer</typesrc>
                <srctime>
                    <timeinfo>
                        <sngdate>
                            <caldate>20190129</caldate>
                        </sngdate>
                    </timeinfo>
                    <srccurr>publication date</srccurr>
                </srctime>
                <srccitea>GISE.GIS_DATA. INTERSECTIONS</srccitea>
                <srccontr>The route intersections provide known calibration points for the roadway segments from which the linearly referenced route can be built.</srccontr>
            </srcinfo>
            <procstep>
                <procdesc>
Overview of geoprocessing Route Change Management:
I.	Get the GISE Road source feature class with the latest edits
II.	Get the road edges for the changed routes
a.	After this process is run - Then need to run calc_console.exe to set the 0-1 measures
III.	Delete then append edges by edge-rte-key to OSM and MPST change feature layers
IV.	Create and calibrate Interstate routes with the Mile Post measure points for changed routes
a.	After this process run SQL to update these measures back to the edge features
V.	Build edge-rte-key mile post measured features for changed routes
VI.	Build the Official State Measure - VDOT's official route measure. (OSM) and mile post measure (MPST) changed route features
VII.	Append spatial data view based changed routes to full set for OSM and MPST layers
VIII.	Append spatial data view based change edge-rte-key to full set for OSM and MPST layers
</procdesc>
                <procdate>20190129</procdate>
                <proccont>
                    <cntinfo>
                        <cntorgp>
                            <cntorg>Spatial Intelligence Group | EDM | ITD | Virginia Department of Transportation</cntorg>
                            <cntper>Spatial Intelligence Group | EDM | ITD | Virginia Department of Transportation</cntper>
                        </cntorgp>
                        <cntaddr>
                            <addrtype>mailing and physical address</addrtype>
                            <address>1401 East Broad Street</address>
                            <city>Richmond</city>
                            <state>Virginia</state>
                            <postal>23219-2052</postal>
                        </cntaddr>
                        <cntvoice>804.786.1999</cntvoice>
                        <cntemail>COITDSIG@VDOT.Virginia.Gov</cntemail>
                        <hours>9am - 5pm EST/EDT, M-F</hours>
                    </cntinfo>
                </proccont>
            </procstep>
        </lineage>
    </dataqual>
    <spdoinfo>
        <direct>Vector</direct>
        <ptvctinf>
            <sdtsterm>
                <sdtstype>String</sdtstype>
                <ptvctcnt>0</ptvctcnt>
            </sdtsterm>
        </ptvctinf>
    </spdoinfo>
    <spref>
        <horizsys>
            <geograph>
                <latres>0.000000</latres>
                <longres>0.000000</longres>
                <geogunit>Decimal degrees</geogunit>
            </geograph>
            <geodetic>
                <horizdn>North American Datum of 1983</horizdn>
                <ellips>Geodetic Reference System 80</ellips>
                <semiaxis>6378137.000000</semiaxis>
                <denflat>298.257222</denflat>
            </geodetic>
        </horizsys>
        <vertdef>
            <altsys>
                <altres>0.000100</altres>
                <altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
            </altsys>
        </vertdef>
    </spref>
    <eainfo>
        <detailed>
            <enttyp>
                <enttypl>SDE_VDOT_EDGE_RTE_OVERLAP_LRS</enttypl>
                <enttypd>Linearly Referenced Route Feature Class</enttypd>
                <enttypds>Virginia Department of Transportation</enttypds>
            </enttyp>
            <attr>
                <attrlabl>OBJECTID</attrlabl>
                <attrdef>Internal feature number.</attrdef>
                <attrdefs>ESRI</attrdefs>
                <attrdomv>
                    <udom>Sequential unique whole numbers that are automatically generated.</udom>
                </attrdomv>
            </attr>
            <attr>
                <attrlabl>EDGE_RTE_KEY</attrlabl>
                <attrdef>A key for the route created by combining the unique Transport_Edge_ID as a prefix with the unique Route Name as the suffix.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>RTE_NM</attrlabl>
                <attrdef>The RNS-defined unique name for the route. This name is a unique key used to identify a single route. It is guaranteed not to change over the life of the route for as long as that route exists.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>RTE_COMMON_NM</attrlabl>
                <attrdef>Route Common Name is an abbreviated form of the route name. It includes either name or number of route and directionality of route, as well as jurisdiction if applicable.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>STREET_NM</attrlabl>
                <attrdef>VGIN sourced street name attribute coinciding with the edge based on TRANSPORT_EDGE_ID.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>RTE_SOURCE_ID</attrlabl>
                <attrdef>For HTRIS source, the 14 character HTRIS ROUTE_ID with leading and trailing spaces if applicable. If the Source is GIS, non-prime routes will have the route direction added to the HTRIS ROUTE_ID</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>RTE_SOURCE_CD</attrlabl>
                <attrdef>Source of the Route Name (HTRIS, GIS, VGIN)</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>RTE_TRANSPORT_EDGE_SEQ</attrlabl>
                <attrdef>Order in which the TRANSPORT_EDGE_IDs are joined to create the an LRS for this RTE_NM.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>TRANSPORT_EDGE_ID</attrlabl>
                <attrdef>Unique identifier for the SDE_ROAD centerline segment.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>TRANSPORT_EDGE_FLIP_IND</attrlabl>
                <attrdef>This indicates if the SDE_ROAD transport edge from and to values need to be flipped to correctly align the segment in increasing measure order for the route.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>TRANSPORT_JUNCTION_FROM_ID</attrlabl>
                <attrdef>The Transport_Junction_ID located at the end of the edge with lower milepoint measure.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>TRANSPORT_JUNCTION_TO_ID</attrlabl>
                <attrdef>The Transport_Junction_ID located at the end of the edge with higher milepoint measure.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>MEASURE_SYSTEM_CD</attrlabl>
                <attrdef>Route measure system code</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
                <attrdomv>
                    <edom>
                        <edomv>CALC</edomv>
                        <edomvd>GIS derived geometric miles for routes that lack any of the other measure systems.</edomvd>
                    </edom>
                </attrdomv>
                <attrdomv>
                    <edom>
                        <edomv>OSM</edomv>
                        <edomvd>Official State Measure - VDOT's official route measure.</edomvd>
                        <edomvds>HTRIS</edomvds>
                    </edom>
                </attrdomv>
                <attrdomv>
                    <edom>
                        <edomv>OUM</edomv>
                        <edomvd>Official Urban Measure - Used for street routes in urban areas.</edomvd>
                    </edom>
                </attrdomv>
                <attrdomv>
                    <edom>
                        <edomv>MPST</edomv>
                        <edomvd>Referenced to Mile Post Markers, only on routes with milepost signage</edomvd>
                    </edom>
                </attrdomv>
            </attr>
            <attr>
                <attrlabl>TRANSPORT_EDGE_FROM_MSR</attrlabl>
                <attrdef>For each edge, the cumulative LRS measure for the route at the end of the edge with lower milepoint measure.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>TRANSPORT_EDGE_TO_MSR</attrlabl>
                <attrdef>For each edge, the cumulative LRS measure for the route at the end of the edge with higher milepoint measure.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>FROM_INTERSECTION_ID</attrlabl>
                <attrdef>Intersection_ID at the end of the edge with lower milepoint measure. Similar to Transport_Junction, Intersection_ID is a unique identifier for the point/node features that connect the road centerline segments. All Intersection_IDs have a corresponding Transport_Junction_ID, but not all Transport_Junctions are Intersections. </attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>TO_INTERSECTION_ID</attrlabl>
                <attrdef>Intersection_ID at the end of the edge with higher milepoint measure. Similar to Transport_Junction, Intersection_ID is a unique identifier for the point/node features that connect the road centerline segments. All Intersection_IDs have a corresponding Transport_Junction_ID, but not all Transport_Junctions are Intersections. </attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>RTE_INTERSECTION_FROM_DSC</attrlabl>
                <attrdef>Description of all routes intersecting the From Intersection for an edge.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>RTE_JURIS_PROPER_NM</attrlabl>
                <attrdef>Name of the Jurisdiction the route is associated with for Urban, Streets, and Secondary route categories. All other route categories are multi-jurisdictional and will display null values.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>TO_PHY_JURISDICTION_NM</attrlabl>
                <attrdef>Physical Jurisdiction Name at the to Junction ID</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>RTE_CATEGORY_NM</attrlabl>
                <attrdef>Categories used to classify routes. Examples - Interstate, Interstate Ramps, Interstate Frontage, US Highway Primary, State Highway Primary, Secondary, Urban, Institutional Property, etc. </attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>RTE_NBR</attrlabl>
                <attrdef>The number assigned to the route for route signage. Definitionally, street name based routes will have a null value.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>RTE_TYPE_NM</attrlabl>
                <attrdef>Route Type Name (Interstate, US Highway, State Highway, Secondary Route, Urban Road, Frontage Road) that corresponds to RTE_TYPE_CD in route based LRS layers.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>RTE_TYPE_MODIFIER_NM</attrlabl>
                <attrdef>Route Type Modifier Name is used to differentiate version of a given route type, such as 'Alternate', 'Business/Commercial', 'Bypass', etc. Corresponds to Route Type Modifier Code.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>RTE_TYPE_MODIFIER_SEQ</attrlabl>
                <attrdef>Route Type Modifier Sequence Number is used to differentiate between routes that have multiple instances of the same Route Type Modifier. For example, US-17NB has "Business" route types in 8 different jurisdictions across the state.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>RTE_SPCL_FEATURE_TYPE_CD</attrlabl>
                <attrdef>Route Special Feature Type Code. Abbreviation of RTE_SPCL_FEATURE_TYPE_NM. Values include: CTL, DCR, ICO, LOT, MNT, RFR, RMP, RST, RTO, TES, TIN, WAY, WST</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>RTE_RAMP_CD</attrlabl>
                <attrdef>A code used to uniquely name each of the special feature route paths. For example, ramp A and B designation at the same exit number. </attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>RTE_CATEGORY_SET_CD</attrlabl>
                <attrdef>Used for setting appropriate zoom levels on maps.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
                <attrdomv>
                    <edom>
                        <edomv>VA</edomv>
                        <edomvd>Virginia</edomvd>
                        <edomvds>US Dept of Commerce</edomvds>
                    </edom>
                </attrdomv>
                <attrdomv>
                    <edom>
                        <edomv>TN</edomv>
                        <edomvd>Tennessee</edomvd>
                        <edomvds>US Dept of Commerce</edomvds>
                    </edom>
                </attrdomv>
                <attrdomv>
                    <edom>
                        <edomv>NC</edomv>
                        <edomvd>North Carolina</edomvd>
                        <edomvds>US Dept of Commerce</edomvds>
                    </edom>
                </attrdomv>
                <attrdomv>
                    <edom>
                        <edomv>MD</edomv>
                        <edomvd>Maryland</edomvd>
                        <edomvds>US Dept of Commerce</edomvds>
                    </edom>
                </attrdomv>
                <attrdomv>
                    <edom>
                        <edomv>DC</edomv>
                        <edomvd>District Of Columbia</edomvd>
                        <edomvds>US Dept of Commerce</edomvds>
                    </edom>
                </attrdomv>
                <attrdomv>
                    <edom>
                        <edomv>WV</edomv>
                        <edomvd>West Virginia</edomvd>
                        <edomvds>US Dept of Commerce</edomvds>
                    </edom>
                </attrdomv>
                <attrdomv>
                    <edom>
                        <edomv>KY</edomv>
                        <edomvd>Kentucky</edomvd>
                        <edomvds>US Dept of Commerce</edomvds>
                    </edom>
                </attrdomv>
            </attr>
            <attr>
                <attrlabl>FROM_JURISDICTION_NM</attrlabl>
                <attrdef>Maintenance Jurisdiction name at the From Junction ID</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>TO_JURISDICTION_NM</attrlabl>
                <attrdef>Maintenance Jurisdiction name at the To Junction ID</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>FROM_JURISDICTION_CD</attrlabl>
                <attrdef>Maintenance Jurisdiction code at the From Junction ID</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>TO_JURISDICTION_CD</attrlabl>
                <attrdef>Maintenance Jurisdiction code at the To Junction ID</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>FROM_STATE_CD</attrlabl>
                <attrdef>State abbreviation at the From Junction ID</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>TO_STATE_CD</attrlabl>
                <attrdef>State abbreviation at the To Junction ID</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>MASTER_RTE_NM</attrlabl>
                <attrdef>The master route is the definitive route on any edge upon which all event data is recorded. There can only be one master route for each edge, and this field yields the name of the master route for the given edge.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>MASTER_RTE_COMMON_NM</attrlabl>
                <attrdef>Master Route Common Name is an abbreviated form of the master route name. It includes either name or number of route and directionality of route, as well as jurisdiction if applicable.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>MASTER_RTE_SOURCE_ID</attrlabl>
                <attrdef>For HTRIS source, the 14 character HTRIS ROUTE_ID with leading and trailing spaces if applicable. If the Source is GIS, non-prime routes will have the route direction added to the HTRIS ROUTE_ID</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>RTE_OPPOSITE_DIRECTION_RTE_NM</attrlabl>
                <attrdef>Route name for the route with opposite directionality to the current route. For numbered routes, opposite route pairs are EB/WB and NB/SB. For street name routes, opposite pair is PR/NP.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>RTE_INTERSECTION_TO_DSC</attrlabl>
                <attrdef>Description of all routes intersecting the To Intersection for an edge.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>FROM_PHY_JURISDICTION_CD</attrlabl>
                <attrdef>VDOT's internal code representing the physical jurisdiction at the From Junction for the edge. Jurisdiction codes precede route name or number in the RTE_NM for secondary and street routes.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>FROM_PHY_JURISDICTION_NM</attrlabl>
                <attrdef>Physical Jurisdiction name at the from Junction ID</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>TO_PHY_JURISDICTION_CD</attrlabl>
                <attrdef>VDOT's internal code representing the physical jurisdiction at the To Junction for the edge. Jurisdiction codes precede route name or number in the RTE_NM for secondary and street routes.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>LRM_CURRENCY_DT</attrlabl>
                <attrdef>Linear Referencing Method Currency Date - Date corresponds to the generation of a new route feature or regeneration of an existing route feature's representation.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>CHANGE_STATUS_CD</attrlabl>
                <attrdef>A change in status indicates that changes to geometry or attribution were performed by GIS editing staff or through automated processing. Values are used internally to indicate ongoing route statuses, but for purposes of the LRS Publish, 'CL' for Closed should be the only value, indicating route is finalized.</attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>SHAPE</attrlabl>
                <attrdef>Feature geometry.</attrdef>
                <attrdefs>ESRI</attrdefs>
                <attrdomv>
                    <udom>Coordinates defining the features.</udom>
                </attrdomv>
            </attr>
            <attr>
                <attrlabl>CHANGE_STATUS_DT</attrlabl>
                <attrdef>Date when CHANGE_STATUS_CD was last modified for the feature. </attrdef>
                <attrdefs>SIG | ITD | Virginia Department of Transportation</attrdefs>
            </attr>
            <attr>
                <attrlabl>SHAPE_Length</attrlabl>
                <attrdef>Length of feature in decimal degrees.</attrdef>
                <attrdefs>ESRI</attrdefs>
                <attrdomv>
                    <udom>Positive real numbers that are automatically generated.</udom>
                </attrdomv>
            </attr>
            <attr>
                <attrlabl>RTE_SPCL_FEATURE_NBR</attrlabl>
            </attr>
            <attr>
                <attrlabl>RTE_ID</attrlabl>
            </attr>
        </detailed>
    </eainfo>
    <distinfo>
        <distrib>
            <cntinfo>
                <cntorgp>
                    <cntorg>Spatial Intelligence Group | EDM | ITD | Virginia Department of Transportation</cntorg>
                    <cntper>Spatial Intelligence Group | EDM | ITD | Virginia Department of Transportation</cntper>
                </cntorgp>
                <cntaddr>
                    <addrtype>mailing and physical address</addrtype>
                    <address>1401 East Broad Street</address>
                    <city>Richmond</city>
                    <state>VA</state>
                    <postal>23219-2052</postal>
                    <country>USA</country>
                </cntaddr>
                <cntvoice>804.786.1999</cntvoice>
                <cntemail>COITDSIG@VDOT.Virginia.Gov</cntemail>
                <hours>9am - 5pm EST/EDT M-F</hours>
            </cntinfo>
        </distrib>
        <resdesc>Offline Data</resdesc>
        <distliab>The information depicted in this GIS layer is the result of digital analyses performed on a database consisting of information from a variety of governmental and other credible sources.  The accuracy of the information presented is limited to the collective accuracy of the database on the date of the analysis.  The information is believed accurate and reasonable efforts have been made to ensure the accuracy of the data.  However, the Spatial Intelligence Group, Virginia Department of Transportation expressly disclaims responsibility for damages or liability that may arise from use of this data.</distliab>
        <stdorder>
            <digform>
                <digtinfo>
                    <formname>ESRI data format, dependent upon request</formname>
                </digtinfo>
                <digtopt>
                    <onlinopt>
                        <computer>
                            <networka>
                                <networkr>withheld</networkr>
                            </networka>
                        </computer>
                        <accinstr>Contact COITDSIG@VDOT.Virginia.Gov for access to FTP site.</accinstr>
                    </onlinopt>
                </digtopt>
            </digform>
            <digform>
                <digtinfo>
                    <formname>ESRI Map Service</formname>
                    <formvern>ArcGIS</formvern>
                </digtinfo>
                <digtopt>
                    <onlinopt>
                        <accinstr>Must have access to VDOT internal network.</accinstr>
                    </onlinopt>
                </digtopt>
            </digform>
            <ordering>This data set is available to VDOT users in electronic format as a geodatabase or shapefile via ftp, e-mail attachment or on CD-ROM</ordering>
        </stdorder>
        <techpreq>Must have software capable of processing Zip files and ESRI geodatabses or shapefiles for the download data. Must have software able to read an ESRI map service if using the map service.</techpreq>
    </distinfo>
    <metainfo>
        <metd>20190129</metd>
        <metc>
            <cntinfo>
                <cntorgp>
                    <cntorg>Spatial Intelligence Group | EDM | ITD | Virginia Department of Transportation</cntorg>
                    <cntper>Spatial Intelligence Group | EDM | ITD | Virginia Department of Transportation</cntper>
                </cntorgp>
                <cntaddr>
                    <addrtype>mailing and physical address</addrtype>
                    <address>1401 East Broad Street</address>
                    <city>Richmond</city>
                    <state>Virginia</state>
                    <postal>23219-2052</postal>
                    <country>USA</country>
                </cntaddr>
                <cntvoice>804.786.1999</cntvoice>
                <cntemail>COITDSIG@VDOT.Virginia.Gov</cntemail>
                <hours>9am - 5pm EST/EDT M-F</hours>
            </cntinfo>
        </metc>
        <metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
        <metstdv>FGDC-STD-001-1998</metstdv>
        <mettc>local time</mettc>
        <metextns>
            <onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
            <metprof>ESRI Metadata Profile</metprof>
        </metextns>
        <metextns>
            <onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
            <metprof>ESRI Metadata Profile</metprof>
        </metextns>
        <metextns>
            <onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
            <metprof>ESRI Metadata Profile</metprof>
        </metextns>
        <metextns>
            <onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
            <metprof>ESRI Metadata Profile</metprof>
        </metextns>
    </metainfo>
    <Esri>
        <CreaDate>20191127</CreaDate>
        <CreaTime>09262500</CreaTime>
        <ArcGISFormat>1.0</ArcGISFormat>
        <SyncOnce>TRUE</SyncOnce>
    </Esri>
<dataIdInfo><idAbs>
This feature class consists of approximately 1,750,000 features representing around 70,000 miles of Interstate, Primary, Secondary and Urban roads throughout the State of Virginia. The Linear Referencing System is based on the Virginia Department of Transportation's Source System of Record for road inventory, Roadway Inventory Management System (RIMS).  

Geometry and Attribution:
The Linear Referencing System (LRS) data contained within this feature class provides route centerline geometry that is segmented at each intersection and supplies key descriptive attribution for each segment (i.e. edge) record.  The feature class also depicts overlapping routes (e.g. Interstate 64 and Interstate 95) as two separate collinear features, one on top of the other.  Routes built in the prime and non-prime directions are included.  Each road centerline record has a master route record assigned.  In addition, local Virginia Geographic Information Network (VGIN) street names are attributed to each edge where possible.

Measures:
The linear reference is based on Official State Mileage (OSM) as derived from reference points at Roadway Inventory Management System (RIMS) roadway intersections (i.e. nodes/junctions).
Note: The overlap, non-prime measures and street names are for reference only. These measures and street names have not been fully validated for accuracy or completeness.
 &lt;p&gt;Item is used within the I-81/I-581 Auxiliary Lane Study,
Roanoke County, VA Story Map App.&lt;/p&gt;

&lt;p&gt;http://vdot.maps.arcgis.com/apps/Cascade/index.html?appid=d12d0be1bd1d44f7a9f1447441fd30d2&lt;/p&gt;</idAbs><idPurp>This linear referenced data layer represents roadways that are maintained by the Virginia Department of Transportation and provides the underlying spatially enabled geometric network to which all "events" (e.g. potholes, pavement type, vehicle accidents, traffic counts, culverts, etc...) can be located.</idPurp><searchKeys><keyword>gis</keyword><keyword>vdot</keyword><keyword>transportation</keyword><keyword>Virginia</keyword><keyword>VDOT</keyword><keyword>Virginia Department of Transportation</keyword></searchKeys><resConst><Consts><useLimit>Disclaimer: Any person, organization, firm, corporation or other entity using this database does so at its own risk. The Virginia Department of Transportation accepts no liability for any loss suffered by any person, organization, firm, corporation, or other entity from the use of the information in this database. In addition, the Virginia Department of Transportation does not guarantee system availability and is not responsible for any losses associated with any system unavailability. VDOT's digital data files are for use in performing the official business of the Commonwealth of Virginia. VDOT Divisions set all policy on the allowable uses of this data. The representations of VDOT business data contained within are believed to be correct. This data is provided without any guarantee of accuracy, timeliness or completeness. No business decisions should be made based on this data without first validating its accuracy against the official Source System of Record (SSR). Users of this data are solely responsible for determining if it is appropriate for their application. Please report errors and omissions directly to the appropriate VDOT Division data owner.</useLimit></Consts></resConst></dataIdInfo></metadata>