20160510 10494100 1.0 FALSE swPIPESTRUCTURES 002 11364136.637971 11388927.977168 6826325.956753 6860618.148339 1 swPIPESTRUCTURES__ATTACHREL Relationship swPIPESTRUCTURES__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 10242200 20230424 10242200 150000000 5000 ItemDescription Version 6.2 (Build 9200) ; Esri ArcGIS 10.8.1.14362 Stormwater Pipe Structures 1 -78.914976 -78.827937 38.487126 38.392686 The stormpipes layer is an arc-based dataset that displays the all of the locations and information of all current storm water pipe structures in the city of Harrisonburg, VA. The data can be digitized using aerial imagery, or can be collected using a GPS-compatible device. Each point in the database should be an accurate representation of what is represented in the field. 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. See also, "swSTORMPIPES" in the ‘STORMSTRUCTURES’ dataset. City of Harrisonburg Harrisonburg Public Works Department STORMSTRUCTURES swPIPESTRUCTURES local government Virginia STORMSTRUCTURE Stormstructures Stormstructure stormstructures stormstructure Storm structures Storm Structures storm structures Storm storm Pipes Pipe pipes pipe Structures Structure structures structure sw STORMPIPES STORMPIPE Stormpipes Stormpipe stormpipes stormpipe Storm pipes Storm pipe storm pipes storm pipe public public works works CityWorks Cityworks cityworks City Works City works city works <DIV STYLE="text-align:Left;">INDEXSection 1: Responsible PartiesSection 2: Explanation of Attribute DataSection 3: Handling of Data and RecommendationsSection 4: Additional ConsiderationsSECTION 1 Responsible PartiesParties responsible for updating this layer:- The GIS Technician at the Community Development office is responsible for entering new features into the dataset from site plans of recent construction projects in the City of Harrisonburg,- The Systems Analyst at 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 Systems Analyst.SECTION 2Explanation of Attribute DataPipeStructureType - type of pipe structure.<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI STYLE="margin:0 0 0 48;">Endwall</LI><LI STYLE="margin:0 0 0 48;">Flared End Section</LI><LI STYLE="margin:0 0 0 48;">Clean Outs</LI></UL>Notes:- Domain: “SW_Pipe_Structure_Type”PipeStructureMaterial – material used for the pipe structure.<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI STYLE="margin:0 0 0 48;">Brick</LI><LI STYLE="margin:0 0 0 48;">CMP</LI><LI STYLE="margin:0 0 0 48;">Concrete</LI><LI STYLE="margin:0 0 0 48;">HDPE-Black</LI><LI STYLE="margin:0 0 0 48;">HDPP-Gray</LI><LI STYLE="margin:0 0 0 48;">RCP</LI></UL>Notes:- Domain: “SW_Pipe_Structure_Material”OwnedBy – owner of the storm pipe structure.<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI STYLE="margin:0 0 0 48;">City</LI><LI STYLE="margin:0 0 0 48;">Other</LI></UL>Notes:- Domain – “SW_Pipe_Structure_Owner”MaintainedBy – party responsible for maintaining stormwater pipe structure.<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI STYLE="margin:0 0 0 48;">City</LI><LI STYLE="margin:0 0 0 48;">Other</LI></UL>Notes:- Domain – “SW_Pipe_Structure_Maintained_byDrainstoMS4 – whether or not the asset drains into the city’s MS4 system.<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI STYLE="margin:0 0 0 48;">Yes</LI><LI STYLE="margin:0 0 0 48;">No</LI></UL>Notes:- Domain: “Drains_To_MS4”Enabled – 1 or 0 Status – refer to status of pipe structure.<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI STYLE="margin:0 0 0 48;">Active</LI><LI STYLE="margin:0 0 0 48;">Abandoned</LI><LI STYLE="margin:0 0 0 48;">Removed</LI><LI STYLE="margin:0 0 0 48;">Proposed</LI></UL>Notes:- Domain: “Storm_Structure_Status”Location – closest address to stormwater pipe structures location, full address - without ZIP code.PlanDate - this is the date of the site plan for the stormwater pipe structure.PlanLink – file path to location where site plans for the corresponding stormwater [pipe structure pipe is found.PipeSize - size of pipeUnique_ID - unique identifying value assigned to a feature, generally same as OBJECTID.Shape – geometric shape of these features are polylines.GlobalID - default editor tracking field, unique serial number for the feature.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.SECTION 3Handling of Data and Recommendations<TABLE STYLE="margin:0 0 0 0;"><TBODY><TR><TD STYLE="padding:1 1 1 1;">Title ofHandlingTopic #1</TD><TD STYLE="padding:1 1 1 1;">[Brief advice/description of how to address a specific component of/issue related to the data.]</TD><TD STYLE="padding:1 1 1 1;">[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </TD></TR><TR><TD STYLE="padding:1 1 1 1;">Title ofHandlingTopic #2</TD><TD STYLE="padding:1 1 1 1;">[Brief advice/description of how to address a specific component of/issue related to the data.]</TD><TD STYLE="padding:1 1 1 1;">[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </TD></TR><TR><TD STYLE="padding:1 1 1 1;">Title ofHandlingTopic #3</TD><TD STYLE="padding:1 1 1 1;">[Brief advice/description of how to address a specific component of/issue related to the data.]</TD><TD STYLE="padding:1 1 1 1;">[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </TD></TR><TR><TD STYLE="padding:1 1 1 1;">Title ofHandlingTopic #4</TD><TD STYLE="padding:1 1 1 1;">[Brief advice/description of how to address a specific component of/issue related to the data.]</TD><TD STYLE="padding:1 1 1 1;">[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </TD></TR><TR><TD STYLE="padding:1 1 1 1;">Title ofHandling Topic #5</TD><TD STYLE="padding:1 1 1 1;">[Brief advice/description of how to address a specific component of/issue related to the data.]</TD><TD STYLE="padding:1 1 1 1;">[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 how and why things 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.)------B. Department Notes - N/AC. Unresolved QuestionsGeometric Network – (direction of flow)D. Other- N/A <DIV><DIV></DIV></DIV></DIV> The swPIPESTRUCTURES data layer was created by Kathy Walker in the Department of Community Development in the City of Harrisonburg, on 5/18/2016. This information was created under the supervision of the Systems Analyst and in association with the GIS Technician at the Department of Community Development for the City of Harrisonburg. Feature Class dataset EPSG 5.3(9.0.0) 0 Simple FALSE 0 TRUE FALSE swPIPESTRUCTURES Feature Class 0 OBJECTID OBJECTID OID 4 10 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. PipeStructureType Pipe_Structure_Type String 255 0 0 PipeStructureMaterial Pipe Structure Material String 255 0 0 OwnedBy Owned By String 50 0 0 MaintainedBy Maintained By String 50 0 0 DrainstoMS4 Drains to MS4 String 50 0 0 Enabled Enabled SmallInteger 2 5 0 Status Status String 255 0 0 Location Location String 255 0 0 PlanDate PlanDate Date 8 0 0 PlanLink PlanLink String 255 0 0 PipeSize PipeSize String 255 0 0 UniqueID Unique ID String 50 0 0 SHAPE SHAPE Geometry 4 0 0 Feature geometry. Esri Coordinates defining the features. 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 20230424