20170214 16531000 1.0 FALSE stGenerators 002 stGenerators__ATTACHREL Relationship stGenerators__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 10382000 20230621 7470100 150000000 5000 ItemDescription Version 6.2 (Build 9200) ; Esri ArcGIS 10.8.1.14362 Street Generators <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.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 - OBJECTIDGeneratorNumber – number assigned to a particular generator.Fuel Type – material that the generator is constructed of.<UL><LI>Propane</LI></UL><UL><LI>Natural Gas</LI></UL>Notes:- Domain: “Generator_Fuel_Type”Wattage– (Watts) a measure of electrical power.InstallDate– date the path was installed.MaintainedBy- designation of the entity that is responsible for maintaining the shared use path.LastInspectionDate– date when the generator was last inspected.Condition– conditional status that describes the generator - this should be found in the Inspection Report.ConditionDate– date that the condition of the generator was inspected.Enabled– 1 or 0Attachment– static photo of the generator.PlanLink– file path to location where site plans for the corresponding generator is found, not applicable for all.InspectionLink- link to the City Works report form.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.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 ofHandlingTopic #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.)------B. Department NotesC. Unresolved QuestionsD. Other- N/A</DIV></DIV></DIV> The Generators data layer was created by Nate Rexrode in the Public Works Department of the City of Harrisonburg, in 2017. This information was created under the supervision of the Systems Analyst and in association with the City of Harrisonburg. City of Harrisonburg Harrisonburg Public Works Department Street STREET generators generator Generator Generators local government Virginia street streets public public works works CityWorks City Works city works The street Generators layer is a point layer that displays the location of generators in the city of Harrisonburg, VA. This layer is designed to keep track of generators at PW that the facilities maintenance tech would maintain. 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 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. Feature Class dataset EPSG 5.3(9.0.0) 0 Simple FALSE 0 TRUE FALSE stGenerators 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 GeneratorNumber Generator Number SmallInteger 2 5 0 FuelType Fuel Type String 255 0 0 Wattage Wattage Integer 4 10 0 InstallDate Install Date Date 8 0 0 MaintainedBy Maintained By Integer 4 10 0 LastInspectionDate Last Inspection Date Date 8 0 0 Condition Condition String 255 0 0 ConditionDate Condition Date Date 8 0 0 Enabled Enabled SmallInteger 2 5 0 Attachment Attachment String 255 0 0 PlanLink Plan 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 InspectionLink Inspection Link String 255 0 0 20230621