<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20130424</CreaDate>
<CreaTime>11133500</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<DataProperties>
<itemProps>
<itemName Sync="FALSE">Roxboro_Ped_Fac_Point</itemName>
<imsContentType Sync="TRUE" export="False">002</imsContentType>
<itemSize Sync="TRUE">0.000</itemSize>
<nativeExtBox>
<westBL Sync="TRUE">673262.182768</westBL>
<eastBL Sync="TRUE">3050302.039243</eastBL>
<southBL Sync="TRUE">49268.852444</southBL>
<northBL Sync="TRUE">1011070.858299</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>15094600</SyncTime>
<ModDate>20251028</ModDate>
<ModTime>15094600</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">TPed_Fac_Point</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
<date>
<pubDate>2013-09-17T00:00:00</pubDate>
</date>
<citRespParty>
<rpIndName>Bicycle and Pedestrian Program</rpIndName>
<rpOrgName>Institute for Transportation Research and Education</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
</idCitation>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<idPurp>Provide point information and a consistent set of attribute fields for proposed and existing pedestrian facilities within the City of Roxboro created through the Roxboro Bicycle &amp; Pedestrian Plan. </idPurp>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P STYLE="margin:0 0 14 0;"&gt;&lt;SPAN&gt;Point pedestrian facilities.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<searchKeys>
<keyword>NCDOT</keyword>
<keyword>Division of Bicycle Pedestrian Transportation</keyword>
<keyword>Planning Grant Initiative</keyword>
<keyword>pedestrian</keyword>
<keyword>sidewalk</keyword>
<keyword>Complete Streets</keyword>
<keyword>crosswalk</keyword>
<keyword>ADA</keyword>
<keyword>Roxboro Bicycle &amp; Pedestrian Plan</keyword>
</searchKeys>
<idCredit>CITY OF ROXBORO, NC. DATA CREATOR - ALTA PLANNING + DESIGN, PROJECT LEAD JASON REYES, PROJECT NUMBER 304.0002024.017.</idCredit>
<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>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-83.511698</westBL>
<eastBL Sync="TRUE">-75.427430</eastBL>
<northBL Sync="TRUE">36.527851</northBL>
<southBL Sync="TRUE">33.805157</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<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_Ped_Fac_Point">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="004"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">0</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="Roxboro_Ped_Fac_Point">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="1"/>
<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_Ped_Fac_Point">
<enttyp>
<enttypl Sync="FALSE">Roxboro_Ped_Fac_Point</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">0</enttypc>
<enttypd>Existing and proposed point pedestrian 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_Ped_Fac_Point.ENTITY</attrlabl>
<attalias Sync="TRUE">DataWeb.DBO.Roxboro_Ped_Fac_Point.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">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 pedestrian point 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="TRUE">Existing Facility</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>EXST_FACIL = Inventory of existing pedestrian point features. Note that inventories or identification of existing facilities may be from any credible source. The variables given are not exhaustive and may not include new innovations.</attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<edom>
<edomv>Marked Crosswalk</edomv>
<edomvd>the portion of the roadway for pedestrians to use in crossing the street, designated with markings to illustrate and clarify the crossing location</edomvd>
<edomvds>PBIN</edomvds>
</edom>
<edom>
<edomv>Pedestrian Signal</edomv>
<edomvd>a signal head providing special types of traffic signal indications exclusively intended for controlling pedestrian traffic</edomvd>
<edomvds>PBIN</edomvds>
</edom>
<edom>
<edomv>Rectangular Rapid Flashing Beacon</edomv>
<edomvd>A warning beacon activated by a pedestrian at an uncontrolled crossing location which uses an irregular flash pattern to signal drivers of a pedestrian’s presence and desire to cross.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Pedestrian Hybrid Beacon</edomv>
<edomvd>A pedestrian-activated device used to warn and control traffic at an unsignalized location to assist pedestrians in crossing at a marked Crosswalk. This was previously referred to as "High- intensity Activated crossWALK," or "HAWK" signal.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Curb Ramp</edomv>
<edomvd>A combined ramp and landing to accomplish a change in level at a curb between the sidewalk and the street. This element provides a transitional access between elevations for pedestrians using wheelchairs, strollers or other devices with wheels, and must comply with ADA Standards. </edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Crossing Island</edomv>
<edomvd>A raised island at intersection or mid-block crossing location that helps protect crossing pedestrians from motor vehicles and provides a place of refuge. Also known as a pedestrian refuge island.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Curb Extension</edomv>
<edomvd>An extension of sidewalk, landscape area, or curb line into the roadway that reduces the crossing distance and enhances visibility for pedestrians and may reduce traffic spread.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Pedestrian Underpass</edomv>
<edomvd>A structure or bridge that crosses under a roadway, barrier, or natural feature specific to pedestrian use</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Pedestrian Overpass </edomv>
<edomvd>A structure or bridge that crosses over a roadway, barrier, or natural feature specific to pedestrian use</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Mid-block Crossing</edomv>
<edomvd>a marked crosswalk that occurs in a location other than an intersection</edomvd>
<edomvds>PBIN</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">ADA_PED</attrlabl>
<attalias Sync="TRUE">ADA (binary)</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">38</atprecis>
<attscale Sync="TRUE">8</attscale>
<attrdef>ADA_PED= ADA compliance is denoted by "1"; non-compliance is denoted by "0". Define Curb Ramp as "compliant" when slope, cross-slope, material and flares (if present) comply with PROWAG; truncated domes, or other acceptable detectable warnings, in contrasting color are present; and ramp is located and oriented to head pedestrians in the correct direction for the crossing. Define Pedestrian Signal as "compliant" when APS is present; any pushbuttons are oriented in the direction of travel for the crossing; and the signal timing is correctly calculated per the current MUTCD. This definition is not exhaustive of details that may qualify a pedestrian point feature as ADA compliant.</attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<edom>
<edomv>1</edomv>
<edomvd>ADA Compliant</edomvd>
<edomvds>PBIN</edomvds>
</edom>
<edom>
<edomv>0</edomv>
<edomvd>Not ADA Compliant</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">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>PROP_FACIL = Proposed or planned point pedestrian features. These improvements must come from an adopted plan or from a professional report (feasibility study, corridor study, etc.) generated with involvement of a governmental entity. The variables may not be exhaustive of future plans.</attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<edom>
<edomv>Marked Crosswalk</edomv>
<edomvd>the portion of the roadway for pedestrians to use in crossing the street, designated with markings to illustrate and clarify the crossing location</edomvd>
<edomvds>PBIN</edomvds>
</edom>
<edom>
<edomv>Pedestrian Signal</edomv>
<edomvd>a signal head providing special types of traffic signal indications exclusively intended for controlling pedestrian traffic</edomvd>
<edomvds>PBIN</edomvds>
</edom>
<edom>
<edomv>Rectangular Rapid Flashing Beacon</edomv>
<edomvd>A warning beacon activated by a pedestrian at an uncontrolled crossing location which uses an irregular flash pattern to signal drivers of a pedestrian’s presence and desire to cross.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Pedestrian Hybrid Beacon</edomv>
<edomvd>A pedestrian-activated device used to warn and control traffic at an unsignalized location to assist pedestrians in crossing at a marked Crosswalk. This was previously referred to as "High- intensity Activated crossWALK," or "HAWK" signal.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Curb Ramp</edomv>
<edomvd>A combined ramp and landing to accomplish a change in level at a curb between the sidewalk and the street. This element provides a transitional access between elevations for pedestrians using wheelchairs, strollers or other devices with wheels, and must comply with ADA Standards. </edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Crossing Island</edomv>
<edomvd>A raised island at intersection or mid-block crossing location that helps protect crossing pedestrians from motor vehicles and provides a place of refuge. Also known as a pedestrian refuge island.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Curb Extension</edomv>
<edomvd>An extension of sidewalk, landscape area, or curb line into the roadway that reduces the crossing distance and enhances visibility for pedestrians and may reduce traffic spread</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Pedestrian Underpass</edomv>
<edomvd>A structure or bridge that crosses under a roadway, barrier, or natural feature specific to pedestrian use</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Pedestrian Overpass</edomv>
<edomvd>a structure or bridge that crosses over a roadway, barrier, or natural feature specific to pedestrian use</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Grade Separation - unspecified</edomv>
<edomvd>A facility, such as an overpass, underpass, skywalk, or tunnel that allows pedestrians to avoid conflicts.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015 </edomvds>
</edom>
<edom>
<edomv>Crossing Improvement - unspecified</edomv>
<edomvd>Indicates the need for proposed improvements to pedestrian crossing environment, typically planning level data</edomvd>
<edomvds>NC Terminology for Active Travel, 2015 </edomvds>
</edom>
<edom>
<edomv>Mid-block Crossing</edomv>
<edomvd>a marked crosswalk that occurs in a location other than an intersection.</edomvd>
<edomvds>PBIN</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">RDWY_PED</attrlabl>
<attalias Sync="TRUE">Roadway</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">50</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>RDWY_PED = Name of roadway associated with the pedestrian feature, 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">IMPROVEMNT</attrlabl>
<attalias Sync="TRUE">Proposed Improvement Type</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>IMPROVEMENT = Proposed planning level improvements to existing pedestrian point features. The variables given are not exhaustive and may not include new innovations.</attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<edom>
<edomv>High-Visibility Crosswalk Upgrade</edomv>
<edomvd>marking a crosswalk with diagonal or longitudinal lines parallel to traffic flow, such as the ladder, continental or bar pair marking pattern.</edomvd>
<edomvds>NC Terminology for Active Travel, 2015</edomvds>
</edom>
<edom>
<edomv>Curb Ramp Upgrade</edomv>
<edomvd>an improvement made to an existing ramp without relocating it to bring it into compliance, such as adding detectable warnings, or adjusting the slope</edomvd>
<edomvds>PBIN</edomvds>
</edom>
<edom>
<edomv>Curb Radii Tightening</edomv>
<edomvd>an improvement to the curb radius to improve the environment for pedestrians. This may include general pedestrian facility improvements at the corner, such as installing or moving curb ramps or installing, moving and/or upgrading crosswalks. </edomvd>
<edomvds>PBIN</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">EXST_SIGN</attrlabl>
<attalias Sync="TRUE">Existing Signage</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">80</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>EXST_SIGN= Existing signage with messaging specifically to pedestrians or to motorists about pedestrian activity
• School Advance Crossing Assembly
• School Crossing Sign Assembly
• Pedestrian Traffic (W11-2)
• In-Street Pedestrian/School Crossing (R1-6, R1-6b)
• Overhead Pedestrian Crossing (R1-9)
• Turning Vehicles Yield to Pedestrians (R10-15, R10-15R, R10-15L)
• Yield Here to Pedestrians (R1-5L, R1-5R, R1-5aL, R1-5aR)
• Push Button Signage (R10-3 through R10-26)
• No Pedestrian Crossing (R9-3, R9-3a)
• Handicapped (W11-9)
• School Bus Stop Ahead (S3-1)
• Pedestrian Destination and Guide Sign - unspecified
• Pedestrian Warning - unspecified
• Pedestrian Regulatory - unspecified</attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<codesetd>
<codesetn>Pedestrian Signage from Manual for Uniform Traffic Control Devices</codesetn>
<codesets>MUTCD, 2009.</codesets>
</codesetd>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">PROP_SIGN</attrlabl>
<attalias Sync="TRUE">Proposed Signage</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">80</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>PROP_SIGN= Proposed signage with messaging specifically to pedestrians or to motorists about pedestrian activity
• School Advance Crossing Assembly
• School Crossing Sign Assembly
• Pedestrian Traffic (W11-2)
• In-Street Pedestrian/School Crossing (R1-6, R1-6b)
• Overhead Pedestrian Crossing (R1-9)
• Turning Vehicles Yield to Pedestrians (R10-15, R10-15R, R10-15L)
• Yield Here to Pedestrians (R1-5L, R1-5R, R1-5aL, R1-5aR)
• Push Button Signage (R10-3 through R10-26)
• No Pedestrian Crossing (R9-3, R9-3a)
• Handicapped (W11-9)
• School Bus Stop Ahead (S3-1)
• Pedestrian Destination and Guide Sign - unspecified
• Pedestrian Warning - unspecified
• Pedestrian Regulatory - unspecified</attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<codesetd>
<codesetn>Pedestrian Signage from Manual for Uniform Traffic Control Devices</codesetn>
<codesets>MUTCD, 2009.</codesets>
</codesetd>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">HAZARD</attrlabl>
<attalias Sync="TRUE">Hazards</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef>HAZARD= Inventory of pedestrian point hazards. </attrdef>
<attrdefs>PBIN</attrdefs>
<attrdomv>
<edom>
<edomv>Poor lighting</edomv>
<edomvd>area requires pedestrian lighting improvements</edomvd>
<edomvds>PBIN</edomvds>
</edom>
<edom>
<edomv>Poor drainage</edomv>
<edomvd>area requires drainage improvements</edomvd>
<edomvds>PBIN</edomvds>
</edom>
<edom>
<edomv>Obstacle</edomv>
<edomvd>any physical impediment or protrusion that is within, blocks or infringes on the accessible pedestrian route. Examples may include utilities structures (poles, cabinets, hydrants, etc.), improperly placed street furniture or trees, improperly placed signage, etc.</edomvd>
<edomvds>PBIN</edomvds>
</edom>
</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 pedestrian point 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">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 pedestrian point 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>
<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>
<dqInfo>
<dataLineage>
<statement>The data contained within this feature class is a result of cleaning and compiling geospatial data from local pedestrian 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 pedestrian-level 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>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
</dqInfo>
</metadata>
