20170214 16540500 1.0 XTools Pro Metadata FALSE stStreets 002 11363228.462951 11389771.842606 6825322.421358 6861897.528654 1 stStreets__ATTACHREL Relationship stStreets__ATTACHREL Relationship Projected GCS_North_American_1983 Linear Unit: Foot_US (0.304801) NAD_1983_StatePlane_Virginia_North_FIPS_4501_Feet <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'><WKT>PROJCS["NAD_1983_StatePlane_Virginia_North_FIPS_4501_Feet",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",11482916.66666666],PARAMETER["False_Northing",6561666.666666666],PARAMETER["Central_Meridian",-78.5],PARAMETER["Standard_Parallel_1",38.03333333333333],PARAMETER["Standard_Parallel_2",39.2],PARAMETER["Latitude_Of_Origin",37.66666666666666],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",2283]]</WKT><XOrigin>-110512500</XOrigin><YOrigin>-88858000</YOrigin><XYScale>3048.00609601219</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.00328083333333333</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>102746</WKID><LatestWKID>2283</LatestWKID></ProjectedCoordinateSystem> 20230424 10393500 20230621 7544900 150000000 5000 ItemDescription Version 6.2 (Build 9200) ; Esri ArcGIS 10.8.1.14362 Streets Paving Schedules 1 -78.918170 -78.824980 38.490647 38.389919 The Streets layer displays the locations and types of all street center lines in the city of Harrisonburg, VA. This layer will be used in conjunction with Cityworks. This layer’s primary purpose is to maintain the Paving Schedule, each of the segments in the layer should be drawn to match its respective paving schedule. The data can be digitized using aerial imagery, or can be collected using a GPS-compatible device. Each line in the database should be an accurate representation of what is on the street. The information already contained within the dataset has been manually collected by the City of Harrisonburg, which has employed the means mentioned above to create and populate the data layer. Please refer to the paving schedule spreadsheet maintained by the Street Division Superintendent, in conjunction with updating this layer. • “StreetPavingInventoryandInspectionEFY” City of Harrisonburg Harrisonburg Public Works Department Street STREET Streets local government Virginia street streets public public works works CityWorks City Works city works city virginia paving schedule paving schedule <DIV STYLE="text-align:Left;"><DIV><DIV>INDEXSection 1: Responsible PartiesSection 2: Explanation of Attribute DataSection 3: Handling of Data and RecommendationsSection 4: Additional ConsiderationsSECTION 1Responsible PartiesParties responsible for updating this layer:- The Public Works Department is responsible for updating and maintaining this layer. Additions or editing of features within this layer should be administered or approved by the Asset Manager.- The Street Division Superintendent at the Public Works Department is responsible for updating and maintaining paving schedule spreadsheet(s)/information.SECTION 2Explanation of Attribute DataUniqueID - Unique identifying value assigned to a feature, generally same as OBJECTID. Assets created after May 2023 follow new UniqueID value: Month & Year + OBJECTID – Example: If the asset was created in June of 2023, the Unique ID will be 0623 - OBJECTIDRoadName– name of the individual road segment identified in the paving schedule.Lanes - number of traffic lanes in segment.SpeedLimit– speed limit in mph of the segment.StreetClassification– VDOT classification of Street<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>Principal Arterial</LI><LI>Minor Arterial</LI><LI>Major Collector</LI><LI>Minor Collector</LI><LI>Local</LI><LI>Non-VDOT Street</LI><LI>Alley</LI></UL>Notes:- Domain: “Street_Classification”StreetDesignation– Whether street is NHS or Non-NHS<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>NHS</LI><LI>Non-NHS</LI></UL>Notes:- Domain: “Street_Designation”BikeLanes– Does the street have bike lanes along segment?<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>Yes</LI><LI>No</LI></UL>Notes:- Domain: “Street_Bike_Lanes”CenterTurnLane– whether or not there is a center turn lane in the segment.<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>Yes</LI><LI>No</LI></UL>Notes:- Domain: “Center_Turn_Lane”Length– (feet) the total length or the street featureInstallDate- this is the year that the street segment was last paved.VDOTConditionAssesment– VDOT CCI rating value.VCADate– date of the VDOT Condition Assesment.LastInspectionDate- date of the last inspection on the street.Condition– conditional status that describes the street - this should be found in the Inspection Report.ConditionDate– date that the condition that the street was inspected.Enabled– 1 or 0Attachment– static photo of the street.Plan Link– file path to location where site plans for the corresponding street is found.InspectionsLink- link to the City Works report form.Location – closest address to street ‘s location, full address - without ZIP code.PlanDate – date of the site plan where the corresponding street is found.created_user– default editor tracking field, who created the feature.created_date– default editor tracking field, when the feature was created.last_edited_user– default editor tracking field, who last edited the feature.last_edited_date- default editor tracking field, when the feature was last edited.GlobalID- default editor tracking field, unique serial number for the feature.Shape– geometric shape of these features are polylines.Shape.STLength()– default field, length of the polyline.SECTION 3Handling of Data and Recommendations<TABLE><TBODY><TR><TD>Title ofHandlingTopic #1</TD><TD>[Brief advice/description of how to address a specific component of/issue related to the data.]</TD><TD>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </TD></TR><TR><TD>Title ofHandlingTopic #2</TD><TD>[Brief advice/description of how to address a specific component of/issue related to the data.]</TD><TD>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </TD></TR><TR><TD>Title ofHandlingTopic #3</TD><TD>[Brief advice/description of how to address a specific component of/issue related to the data.]</TD><TD>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </TD></TR><TR><TD>Title ofHandlingTopic #4</TD><TD>[Brief advice/description of how to address a specific component of/issue related to the data.]</TD><TD>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </TD></TR><TR><TD>Title ofHandling Topic #5</TD><TD>[Brief advice/description of how to address a specific component of/issue related to the data.]</TD><TD>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </TD></TR></TBODY></TABLE>SECTION 4Additional ConsiderationsA. History & Logic of the Data[For future reference, please list facets of the history of the decision-making process related to the data’s use – the howand whythings were specifically done the way that they were.] (If the data should be handled/collected a specific way, that should be listed and explained here.)------- N/AB. Department Notes- N/AC. Unresolved Questions- N/AD. Other- N/A</DIV></DIV></DIV> The Streets data layer was created by Nate Rexrode in the Public Works Department of the City of Harrisonburg, on 5/1/2017. This information was created under the supervision of the Systems Analyst and in association with the GIS Administrator for the City of Harrisonburg. Feature Class dataset EPSG 5.3(9.0.0) 0 Simple FALSE 0 TRUE FALSE stStreets Feature Class 0 OBJECTID OBJECTID OID 4 10 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. SHAPE SHAPE Geometry 4 0 0 Feature geometry. Esri Coordinates defining the features. UniqueID Unique ID String 50 0 0 RoadName Name String 255 0 0 Lanes Lanes SmallInteger 2 5 0 SpeedLimit Speed Limit SmallInteger 2 5 0 StreetClassification Street Classification String 255 0 0 StreetDesignation Street Designation String 255 0 0 BikeLanes Bike Lanes String 255 0 0 CenterTurnLane Center Turn Lane String 255 0 0 Length Length Integer 4 10 0 InstallDate Install Date Date 8 0 0 VDOTConditionAssesment VDOT Condition Assesment String 255 0 0 VCADate VCA Date Date 8 0 0 CityConditionAssessment City Condition Assessment String 255 0 0 CCADate CCA Date Date 8 0 0 Enabled Enabled SmallInteger 2 5 0 Attachment Attachment String 255 0 0 PlanLink Plan Link String 255 0 0 InspectionLink Inspection Link String 255 0 0 created_user created_user String 255 0 0 created_date created_date Date 8 0 0 last_edited_user last_edited_user String 255 0 0 last_edited_date last_edited_date Date 8 0 0 LastInspectionDate Last Inspection Date Date 8 0 0 SHAPE.STLength() SHAPE.STLength() Double 0 0 0 20230621