<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20130424</CreaDate>
<CreaTime>11131200</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="FALSE">Roxboro_Bike_Fac_Linear</itemName>
<imsContentType Sync="TRUE" export="False">002</imsContentType>
<itemSize Sync="TRUE">0.000</itemSize>
<nativeExtBox>
<westBL Sync="TRUE">494678.359819</westBL>
<eastBL Sync="TRUE">3050450.051086</eastBL>
<southBL Sync="TRUE">46865.105283</southBL>
<northBL Sync="TRUE">1042842.475529</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_WGS_1984</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Meter (1.000000)</csUnits>
<projcsn Sync="TRUE">WGS_1984_Web_Mercator_Auxiliary_Sphere</projcsn>
<peXml Sync="TRUE">&lt;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.8'&gt;&lt;WKT&gt;PROJCS[&amp;quot;WGS_1984_Web_Mercator_Auxiliary_Sphere&amp;quot;,GEOGCS[&amp;quot;GCS_WGS_1984&amp;quot;,DATUM[&amp;quot;D_WGS_1984&amp;quot;,SPHEROID[&amp;quot;WGS_1984&amp;quot;,6378137.0,298.257223563]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Mercator_Auxiliary_Sphere&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,0.0],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,0.0],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,0.0],PARAMETER[&amp;quot;Auxiliary_Sphere_Type&amp;quot;,0.0],UNIT[&amp;quot;Meter&amp;quot;,1.0],AUTHORITY[&amp;quot;EPSG&amp;quot;,3857]]&lt;/WKT&gt;&lt;XOrigin&gt;-20037700&lt;/XOrigin&gt;&lt;YOrigin&gt;-30241100&lt;/YOrigin&gt;&lt;XYScale&gt;10000&lt;/XYScale&gt;&lt;ZOrigin&gt;0&lt;/ZOrigin&gt;&lt;ZScale&gt;1&lt;/ZScale&gt;&lt;MOrigin&gt;0&lt;/MOrigin&gt;&lt;MScale&gt;1&lt;/MScale&gt;&lt;XYTolerance&gt;0.001&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.001&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.001&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;102100&lt;/WKID&gt;&lt;LatestWKID&gt;3857&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<SyncDate>20251028</SyncDate>
<SyncTime>15093000</SyncTime>
<ModDate>20251028</ModDate>
<ModTime>15093000</ModTime>
<ArcGISProfile>ISO19139</ArcGISProfile>
<scaleRange>
<minScale>150000000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
<ArcGISFormat>1.0</ArcGISFormat>
</Esri>
<dataIdInfo>
<envirDesc Sync="TRUE"> Version 6.2 (Build 9200) ; Esri ArcGIS 10.9.1.28388</envirDesc>
<dataLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<idCitation>
<resTitle Sync="FALSE">Roxboro_Bike_Fac_Linear</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
<citRespParty>
<rpIndName>Bicycle and Pedestrian Program</rpIndName>
<rpOrgName>Institute for Transportation Research and Education</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<date>
<pubDate>2013-09-17T00:00:00</pubDate>
</date>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<idPurp>Provide linear information and a consistent set of attribute fields for proposed bicycle facilities within the City of Roxboro created through the 2025 Roxboro Bicycle &amp; Pedestrian Plan. </idPurp>
<idCredit>CITY OF ROXBORO, NC. DATA CREATOR - ALTA PLANNING + DESIGN, PROJECT LEAD JASON REYES, PROJECT NUMBER 304.0002024.017.</idCredit>
<searchKeys>
<keyword>PBIN</keyword>
<keyword>NCDOT</keyword>
<keyword>Bicycle</keyword>
<keyword>Complete Streets</keyword>
<keyword>North Carolina</keyword>
<keyword>Integrated Mobility Division</keyword>
<keyword>Roxboro Bicycle &amp; Pedestrian Plan</keyword>
</searchKeys>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-84.123548</westBL>
<eastBL Sync="TRUE">-75.423035</eastBL>
<northBL Sync="TRUE">36.615106</northBL>
<southBL Sync="TRUE">33.775530</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;The North Carolina Department of Transportation shall not be held liable for improper or incorrect use of the data described and/or contained herein. These data and related graphics, where available, are not legal documents and are not intended to be used as such. The information contained in these data is dynamic and will change over time. It is the responsibility of the data user to use the data appropriately and consistent within the limitations of geospatial data in general and these data in particular. The NCDOT gives no warranty, expressed or implied, as to the accuracy, reliability or completeness of the data. &lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;Linear bicycle assets.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<tpCat>
<TopicCatCd value="018"/>
</tpCat>
</dataIdInfo>
<mdLang>
<languageCode Sync="TRUE" value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd Sync="TRUE" value="004"/>
</mdChar>
<distInfo>
<distFormat>
<formatName Sync="FALSE">Feature Class</formatName>
<formatVer>1.0</formatVer>
</distFormat>
<distTranOps>
<transSize Sync="TRUE">0.000</transSize>
</distTranOps>
</distInfo>
<mdHrLv>
<ScopeCd Sync="TRUE" value="005"/>
</mdHrLv>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="3857" value="2264"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">6.18.3(9.3.1.2)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="Roxboro_Bike_Fac_Linear">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="Roxboro_Bike_Fac_Linear">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="3"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">0</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
<eainfo>
<detailed Name="Roxboro_Bike_Fac_Linear">
<enttyp>
<enttypl Sync="FALSE">Roxboro_Bike_Fac_Linear</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">0</enttypc>
<enttypd>Existing and proposed linear bicycle facilities of North Carolina</enttypd>
<enttypds>PBIN</enttypds>
</enttyp>
<attr>
<attrlabl Sync="TRUE">OBJECTID</attrlabl>
<attalias Sync="TRUE">OBJECTID</attalias>
<attrtype Sync="TRUE">OID</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">10</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Internal feature number.</attrdef>
<attrdefs Sync="TRUE">ESRI</attrdefs>
<attrdomv>
<udom Sync="TRUE">Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">DataWeb.DBO.Roxboro_Bike_Fac_Linear.ENTITY</attrlabl>
<attalias Sync="TRUE">DataWeb.DBO.Roxboro_Bike_Fac_Linear.ENTITY</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape</attrlabl>
<attalias Sync="TRUE">Shape</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">4</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="TRUE">Feature geometry.</attrdef>
<attrdefs Sync="TRUE">ESRI</attrdefs>
<attrdomv>
<udom Sync="TRUE">Coordinates defining the features.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">ENTITY</attrlabl>
<attalias Sync="TRUE">Entity</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>ENTITY = For existing facilities, use the credible entity, agency, or organization who is responsible for the collection, storage or maintenance of the bicycle facility data being submitted. For proposed facilities, enter data only from governmental agencies with adopted plans, or entities reporting on professional studies (corridor, feasibility, etc.) where the locality was involved.
</attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<udom>A credible entity, agency, or organization</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">PLAN_YEAR</attrlabl>
<attalias Sync="TRUE">Plan Year</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
<attrdef>PLAN YEAR= If the bicycle linear data is taken from an adopted plan, enter the date in year format in which the plan was adopted. </attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<rdom>
<rdommin>1940</rdommin>
<rdommax>2100</rdommax>
</rdom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">EXST_FACIL</attrlabl>
<attalias Sync="FALSE">Existing Facility Type</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>EXST_FACIL= The inventory of existing linear bicycle facilities. Note that inventories or identification of existing facilities may be from any credible source. Where there is more than one treatment on a roadway segment such as a bike lane on an uphill and shared lane on a downhill, each should be included as a discreet linear data piece. </attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<edom>
<edomv>Bike Lane</edomv>
<edomvd>A marked lane along a portion of the roadway that has been designated for preferential or exclusive use for bicyclists via pavement markings in compliance with the MUTCD. It is intended for one-way travel in the same direction as the adjacent traffic lane.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Buffered Bike Lane</edomv>
<edomvd>A conventional bicycle lane with a designated buffer space, typically delineated by markings, that separates the bicycle lane from the adjacent motor vehicle travel lane and/or parking lane.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Paved Shoulder</edomv>
<edomvd>The portion of the roadway contiguous with the travel lanes that accommodates stopped vehicles, emergency vehicles, and reduces the frequency of pavement maintenance. Shoulders, where paved and of sufficient width, may be used by bicyclists.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Shared Lane</edomv>
<edomvd>A lane of the traveled way that is open to both bicycle and motor vehicle travel where there are improvements in roadway width, signing, or marking for bicycling purposes. Shared Lanes often include improvements such as Shared Lane Markings or are designated as Bicycle Boulevards which must be indicated under the field Existing Signing and Marking. Where intended explicitly for purposes of serving as a bicycling facility, wide outside lanes should also be included in this category.</edomvd>
<edomvds>PBIN</edomvds>
</edom>
<edom>
<edomv>Separated Bike Lane</edomv>
<edomvd>An exclusive bike facility that combines the user experience of a separated path with the on-street infrastructure of a conventional bike lane. Also known as a Cycle Track or Protected Bike Lane.</edomvd>
<edomvds>NC Terminology for Active Travel</edomvds>
</edom>
<edom>
<edomv>Contra-flow Bike Lane </edomv>
<edomvd>Bicycle lanes designed to allow bicyclists to ride in the opposite direction of motor vehicle traffic. </edomvd>
<edomvds>NACTO Urban Bikeway Design Guide, 2011</edomvds>
</edom>
<edom>
<edomv>Other</edomv>
<edomvd>A facility that does not fall under an existing value</edomvd>
<edomvds>PBIN</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">EXST_SIGN</attrlabl>
<attalias Sync="TRUE">Existing Signing and Marking</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>EXST_SIGN = Signing and marking whose primary purpose is to distinguish a facility for bicycling or indicate bicycling routes. Bikeway markings represent any device applied onto the pavement surface and intended to designate a specific right-of-way, direction, potential conflict area, or route option. Connector routes should be classified as bike routes.</attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<edom>
<edomv>Bike Route</edomv>
<edomvd>A segment of road identified as a path of travel for bicyclists between destinations which may have directional and informational Signage and Markings. Routes may exist at the national, state, county and local level.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Wayfinding</edomv>
<edomvd>Comprehensive Signage and/or Markings to guide travelers to their destinations along preferred routes by providing information such as distances or times to reach key destinations or areas.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Bicycle Boulevard</edomv>
<edomvd>A segment of street, or series of contiguous street segments, that has been modified to accommodate through-bicycle traffic and minimize through- motor traffic. There are a variety of facilities that can be used to designate a boulevard including: Signage, Shared Lane Markings, partial- or full-street closures, mini-circles, and other streetscape improvements. Also known as a Neighborhood Greenway.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Shared Lane Markings</edomv>
<edomvd>A pavement marking symbol used to indicate a Shared Lane environment for bicycles and motor vehicles. The markings help assist with bicyclists’ positioning and direction of travel on the roadway, can indicate a preferred bicycling route, and alert motorists of a bicyclist’s likely location on the roadway. Also known as Sharrows.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">COND_BIKE</attrlabl>
<attalias Sync="TRUE">Surface Condition</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>COND_BIKE = Subjective score for surface condition of existing facilities. </attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<edom>
<edomv>Good</edomv>
<edomvd>Facility has a sound surface condition</edomvd>
<edomvds>PBIN</edomvds>
</edom>
<edom>
<edomv>Needs Improvement</edomv>
<edomvd>Facility has a surface feature that needs to be addressed</edomvd>
<edomvds>PBIN</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">PROP_FACIL</attrlabl>
<attalias Sync="TRUE">Proposed Facility Type</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>The inventory of proposed or planned bicycling facilities. This list may not be exhaustive of facilities proposed in future plans. Only governmental agencies with adopted plans, or entities reporting on professional studies (corridor, feasibility, etc.) where the locality was involved should include data on proposed facilities. Where there is more than one treatment on a roadway segment such as a bike lane on an uphill and shared lane on a downhill, each should be included as a discreet linear data piece. </attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<edom>
<edomv>Bike Lane</edomv>
<edomvd>A marked lane along a portion of the roadway that has been designated for preferential or exclusive use for bicyclists via pavement markings in compliance with the MUTCD. It is intended for one-way travel in the same direction as the adjacent traffic lane.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Buffered Bike Lane</edomv>
<edomvd>A conventional bicycle lane with a designated buffer space, typically delineated by markings, that separates the bicycle lane from the adjacent motor vehicle travel lane and/or parking lane.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Paved Shoulder</edomv>
<edomvd>The portion of the roadway contiguous with the travel lanes that accommodates stopped vehicles, emergency vehicles, and reduces the frequency of pavement maintenance. Shoulders, where paved and of sufficient width, may be used by bicyclists.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Shared Lane</edomv>
<edomvd>A lane of the traveled way that is open to both bicycle and motor vehicle travel where there are improvements in roadway width, signing, or marking for bicycling purposes. Shared Lanes often include improvements such as Shared Lane Markings or are designated as Bicycle Boulevards which must be indicated under the field Proposed Signing and Marking. Where intended explicitly for purposes of serving as a bicycling facility, wide outside lanes should also be included in this category.</edomvd>
<edomvds>PBIN</edomvds>
</edom>
<edom>
<edomv>Separated Bike Lane</edomv>
<edomvd>An exclusive bike facility that combines the user experience of a separated path with the on-street infrastructure of a conventional bike lane. Also known as a Cycle Track or Protected Bike Lane.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Contra-flow Bike Lane </edomv>
<edomvd>Bicycle lanes designed to allow bicyclists to ride in the opposite direction of motor vehicle traffic. </edomvd>
<edomvds>NACTO Urban Bikeway Design Guide, 2011</edomvds>
</edom>
<edom>
<edomv>Improvement – unspecified</edomv>
<edomvd>Proposed improvement that is unspecified, typically plan or study level information</edomvd>
<edomvds>PBIN</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">PROP_SIGN</attrlabl>
<attalias Sync="TRUE">Proposed Signing and Marking</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>Proposed signing and marking whose primary purpose is to distinguish a facility for bicycling or indicate bicycling routes. Bikeway markings represent any device applied onto the pavement surface and intended to designate a specific right-of-way, direction, potential conflict area, or route option. Connector routes should be classified as bike routes.</attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<edom>
<edomv>Bike Route</edomv>
<edomvd>A segment of road identified as a path of travel for bicyclists between destinations which may have directional and informational Signage and Markings. Routes may exist at the national, state, county and local level.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Wayfinding</edomv>
<edomvd>Comprehensive Signage and/or Markings to guide travelers to their destinations along preferred routes by providing information such as distances or times to reach key destinations or areas.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Bicycle Boulevard</edomv>
<edomvd>A segment of street, or series of contiguous street segments, that has been modified to accommodate through-bicycle traffic and minimize through- motor traffic. There are a variety of facilities that can be used to designate a boulevard including: Signage, Shared Lane Markings, partial- or full-street closures, mini-circles, and other streetscape improvements. Also known as a Neighborhood Greenway.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Shared Lane Markings</edomv>
<edomvd>A pavement marking symbol used to indicate a Shared Lane environment for bicycles and motor vehicles. The markings help assist with bicyclists’ positioning and direction of travel on the roadway, can indicate a preferred bicycling route, and alert motorists of a bicyclist’s likely location on the roadway. Also known as Sharrows.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Signing Marking Unspecified</edomv>
<edomvd>Proposed signing or marking that is unspecified, typically plan or study level information</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">RDWY_BIKE</attrlabl>
<attalias Sync="TRUE">Roadway</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>RDWY_BIKE = Name of roadway associated with the bicycle facility, where available. Allows for identification of exact roadway segment the bicycle facility corresponds to, even in cases of lack of congruence with roadway shapefiles.</attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<udom>Name of roadway.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">COLCT_YEAR</attrlabl>
<attalias Sync="TRUE">Collection Year</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">5</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>COLCT_YEAR = The date, in year format, when the data was most recently collected and/or updated.</attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<rdom>
<rdommin>1940</rdommin>
<rdommax>2100</rdommax>
</rdom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">CARD_DIRCT</attrlabl>
<attalias Sync="TRUE">Cardinal Direction</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>CARD_DIRCT= Location detail for existing or proposed linear features that may be on one or more sides of a segment. This must be included where more clarification about the placement or position of the facility on the roadway is necessary.</attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<edom>
<edomv>North</edomv>
<edomvd>North side of the roadway</edomvd>
<edomvds>PBIN</edomvds>
</edom>
<edom>
<edomv>South</edomv>
<edomvd>South side of the roadway</edomvd>
<edomvds>PBIN</edomvds>
</edom>
<edom>
<edomv>East</edomv>
<edomvd>East side of the roadway</edomvd>
<edomvds>PBIN</edomvds>
</edom>
<edom>
<edomv>West</edomv>
<edomvd>West side of the roadway</edomvd>
<edomvds>PBIN</edomvds>
</edom>
<edom>
<edomv>Both</edomv>
<edomvd>Both sides of the roadway</edomvd>
<edomvds>PBIN</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">WIDTH</attrlabl>
<attalias Sync="TRUE">Facility Width</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">5</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>WIDTH = Width of the bicycle facility for the majority of a segment. For Bike Lane, Shoulder, Buffered Bike Lane, and Contra-flow Bike Lanes, width is measured from the outermost motor vehicle travel lane to the edge of pavement or boundary of parking lane. The gutter pan on an urban street is not considered part of a bicycle facility. For buffered bike lanes and contra-flow lanes bicycle lanes, the buffer is included in the width if considered by the jurisdiction as a part of the bicycling facility. For Wide Outside Lane and lanes with shared lane markings width is measured as the width of the shared travel lane. </attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<rdom>
<rdommin>4</rdommin>
<rdommax>20</rdommax>
<attrunit>Feet</attrunit>
</rdom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">RMBL_STRP</attrlabl>
<attalias Sync="TRUE">Rumble Strips</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>RMBL_STRP= Indicate the presence or absence of rumble strips along a street segment, and whether the strips are continuous or spaced for bicyclists to cross.</attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<edom>
<edomv>None</edomv>
<edomvd>Not present</edomvd>
<edomvds>PBIN</edomvds>
</edom>
<edom>
<edomv>Continuous</edomv>
<edomvd>Present, without gaps</edomvd>
<edomvds>PBIN</edomvds>
</edom>
<edom>
<edomv>Spaced</edomv>
<edomvd>Present, with gaps</edomvd>
<edomvds>PBIN</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">IMPL_MTHD</attrlabl>
<attalias Sync="TRUE">Implementation Method</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>IMPL_MTHD = The method of implementation identified to install proposed or planned facilities, or to generally improve a roadway segment for bicycling. </attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<edom>
<edomv>Restripe</edomv>
<edomvd>Adjustment in the lateral placement of existing travel lanes to reallocate roadway space for bicyclists or create a greater buffer width between motor vehicle lanes and existing or proposed pedestrian facilities. This adjustment does not remove or add any travel lanes for motor vehicles.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Repave</edomv>
<edomvd>Proposed implementation method to improve a facility for bicyclists by capitalizing on the routine paving or resurfacing maintenance schedule.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Reallocate</edomv>
<edomvd>A technique to modify the number or width of travel lanes to achieve systemic improvements. Variants of reallocation include 4-to-3 lane conversion, lane reduction, road diet, or reconfiguration.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Marking</edomv>
<edomvd>As a proposed implementation method, marking means striping or painting facilities such as shared lane markings or bicycle lanes without any need for additional improvements or adjustments to the roadway. They are intended to provide information, guidance, regulation, or warnings to road users.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Widening</edomv>
<edomvd>Increasing the width of the paved portion of the roadway to specifically improve the roadway segment for a bicycling facility.</edomvd>
<edomvds>PBIN</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">EXST_NAME</attrlabl>
<attalias Sync="TRUE">Existing Facility Name: Local</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>EXST_NAME = The name of the existing signed facility, used for local designations. This is the local name of the bike route, way-finding route or bicycle boulevard. A single route segment may have multiple designations (local, county, state, and national).</attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<udom>The name of the facility.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">EXST_NAME2</attrlabl>
<attalias Sync="TRUE">Existing Facility Name: County</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>EXST_ NAME2 = Name of the existing signed facility, used for county-wide designations. This is the name of the county bike route or way-finding route. A single route segment may have multiple designations (local, county, state, and national).</attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<udom>The name of the facility.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">PROP_NAME</attrlabl>
<attalias Sync="TRUE">Proposed Facility Name</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>PROP_ NAME= The name of the proposed facility. The official name of the bike route, wayfinding or bicycle boulevard identified in the Proposed Signed Facility field. </attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<udom>Proposed facility name.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">EXST_NAME3</attrlabl>
<attalias Sync="TRUE">Existing Facilty Name: State</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>EXST_NAME3 =Name of the existing signed facility, used for statewide designations. This is the name of the state bike route or way-finding route. A single route segment may have multiple designations (local, county, state, and national).</attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<udom>The name of the facility.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">EXST_NAME4</attrlabl>
<attalias Sync="TRUE">Existing Facility Name: National</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>EXST_ NAME4 =Name of the existing signed facility, used for national designations. This is the name of the national bike route or way-finding route. A single route segment may have multiple designations (local, county, state, and national).</attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<udom>The name of the facility.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">INT_YEAR</attrlabl>
<attalias Sync="FALSE">Integration Year</attalias>
<attrtype Sync="TRUE">SmallInteger</attrtype>
<attwidth Sync="TRUE">2</attwidth>
<atprecis Sync="TRUE">5</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>INT_YEAR = The date, in year format when the data was added to the PBIN.</attrdef>
<attrdefs>PBIN</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">PLAN_NAME</attrlabl>
<attalias Sync="FALSE">Plan Name</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>PLAN_NAME = If the bicycle linear data was adopted from a plan, enter the name of the locally adopted plan for which the data was created or compiled.</attrdef>
<attrdefs>PBIN</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape.STLength()</attrlabl>
<attalias Sync="TRUE">Shape.STLength()</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">0</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
</attr>
<attr>
<attrlabl Sync="TRUE">CTP_NAME</attrlabl>
<attalias Sync="FALSE">CTP Name</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>CTP_NAME = If the bicycle linear data is a component of a Comprehensive Transportation Plan, enter the name of the CTP mutually adopted between the state and local area partners.</attrdef>
<attrdefs>PBIN</attrdefs>
</attr>
</detailed>
</eainfo>
<mdDateSt Sync="TRUE">20251028</mdDateSt>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<dataLineage>
<statement>The data contained within this feature class is a result of cleaning and compiling geospatial data from local bicycle plans supported by the NCDOT Planning Grant Initiative (2004-2013) and voluntary submissions from local jurisdictions from a solicitation process starting in early 2013. All relevant bicycling data was preserved from the original data sets and additional information on the jurisdiction from which the data was obtained can be found within the ENTITY field. The data set remains incomplete as solicitation from agencies and jurisdictions within North Carolina is ongoing.</statement>
</dataLineage>
</dqInfo>
<mdContact>
<rpIndName>Bicycle and Pedestrian Program</rpIndName>
<rpOrgName>Institute for Transportation Research and Education</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
<displayName>Bicycle and Pedestrian Program</displayName>
</mdContact>
</metadata>
