<?xml version="1.0" encoding="UTF-8"?><metadata xml:lang="en">
<Esri>
<CreaDate>20200727</CreaDate>
<CreaTime>12211900</CreaTime>
<SyncOnce>FALSE</SyncOnce>
<SyncDate>20200128</SyncDate>
<SyncTime>15225800</SyncTime>
<ModDate>20210630</ModDate>
<ModTime>8352100</ModTime>
<ArcGISFormat>1.0</ArcGISFormat>
<DataProperties>
<itemProps>
<itemName Sync="TRUE">roadway_classifications</itemName>
<nativeExtBox>
<westBL Sync="TRUE">1265464.438803</westBL>
<eastBL Sync="TRUE">1290878.932266</eastBL>
<southBL Sync="TRUE">57166.874965</southBL>
<northBL Sync="TRUE">84012.292075</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
<itemSize Sync="TRUE">0.019</itemSize>
<imsContentType Sync="TRUE" export="False">002</imsContentType>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Foot_US (0.304801)</csUnits>
<projcsn Sync="TRUE">NAD_1983_StatePlane_Washington_North_FIPS_4601_Feet</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.6'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_StatePlane_Washington_North_FIPS_4601_Feet&amp;quot;,GEOGCS[&amp;quot;GCS_North_American_1983&amp;quot;,DATUM[&amp;quot;D_North_American_1983&amp;quot;,SPHEROID[&amp;quot;GRS_1980&amp;quot;,6378137.0,298.257222101]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Lambert_Conformal_Conic&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,1640416.666666667],PARAMETER[&amp;quot;False_Northing&amp;quot;,0.0],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-120.8333333333333],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,47.5],PARAMETER[&amp;quot;Standard_Parallel_2&amp;quot;,48.73333333333333],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,47.0],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;EPSG&amp;quot;,2285]]&lt;/WKT&gt;&lt;XOrigin&gt;-117104300&lt;/XOrigin&gt;&lt;YOrigin&gt;-99539600&lt;/YOrigin&gt;&lt;XYScale&gt;3048.0060960121928&lt;/XYScale&gt;&lt;ZOrigin&gt;-100000&lt;/ZOrigin&gt;&lt;ZScale&gt;10000&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;10000&lt;/MScale&gt;&lt;XYTolerance&gt;0.0032808333333333331&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;102748&lt;/WKID&gt;&lt;LatestWKID&gt;2285&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<ArcGISstyle>FGDC CSDGM Metadata</ArcGISstyle>
<ArcGISProfile>FGDC</ArcGISProfile>
<scaleRange>
<minScale>50000</minScale>
<maxScale>5000</maxScale>
</scaleRange>
</Esri>
<mdLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</mdLang>
<mdChar>
<CharSetCd value="004"/>
</mdChar>
<mdHrLv>
<ScopeCd value="005"/>
</mdHrLv>
<mdContact>
<rpIndName>Katie Baker</rpIndName>
<rpOrgName>City of Puyallup</rpOrgName>
<rpPosName>Senior Planner IACP</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum tddtty="">253-435-3604</voiceNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>333 South Meridian, 2nd Floor</delPoint>
<city>Puyallup</city>
<adminArea>WA</adminArea>
<postCode>98371</postCode>
<country>US</country>
</cntAddress>
<cntHours>8AM - 5PM</cntHours>
</rpCntInfo>
<role>
<RoleCd value="006"/>
</role>
</mdContact>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<distInfo>
<distributor>
<distorCont>
<rpIndName>Jennifer Recco</rpIndName>
<rpOrgName>City of Puyallup</rpOrgName>
<rpPosName>GIS Coordinator</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum>253-841-5571</voiceNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>333 South Meridian, 4th Floor</delPoint>
<city>Puyallup</city>
<adminArea>WA</adminArea>
<postCode>98371</postCode>
<eMailAdd>jennifer@ci.puyallup.wa.us</eMailAdd>
</cntAddress>
<cntHours>8AM - 5PM</cntHours>
</rpCntInfo>
<role>
<RoleCd value="005"/>
</role>
</distorCont>
<distorOrdPrc>
<resFees>There is a cost for the CD. Please contact the distributor for details.</resFees>
<ordInstr>Public Records Request form and GIS Digital Data Disclaimer must be completed and returned to the distributor prior to the data being released if requested on media. Once both forms are received the data can be burned to a CD/DVD and mailed or readied for pick-up at the 2nd floor front counter of City Hall.
Published City data is available on the City's website: http://www.cityofpuyallup.org/business/gis-data/ Please read the Disclaimer to and Warrant by Users of the data and the data's metadata prior to downloading the data. There is no cost to download the data. </ordInstr>
<ordTurn>Within two weeks from the date of the Public Record Request if requested on media.</ordTurn>
<planAvDtTm>2018-04-09T00:00:00</planAvDtTm>
<planAvTmPd>
<tmBegin>2018-04-09T00:00:00</tmBegin>
</planAvTmPd>
</distorOrdPrc>
</distributor>
<distFormat>
<formatName Sync="TRUE">File Geodatabase Feature Class</formatName>
</distFormat>
</distInfo>
<dataIdInfo>
<idCitation>
<date>
<pubDate>2018-04-13T00:00:00</pubDate>
<createDate>2015-05-07T00:00:00</createDate>
<reviseDate>2015-06-24T00:00:00</reviseDate>
</date>
<citRespParty>
<rpOrgName>City of Puyallup</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
<rpIndName>Jennifer Recco</rpIndName>
<rpPosName>GIS Coordinator</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<delPoint>333 South Meridian, 4th Floor</delPoint>
<city>Puyallup</city>
<adminArea>WA</adminArea>
<postCode>98371</postCode>
<eMailAdd>jennifer@ci.puyallup.wa.us</eMailAdd>
</cntAddress>
<cntPhone>
<voiceNum>253-841-5571</voiceNum>
</cntPhone>
</rpCntInfo>
</citRespParty>
<otherCitDet>Obtain from the Comprehensive Plan 1994 (updated as of 12/31/2006) in section Transportation Element regarding map figure VI-8. In 2015 the City's Comprehensive Plan was updated, and consultant hired to update the Tranportation Element which resulted in the original data being modified to meet current standards. This information can be found in the updated Map 7-3 found in the Transportation Element. The updated Comprehensive Plan was adopted by Ordinance #3102 effective December 27, 2015.</otherCitDet>
<citRespParty>
<rpIndName>Peter Nguyen</rpIndName>
<rpOrgName>Fehr and Peers</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
<rpCntInfo>
<cntAddress addressType="both">
<city>Seattle</city>
<adminArea>WA</adminArea>
<eMailAdd>p.nguyen@fehrandpeers.com</eMailAdd>
<delPoint>1001 4th Ave, Ste 4120</delPoint>
<postCode>98154</postCode>
</cntAddress>
<cntPhone>
<voiceNum>206-576-4220</voiceNum>
</cntPhone>
</rpCntInfo>
<rpPosName>Senior GIS Analyst</rpPosName>
</citRespParty>
<resTitle Sync="TRUE">roadway_classifications</resTitle>
<presForm>
<PresFormCd Sync="TRUE" value="005"/>
</presForm>
</idCitation>
<idAbs>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P STYLE="margin:0 0 11 0;"&gt;&lt;SPAN&gt;This feature class is to represent a well-planned system of roadways within the City of Puyallup community. This feature class will provide a future roadway network which will serve the future land use pattern and anticipated growth. The functional classification plan establishes a hierarchy of roadways intended to allow for effective traffic movement within and through the community. The 20-year roadway improvement plan identifies improvements to the arterial/collector and traffic control system needed to serve forecasted growth and travel demands. Anticipated 20-year service levels based on the roadway improvement plan are determined and levels of service for concurrency management are established. Level of service figures are not provided within this feature class. &lt;/SPAN&gt;&lt;/P&gt;&lt;P STYLE="margin:0 0 11 0;"&gt;&lt;SPAN /&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</idAbs>
<idPurp>The purpose of this file geodatabase feature class is to provide, at a glance for planning purposes, the identification of roadway system functional classification. More specifically to: 1. provide for efficient movement of people and goods;
2. guide integration with the associated land use pattern and responsiveness to growth; 3. direct heavily trafficked routes around residential neighborhoods;
4. disperse traffic through an interconnected roadway network; 5. direct interconnectivity with the regional roadway system; 6. and guide support of a transportation demand management strategy which encourages use of alternative transportation modes.
</idPurp>
<idStatus>
<ProgCd value="001"/>
</idStatus>
<idPoC>
<rpIndName>William Keller</rpIndName>
<rpOrgName>City of Puyallup</rpOrgName>
<rpPosName>GIS Coordinator</rpPosName>
<rpCntInfo>
<cntPhone>
<voiceNum tddtty="">253-841-5571</voiceNum>
</cntPhone>
<cntAddress addressType="both">
<delPoint>333 South Meridian, 4th Floor</delPoint>
<city>Puyallup</city>
<adminArea>WA</adminArea>
<postCode>98371</postCode>
<eMailAdd>WKeller@PuyallupWA.gov</eMailAdd>
</cntAddress>
<cntHours>8AM - 5PM</cntHours>
</rpCntInfo>
<role>
<RoleCd value="007"/>
</role>
</idPoC>
<searchKeys>
<keyword>local feeder</keyword>
<keyword>functional classification</keyword>
<keyword>motorized transportation</keyword>
<keyword>principal arterial</keyword>
<keyword>community network</keyword>
<keyword>collector</keyword>
<keyword>minor arterial</keyword>
<keyword>state planned extensions</keyword>
<keyword>roadway network</keyword>
<keyword>neighborhood collector</keyword>
</searchKeys>
<resConst>
<LegConsts>
<othConsts>Disclaimer to and Warranty by Users of City of Puyallup GIS Data 1. Limitations The City of Puyallup makes no warranty, expressed or implied, concerning the data's content, accuracy, currency or completeness, or concerning the results to be obtained from queries or use of the data. ALL DATA IS EXPRESSLY PROVIDED 'AS IS' AND 'WITH ALL FAULTS'. The City of Puyallup makes no warranty of fitness for a particular purpose, and no representation as to the quality of any data. Users of data are responsible for ensuring the accuracy, currency and other qualities of all products (including maps, reports, displays and analysis) produced from or in connection with the City of Puyallup's GIS data. No employee or agent of the City of Puyallup is authorized to waive or modify this paragraph. If a user informs others that a product is based on the City of Puyallup's data, the City of Puyallup specifically requests and directs that the user also disclose the limitations contained in this paragraph and in paragraph 4. 2. Data Interpretation City of Puyallup data is developed and maintained solely for the City of Puyallup business functions, and use or interpretation of data by the Requestor or others is solely their responsibility. The City of Puyallup's Community Development Center will provide data interpretation services. 3. Spatial Accuracy Map data can be plotted or represented at various scales other than the original source of the data. The Requestor is responsible for adhering to industry standard mapping practices which specify that data utilized in a map or analysis, separately or in combination with other data, will be produced at the largest scale common to all data sets. 4. No City of Puyallup Liability City of Puyallup shall not be liable to the Requestor (or transferees or venders or Requestor) for damages of any kind, including lost profits, lost savings or any other incidental of consequential damages relating to the providing of the data or the use of it. The Requestor shall have no remedy by law or equity against the City of Puyallup in the case the data provided is inaccurate, incomplete or otherwise defective in any way. 5. Requester's Warranty Against Commercial Use of Lists RCW 42.17.260 (9) prohibits the release of lists of individuals requested for commercial purposes, and Requestor expressly represents that no such use of any such list will be made by Requestor or its transferee)s) or vender (s). 'Commercial Purposes' means contacting or in some way personally affecting the individuals identified on the list with the purpose of facilitating one's commercial activities. 6. Secondary Data Dissemination Requestors may not secondarily disseminate (give City of Puyallup data to other entities) without prior written permission from the City of Puyallup. 7. Project Data Requestors are encouraged to supply their project data back to the City of Puyallup for use by the City of Puyallup. </othConsts>
<accessConsts>
<RestrictCd value="008"/>
</accessConsts>
<useConsts>
<RestrictCd value="008"/>
</useConsts>
<useLimit>Everyone must read the metadata before using the data. </useLimit>
</LegConsts>
</resConst>
<resConst>
<Consts>
<useLimit>&lt;DIV STYLE="text-align:Left;"&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;All users must read the metadata before using the data.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</useLimit>
</Consts>
</resConst>
<dataLang>
<languageCode value="eng"/>
<countryCode Sync="TRUE" value="USA"/>
</dataLang>
<idCredit>Peter Nguyen, Senior GIS Analyst, Fehr and Peers, Seattle
Jennifer Recco, GIS Coordinator, City of Puyallup</idCredit>
<dataChar>
<CharSetCd value="004"/>
</dataChar>
<resMaint>
<maintFreq>
<MaintFreqCd value="009"/>
</maintFreq>
</resMaint>
<envirDesc Sync="TRUE"> Version 6.2 (Build 9200) ; Esri ArcGIS 10.6.1.9328</envirDesc>
<spatRpType>
<SpatRepTypCd Sync="TRUE" value="001"/>
</spatRpType>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<exTypeCode Sync="TRUE">1</exTypeCode>
<westBL Sync="TRUE">-122.342196</westBL>
<eastBL Sync="TRUE">-122.237977</eastBL>
<northBL Sync="TRUE">47.221555</northBL>
<southBL Sync="TRUE">47.146654</southBL>
</GeoBndBox>
</geoEle>
</dataExt>
<tpCat>
<TopicCatCd value="018"/>
</tpCat>
</dataIdInfo>
<mdMaint>
<maintFreq>
<MaintFreqCd value="009"/>
</maintFreq>
</mdMaint>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005"/>
</scpLvl>
</dqScope>
<dataLineage>
<dataSource type="">
<srcCitatn>
<date>
<pubDate>2008-08-05</pubDate>
</date>
<citRespParty>
<rpOrgName>City of Puyallup</rpOrgName>
<role>
<RoleCd value="006"/>
</role>
</citRespParty>
<otherCitDet>City of Puyallup Comprehensive Plan 1994 (updated as of 12/31/2006) section Transportation Element referenceing map figure VI-8.</otherCitDet>
<resTitle>rdwy_sys_functional_class</resTitle>
<resAltTitle>roadway system functional classification</resAltTitle>
<collTitle>NA</collTitle>
</srcCitatn>
<srcExt>
<tempEle>
<TempExtent>
<exTemp>
<TM_Period>
<tmBegin>2006-12-31</tmBegin>
<tmEnd>2009-08-05</tmEnd>
</TM_Period>
</exTemp>
</TempExtent>
</tempEle>
</srcExt>
<srcDesc>Figure VI-8 in the Transportation Element of the Comprehensive Plan and all relavant shapefiles were used as a base for this update performed by Fehr and Peers in 2015. </srcDesc>
</dataSource>
<statement>There were multiple shapefiles created by classification used in the existing map figure VI-8 of the Comprehensive Plan. These were copied and new fields were added: (Status, Class, NumOfLanes, ROW_Width, Post_Speed, Exp_DTraff) to each shapefile. The datasets where edited by snapping Pierce County roads and splitting based on criteria:(Future Rdwy Conn, Future Rdwy Segment, New Link Proj). The use of the split tool is to calculate future queries. Each shapefile was merged, using the merge tool in ArcToolbox.
In 2015 Fehr and Peers performed an assessment and edited existing data to meet criteria for the 2015 Comprehensive Plan Transportation Element update. The new Roadway Classification file was created from classifications used in the previous map figure VI-8 of the Comprehensive Plan. Fields that were updated and/or added include: Status, NumOfLanes, ROW_Width, Post_Speed, Exp_DTraff, ClassFut, and Miles. The dataset was created by editing with the use of snapping and splitting tools. Existing Pierce County roads were referenced in the creation of this data. this new data was delivered as a file geodatabase. </statement>
<prcStep>
<stepDesc>There were multiple shapefiles created by classifications used in the existing map figure VI-8 of the Comprehensive Plan. These were copied and new fields were added: (Status, Class, NumOfLanes, ROW_Width, Post_Speed, Exp_DTraff) to each shapefile. The datasets where edited by snapping Pierce County roads and splitting based on criteria:(Future Rdwy Conn, Future Rdwy Segment, New Link Proj). The use of the split tool is to caluclate future queries. Each shapefiles was merged, using the merge tool in ArcToolbox.
In 2015 Fehr and Peers perfromed an assessment and edited the data to meet criteria for the 2015 Comprehensive Plan Transportation Element update. The new RoadClass file was created from classifications used in the previous map figure VI-8 of the Comprehensive Plan. Fields that were updated and/or added include: Status, NumOfLanes, ROW_Width, Post_Speed, Exp_DTraff, ClassFut, and Miles. The dataset was created by editing with the use of snapping and splitting tools. Existing Pierce County roads were referenced in the creation of this data.</stepDesc>
<stepRat>Washington State mandates that the Comprehensive Plan is updated every eight (8) years. The Transportation Element was updated utilizing 20 year growth allocations resulting in the Roadway Classifications being updated in 2015. </stepRat>
<stepProc>
<rpIndName>Peter Nguyen</rpIndName>
<rpOrgName>Fehr and Peers</rpOrgName>
<role>
<RoleCd value="011"/>
</role>
<rpCntInfo>
<cntAddress addressType="both">
<city>Seattle</city>
<adminArea>WA</adminArea>
<eMailAdd>p.nguyen@fehrandpeers.com</eMailAdd>
<delPoint>1001 4th Ave, Ste 4120</delPoint>
<postCode>98154</postCode>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum>206-576-4220</voiceNum>
</cntPhone>
</rpCntInfo>
<displayName>Peter Nguyen</displayName>
<rpPosName>Senior GIS Analyst</rpPosName>
</stepProc>
<stepDateTm>2015-05-07T00:00:00</stepDateTm>
</prcStep>
</dataLineage>
</dqInfo>
<eainfo>
<detailed Name="roadway_classifications">
<enttyp>
<enttypl Sync="TRUE">roadway_classifications</enttypl>
<enttypt Sync="TRUE">Feature Class</enttypt>
<enttypc Sync="TRUE">118</enttypc>
</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">0</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">Shape</attrlabl>
<attalias Sync="TRUE">Shape</attalias>
<attrtype Sync="TRUE">Geometry</attrtype>
<attwidth Sync="TRUE">0</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">Status</attrlabl>
<attalias Sync="TRUE">Status</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<attrdef>Future Roadway</attrdef>
<attrdomv>
<edom>
<edomv>Future Rdwy Conn</edomv>
<edomvd>Future Roadway Connection</edomvd>
<edomvds>Fehr and Peers</edomvds>
</edom>
<edom>
<edomv>Future Rdwy Segment</edomv>
<edomvd>Future Roadway Sepment</edomvd>
<edomvds>Fehr and Peers</edomvds>
</edom>
<udom Sync="TRUE"/>
</attrdomv>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdefs Sync="TRUE">Esri</attrdefs>
</attr>
<attr>
<attrlabl Sync="TRUE">NumOfLanes</attrlabl>
<attalias Sync="TRUE">Number of Lanes</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">5</attwidth>
<attrdef>Varied to accomodate the anticipated volume</attrdef>
<attrdefs>City of Puyallup - Comprehensive Plan</attrdefs>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<udom Sync="TRUE"/>
</attrdomv>
<attrdomv>
<edom>
<edomv>2/3</edomv>
<edomvd>Two or three lanes</edomvd>
<edomvds>Field verification; Fehr and Peers</edomvds>
</edom>
<edom>
<edomv>'Null'</edomv>
<edomvd>No value noted</edomvd>
<edomvds>Fehr and Peers</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">ROW_Width</attrlabl>
<attalias Sync="FALSE">ROW Width</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">15</attwidth>
<attrdef>Right of Way Width (feet)</attrdef>
<attrdefs>City of Puyallup - Comprehensive Plan</attrdefs>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<udom Sync="TRUE"/>
</attrdomv>
<attrdomv>
<edom>
<edomv>'Null'</edomv>
<edomvd>No value noted</edomvd>
<edomvds>Fehr and Peers</edomvds>
</edom>
<edom>
<edomv>60-70</edomv>
<edomvd>60 ft to 70 ft</edomvd>
<edomvds>Field verification; Fehr and Peers</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">Post_Speed</attrlabl>
<attalias Sync="TRUE">Posted Speed</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">10</attwidth>
<attrdef>Posted Speed - miles per hour (mph)</attrdef>
<attrdefs>City of Puyallup - Comprehensive Plan</attrdefs>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<udom Sync="TRUE"/>
</attrdomv>
<attrdomv>
<edom>
<edomv>25</edomv>
<edomvd>25 miles per hour</edomvd>
<edomvds>Field verification</edomvds>
</edom>
<edom>
<edomv>'Null'</edomv>
<edomvd>No value noted</edomvd>
<edomvds>Fehr and Peers</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">Exp_DTraff</attrlabl>
<attalias Sync="FALSE">Expected Daily Traffic</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">20</attwidth>
<attrdef>Expected Daily Traffic</attrdef>
<attrdefs>City of Puyallup and Fehr and Peers</attrdefs>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdomv>
<udom Sync="TRUE"/>
</attrdomv>
<attrdomv>
<edom>
<edomv>8,000 - 20,000</edomv>
<edomvd>trips per day</edomvd>
<edomvds>Fehr and Peers</edomvds>
</edom>
<edom>
<edomv>'Null'</edomv>
<edomvd>No value noted</edomvd>
<edomvds>Fehr and Peers</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">ClassFut</attrlabl>
<attalias Sync="TRUE">Roadway Classification</attalias>
<attrtype Sync="TRUE">String</attrtype>
<attwidth Sync="TRUE">30</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="FALSE">Current Roadway Classification</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE"/>
</attrdomv>
<attrdomv>
<edom>
<edomv>Local Feeder Rd</edomv>
<edomvd>Local Feeder Road: Local streets are the lowest functional classification, providing circulation and access within residential neighborhoods.</edomvd>
<edomvds>City of Puyallup Comphrensive Plan Transportation Element</edomvds>
</edom>
<edom>
<edomv>Major Arterial</edomv>
<edomvd>The highest functional classification and tend to carry the highest volumes. They serve regional through trips and connect Puyallup with the rest of the region.</edomvd>
<edomvds>City of Puyallup Comphrensive Plan Transportation Element</edomvds>
</edom>
<edom>
<edomv>Minor Arterial</edomv>
<edomvd>The next highest functional classification, which are designed for higher volumes, but tend not to be major regional travelways. They provide inter-neighborhood connections. </edomvd>
<edomvds>City of Puyallup Comphrensive Plan Transportation Element</edomvds>
</edom>
<edom>
<edomv>Major Collector</edomv>
<edomvd>Distribute trips between local streets and arterials and serve as transition roadways to or from commercial and residential areas. These are higher volume collectors where streets should be designed to maintain vehicular mobility. </edomvd>
<edomvds>City of Puyallup Comphrensive Plan Transportation Element</edomvds>
</edom>
<edom>
<edomv>Minor Collector</edomv>
<edomvd>These also distribute trips between local streets and arterials and serve as transition roadways to or from commercial and residential areas. They have lower volumes and can include select traffic calming elements to balance experience for all modes with vehicular mobility. </edomvd>
<edomvds>City of Puyallup Comphrensive Plan Transportation Element</edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">Miles</attrlabl>
<attalias Sync="TRUE">Miles</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="FALSE">Shape_Length field divided by 5280 feet</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE"/>
</attrdomv>
<attrdomv>
<edom>
<edomv>.16</edomv>
<edomvd>.16 of a mile</edomvd>
<edomvds>Used the Calculator function to get miles from Shape_Length field by dividing it by 5280 feet. </edomvds>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl Sync="TRUE">Shape_Length</attrlabl>
<attalias Sync="TRUE">Shape_Length</attalias>
<attrtype Sync="TRUE">Double</attrtype>
<attwidth Sync="TRUE">8</attwidth>
<atprecis Sync="TRUE">0</atprecis>
<attscale Sync="TRUE">0</attscale>
<attrdef Sync="FALSE">Length of feature in internal units. (feet)</attrdef>
<attrdefs Sync="TRUE">Esri</attrdefs>
<attrdomv>
<udom Sync="TRUE">Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
</detailed>
</eainfo>
<mdHrLvName Sync="TRUE">dataset</mdHrLvName>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode Sync="TRUE" code="2285"/>
<idCodeSpace Sync="TRUE">EPSG</idCodeSpace>
<idVersion Sync="TRUE">5.3(9.0.0)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<spatRepInfo>
<VectSpatRep>
<geometObjs Name="roadway_classifications">
<geoObjTyp>
<GeoObjTypCd Sync="TRUE" value="002"/>
</geoObjTyp>
<geoObjCnt Sync="TRUE">118</geoObjCnt>
</geometObjs>
<topLvl>
<TopoLevCd Sync="TRUE" value="001"/>
</topLvl>
</VectSpatRep>
</spatRepInfo>
<spdoinfo>
<ptvctinf>
<esriterm Name="roadway_classifications">
<efeatyp Sync="TRUE">Simple</efeatyp>
<efeageom Sync="TRUE" code="3"/>
<esritopo Sync="TRUE">FALSE</esritopo>
<efeacnt Sync="TRUE">118</efeacnt>
<spindex Sync="TRUE">TRUE</spindex>
<linrefer Sync="TRUE">FALSE</linrefer>
</esriterm>
</ptvctinf>
</spdoinfo>
<mdDateSt Sync="TRUE">20210630</mdDateSt>
</metadata>
