Layers:

Layer: Stormwater Pipe Structures (0)

Name: Stormwater Pipe Structures

Display Field: PipeStructureType

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: 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.EndwallFlared End SectionClean OutsNotes:- Domain: “SW_Pipe_Structure_Type”PipeStructureMaterial – material used for the pipe structure.BrickCMPConcreteHDPE-BlackHDPP-GrayRCPNotes:- Domain: “SW_Pipe_Structure_Material”OwnedBy – owner of the storm pipe structure.CityOtherNotes:- Domain – “SW_Pipe_Structure_Owner”MaintainedBy – party responsible for maintaining stormwater pipe structure.CityOtherNotes:- Domain – “SW_Pipe_Structure_Maintained_byDrainstoMS4 – whether or not the asset drains into the city’s MS4 system.YesNoNotes:- Domain: “Drains_To_MS4”Enabled – 1 or 0 Status – refer to status of pipe structure.ActiveAbandonedRemovedProposedNotes:- 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 RecommendationsTitle ofHandlingTopic #1[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #2[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #3[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #4[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandling Topic #5[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] 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

Copyright Text: 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.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 15000.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 1.1363503691822592E7
YMin: 6826329.292332139
XMax: 1.1388927119975282E7
YMax: 6860618.285551262
Spatial Reference: 102746  (2283)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false


HasZ: false

HasM: false

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• PipeStructureType ( type: esriFieldTypeString, alias: Pipe_Structure_Type, length: 255 , Coded Values: [Endwall: Endwall] , [Flared End Section: Flared End Section] , [Clean Outs: Clean Outs] , ...6 more... )
• PipeStructureMaterial ( type: esriFieldTypeString, alias: Pipe Structure Material, length: 255 , Coded Values: [Brick: Brick] , [CMP: CMP] , [Concrete: Concrete] , ...3 more... )
• OwnedBy ( type: esriFieldTypeString, alias: Owned By, length: 50 , Coded Values: [City: City] , [Other: Other] )
• MaintainedBy ( type: esriFieldTypeString, alias: Maintained By, length: 50 , Coded Values: [City: City] , [Other: Other] )
• DrainstoMS4 ( type: esriFieldTypeString, alias: Drains to MS4, length: 50 , Coded Values: [Yes: Yes] , [No: No] )
• Enabled ( type: esriFieldTypeSmallInteger, alias: Enabled )
• Status ( type: esriFieldTypeString, alias: Status, length: 255 , Coded Values: [Active: Active] , [Abandoned: Abandoned] , [Removed: Removed] , ...1 more... )
• Location ( type: esriFieldTypeString, alias: Location, length: 255 )
• PlanDate ( type: esriFieldTypeDate, alias: PlanDate, length: 8 )
• PlanLink ( type: esriFieldTypeString, alias: PlanLink, length: 255 )
• PipeSize ( type: esriFieldTypeString, alias: PipeSize, length: 255 )
• UniqueID ( type: esriFieldTypeString, alias: Unique ID, length: 50 )
• created_user ( type: esriFieldTypeString, alias: created_user, length: 255 )
• created_date ( type: esriFieldTypeDate, alias: created_date, length: 8 )
• last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, length: 255 )
• last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, length: 8 )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )

Layer: Bridges and Culverts (1)

Name: Bridges and Culverts

Display Field: StreetNameLocation

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: 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 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 DataStructureID – identification code from the inspection report.StreetNameLocation – closest address to bridge\culvert’s location, full address - without ZIP code.FeatureIntersected – type of feature intersected by the bridge\road culvert.StreetWaterwayRailroadMultipleNotes:- Domain: “Bridges_Culverts_Feature_Intersected”BridgeorCulvert – whether the asset is a bridge or a road culvert.BridgeCulvertNotes:- Domain: “Bridges_or_Culverts”NumberofCulverts – total number of channels contained within the culvert.SingleDoubleTripleOtherNotes:- Domain: “Number_of_Culverts”CulvertShape – shape of the culvertCircularEllipticalBoxNotes:- Domain: “Culvert_Shape”CulvertMaterial – material of the culvert.Precast ConcreteCMPNotes:- Domain: “Culvert_Material”CulvertWidth – (inches) length of the longest edge\diameter of culvert, value from inspection report.CulvertHeight - (inches) height of the of culvert, value from inspection report.InstallDate - this is the year that the curb was physically installed, value from inspection report.OwnedBy - designation of the entity that has ownership of the curb.CityOtherNotes:- Domain: “Curb_Owned_By”MaintainedBy - designation of the entity that is responsible for maintaining the curb.CityOtherNotes:- Domain: “Curb_Maintained_By”LastInspectionDate - date of the last inspection on the curb.Condition – conditional status that describes the curb - this should be found in the Inspection Report.ConditionDate – date that the condition of the curb was inspected.Enabled – 1 or 0Attachment – static photo of the curb.Plan Link – file path to location where site plans for the corresponding curb is found.InspectionsLink - link to the City Works report form - full path name.Location – closest address to curb’s location, full address - without ZIP code.PlanDate – date of the site plan where the corresponding curb is found.UniqueID - 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 - OBJECTIDcreated_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 RecommendationsPlacement of Point FeatureBridge/culvert points should be placed in the center of the structure, unless they overlap with another feature – if this occurs, offset the culvert point featureIf a culvert overlaps with a bridge feature – refer to the inspection report “Orientation” field to help determine on which side of the culvert to place the point.Inspection ReportsThe current inspection reports for bridges and culverts can be found here: N:\Streets\Maintenance\InventoriesN/ATitle ofHandlingTopic #3[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #4[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandling Topic #5[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] 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.)------7/6/2016 - Initial Planning: Will contain data for Cityworks. This will include road and pedestrian bridges. All bridges and culverts that require structural “bridge” inspections.6/19/2018 – Bridge point features should be maintained in the center of their respective structures, culvert points that overlap a bridge feature should be offset to one of the ends of the culvert – this is determined by the “Orientation” field found in the inspection report. B. Department Notes- Cityworks will need to track:Last Inspection DateConditionCondition NotesLast Maintenance DateSchedule Maintenance - for bridge washing after winter, annually. No other reoccurring scheduled work. Other maintenance work would come from work orders. Work orders C. Unresolved Questions- N/AD. Other- Endwalls are part of the culvert/ bridges

Copyright Text: The BridgesandRoadCulverts data layer was created by Nate Rexrode in the Public Works Department of the City of Harrisonburg, on 7/19/2016. This information was created under the supervision of the Systems Analyst and in association with the Department of Community Development for the City of Harrisonburg.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 15000.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 1.1364168071963832E7
YMin: 6825206.14632839
XMax: 1.1387091261681661E7
YMax: 6856070.549166396
Spatial Reference: 102746  (2283)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false


HasZ: true

HasM: false

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• StructureID ( type: esriFieldTypeString, alias: Structure_ID, length: 255 )
• StreetNameLocation ( type: esriFieldTypeString, alias: Street_Name_Location, length: 255 )
• FeatureIntersected ( type: esriFieldTypeString, alias: Feature_Intersected, length: 255 , Coded Values: [Street: Street] , [Waterway: Waterway] , [Railroad: Railroad] , ...1 more... )
• BridgeorCulvert ( type: esriFieldTypeString, alias: Bridge_or_Culvert, length: 255 , Coded Values: [Bridge: Bridge] , [Culvert: Culvert] )
• NumberofCulverts ( type: esriFieldTypeString, alias: Number_of_Culverts, length: 255 , Coded Values: [Single: Single] , [Double: Double] , [Triple: Triple] , ...1 more... )
• CulvertShape ( type: esriFieldTypeString, alias: Culvert_Shape, length: 255 , Coded Values: [Circular: Circular] , [Elliptical: Elliptical] , [Box: Box] )
• CulvertMaterial ( type: esriFieldTypeString, alias: Culvert_Material, length: 255 , Coded Values: [Precast Concrete: Precast Concrete] , [CMP: CMP] )
• CulvertWidth ( type: esriFieldTypeInteger, alias: Culvert_Width )
• CulvertHeight ( type: esriFieldTypeInteger, alias: Culvert_Height )
• InstallDate ( type: esriFieldTypeDate, alias: Install_Date, length: 8 )
• OwnedBy ( type: esriFieldTypeString, alias: Owned_By, length: 255 , Coded Values: [City: City] , [Other: Other] )
• MaintainedBy ( type: esriFieldTypeString, alias: Maintained_By, length: 255 , Coded Values: [City: City] , [Other: Other] )
• LastInspectionDate ( type: esriFieldTypeString, alias: Last_Inspection_Date, length: 255 )
• Condtion ( type: esriFieldTypeSmallInteger, alias: Condtion )
• ConditonDate ( type: esriFieldTypeDate, alias: Conditon_Date, length: 8 )
• Enabled ( type: esriFieldTypeSmallInteger, alias: Enabled )
• Attachment ( type: esriFieldTypeString, alias: Attachment, length: 255 )
• PlanLink ( type: esriFieldTypeString, alias: Plan_Link, length: 500 )
• InspectionLink ( type: esriFieldTypeString, alias: Inspection_Link, length: 255 )
• PlanDate ( type: esriFieldTypeDate, alias: PlanDate, length: 8 )
• UniqueID ( type: esriFieldTypeString, alias: Unique ID, length: 50 )
• created_user ( type: esriFieldTypeString, alias: created_user, length: 255 )
• created_date ( type: esriFieldTypeDate, alias: created_date, length: 8 )
• last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, length: 255 )
• last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, length: 8 )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )

Layer: Storm Pipes (2)

Name: Storm Pipes

Display Field: ConveyanceType

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: 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 DataConveyance Type – structural type of culvert/stormwater pipe.PipeBox Culvert*Artificial Path– this conveyance type ensures connectivity by filling the visual gaps left between pipe ends and physically large structures represented by points. (KW)Notes:- Domain: “Stormpipe_Conveyance_Type”- *See example in: SECTION 4A PipeShape - shape of stormwater pipe.BoxCircularEllipticalNotes:- Domain: “Stormpipe_Pipe_Shape” CircularPipeSize - (inches) size of circular stormwater pipe.3*4*6*8*10*12151821242730333642485460Notes:- Domain: “Stormpipe_Circular_Pipe_Size”- *See notes in: SECTION 4AOldEllipticalPipeRise – (inches) manual entry field, size of old elliptical stormwater pipe.BoxCulvertSize – (feet) size of box culvert/storm pipe.3 x 23 x 34 x 24 x 34 x 4OtherNotes:- Domain: “Stormpipe_Box_Size”- See question in SECTION 4CPipeMaterial – material construction of the culvert/storm pipe.HDPE – BlackHDPP – GrayCMPSteelRCP - ConcretePVCDuctile IronClayStoneBrickOtherPipe ShapeCircularEllipticalNotes:- Domain: “Stormpipe_Materials”LengthFeet – (feet) the total length or the culvert/stormwater pipe featureInstallDate - this is the year that the culvert/stormwater pipe was physically installed.OwnedBy - designation of the entity that has ownership of the culvert/storm pipe.CityOtherNotes:- Domain: “Stormpipe_Owned_By”MaintainedBy - designation of the entity that is responsible for maintaining the culvert/storm pipe.CityOtherNotes:- Domain: “Stormpipe_Maintained_by”LastInspectionDate - date of the last inspection on the culvert/stormwater pipe.Condition – conditional status that describes the culvert/stormwater pipe - this should be found in the Inspection Report.ConditionDate – date that the condition of the culvert/stormwater pipe was inspected.Enabled – 1 or 0Attachment – static photo of the culvert/stormwater pipe.PlanLink – file path to location where site plans for the corresponding culvert/stormwater pipe is found.InspectionsLink - link to the inspection report form.Status – refer to supervisor on specifications for this field.Location – closest address to culvert/stormwater pipe’s location, full address - without ZIP code.PlanDate - this is the date of the site plan for the culvert/stormwater pipe.DrainstoMS4 – whether or not the asset drains into the city’s MS4 system.YesNoNotes:- Domain: “Drains_To_MS4”OldEllipticalPipeSpan - elliptical pipe size (inches) for RCP.OtherPipeSize - EllipticalPipeRiseSize - size of elliptical pipe rise.14171921222427282932343538424348535758646671737781838795103112117128137142Notes:- Domain: “Elliptical_Pipe_Span_Size”EllipticalPipeSpanSize - size of elliptical pipe span.13151820232429303438424345475152535557596063676871757679838791Notes:- Domain: “Elliptical_Pipe_Span_Size”Unique_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.Shape.STLength() – default field, length of the polyline.SECTION 3Handling of Data and RecommendationsTitle ofHandlingTopic #1[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #2[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #3[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #4[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandling Topic #5[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] 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.)------1/6/2016 – Nate Rexrode (Systems Analyst – Public Works) added new sizes to domains (inches):3468107/6/2016 – SECTION 2: Conveyance Type >> Artificial Path – this conveyance type ensures connectivity by filling the visual gaps left between pipe ends and physically large structures represented by points. (KW)For example: B. Department Notes - N/AC. Unresolved Questions1/11/2016 - I’m not sure where the break point is for box sizes to become culverts (and be inspected with bridges)? (thanhd)12/11/2017 - The reliability of location shown on GIS maps for stormpipes is questionable. We are not confident that storm pipes shown are really where they go. Sometimes we know where the inlet and outlet are for a storm pipe, but not sure what happens under ground in between. How have other communities addressed this? We thought we might do grades for our level of confidence - Location Information: Accurate, Possibly Accurate, Not Accurate?12/11/2017 - Geometric Network – To understand inlet v. outlet of pipes (direction of flow)D. Other- N/A

Copyright Text: The swSTORMPIPES data layer was created by Nate Rexrode in the Public Works Department of the City of Harrisonburg, on 9/19/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.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 15000.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 1.1363278220725164E7
YMin: 6825455.809542984
XMax: 1.1389891207197249E7
YMax: 6861525.827297807
Spatial Reference: 102746  (2283)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSLSSolid
Color: [0, 0, 0, 255]
Width: 4
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false


HasZ: true

HasM: false

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• ConveyanceType ( type: esriFieldTypeString, alias: Conveyance_Type, length: 255 , Coded Values: [Pipe: Pipe] , [Box Culvert: Box Culvert] , [Artifical Path: Artificial Path] )
• PipeShape ( type: esriFieldTypeString, alias: Pipe_Shape, length: 255 , Coded Values: [Box: Box] , [Circular: Circular] , [Elliptical: Elliptical] )
• CircularPipeSize ( type: esriFieldTypeString, alias: Circular Pipe Size (inches), length: 255 , Coded Values: [10: 10] , [12: 12] , [15: 15] , ...19 more... )
• OldEllipticalPipeRise ( type: esriFieldTypeString, alias: Elliptical Pipe Size (inches) for HDPE, HDPP, CMP, Steel, length: 255 )
• BoxCulvertSize ( type: esriFieldTypeString, alias: Box Culvert Size (ft), length: 255 , Coded Values: [3 x 2: 3 x 2] , [3 x 3: 3 x 3] , [4 x 2: 4 x 2] , ...3 more... )
• PipeMaterial ( type: esriFieldTypeString, alias: Pipe_Material, length: 255 , Coded Values: [Brick: Brick] , [Clay: Clay] , [CMP: CMP] , ...11 more... )
• LengthFeet ( type: esriFieldTypeInteger, alias: Length (ft) )
• InstallDate ( type: esriFieldTypeDate, alias: Install_Date, length: 8 )
• OwnedBy ( type: esriFieldTypeString, alias: Owned_By, length: 255 , Coded Values: [City: City] , [Other: Other] )
• MaintainedBy ( type: esriFieldTypeString, alias: Maintained_By, length: 255 , Coded Values: [City: City] , [Other: Other] )
• LastInspectionDate ( type: esriFieldTypeString, alias: Last_Inspection_Date, length: 255 )
• Condition ( type: esriFieldTypeSmallInteger, alias: Condition )
• ConditionDate ( type: esriFieldTypeDate, alias: Condition_Date, length: 8 )
• Enabled ( type: esriFieldTypeSmallInteger, alias: Enabled )
• Attachment ( type: esriFieldTypeString, alias: Attachment, length: 255 )
• PlanLink ( type: esriFieldTypeString, alias: Plan_Link, length: 255 )
• InspectionLink ( type: esriFieldTypeString, alias: Inspection_Link, length: 255 )
• Status ( type: esriFieldTypeString, alias: Status, length: 255 , Coded Values: [Active: Active] , [Abandoned: Abandoned] , [Removed: Removed] , ...1 more... )
• Location ( type: esriFieldTypeString, alias: Location, length: 255 )
• PlanDate ( type: esriFieldTypeDate, alias: PlanDate, length: 8 )
• DrainstoMS4 ( type: esriFieldTypeString, alias: DrainstoMS4, length: 255 , Coded Values: [Yes: Yes] , [No: No] )
• OldEllipticalPipeSpan ( type: esriFieldTypeString, alias: Elliptical Pipe Size (inches) for RCP, length: 255 )
• OtherPipeSize ( type: esriFieldTypeString, alias: OtherPipeSize, length: 255 )
• EllipticalPipeRiseSize ( type: esriFieldTypeSmallInteger, alias: Size of Elliptical Pipe Rise , Coded Values: [14: 14] , [17: 17] , [19: 19] , ...31 more... )
• EllipticalPipeSpanSize ( type: esriFieldTypeSmallInteger, alias: Size of Elliptical Pipe Span , Coded Values: [13: 13] , [15: 15] , [18: 18] , ...28 more... )
• UniqueID ( type: esriFieldTypeString, alias: Unique ID, length: 50 )
• created_user ( type: esriFieldTypeString, alias: created_user, length: 255 )
• created_date ( type: esriFieldTypeDate, alias: created_date, length: 8 )
• last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, length: 255 )
• last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, length: 8 )
• Reinstall_Date ( type: esriFieldTypeDate, alias: Reinstall_Date, length: 8 )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape.STLength() )

Layer: Stormwater Manholes (3)

Name: Stormwater Manholes

Display Field: Type

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: 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 DataType - type of manhole.Cast-In-Place ManholePrecast ManholeNotes:- Domain: “SW_Manhole_Type”Depth – depth of manholeLength – length of face of manholePipe1In - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe2In - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe3In - [Pipe size in inches] [Pipe type] – Ex: 36” CMP Pipe4In - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe5In - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe1Out - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe2Out - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe3Out - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe4Out - [Pipe size in inches] [Pipe type] – Ex: 36” CMPDrainstoMS4 – whether or not the asset drains into the city’s MS4 system.YesNoNotes:- Domain: “Drains_To_MS4”OwnedBy – owner of the manhole.CityOtherNotes:- Domain – “SW_Manhole_Owned_By”MaintainedBy – party responsible for maintaining the manhole.CityOtherNotes:- Domain – “SW_Manhole_Maintained_ByLastInspectionDate - date of the last inspection on the manholeCondition – conditional status that describes the manhole - this should be found in the Inspection Report.ConditionDate – date that the condition of the manhole was inspected.Enabled – 1 or 0 Attachment – static photo of the manhole.PlanLink – link to site plans for manhole.InspectionLink - this is the date of the site plan for the stormwater manhole.InstallDate – file path to location where site plans for the corresponding manhole is found.Status - status of manhole.Location – closest address to stormwater manholes location, full address - without ZIP code.NewDepth – New Depth of manhole.Unique_ID - unique identifying value assigned to a feature, generally same as OBJECTID.Shape – geometric shape of these features are pointsGlobalID - 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 RecommendationsTitle ofHandlingTopic #1[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #2[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #3[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #4[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandling Topic #5[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] 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 Questions-N/AD. Other- N/A

Copyright Text: The swMANHOLES data layer was created by Kathy Walker in the Department of Community Development in the City of Harrisonburg, on 7/13/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.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 15000.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 1.1363548627008498E7
YMin: 6826118.43026498
XMax: 1.1387808939052075E7
YMax: 6860645.724071145
Spatial Reference: 102746  (2283)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false


HasZ: true

HasM: false

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• Type ( type: esriFieldTypeString, alias: Type, length: 255 , Coded Values: [Cast-In-Place Manhole: Cast-In-Place Manhole] , [Precast Manhole: Precast Manhole] )
• Depth ( type: esriFieldTypeString, alias: Depth, length: 255 )
• Length ( type: esriFieldTypeString, alias: Length (ft), length: 255 )
• Pipe1In ( type: esriFieldTypeString, alias: Pipe 1 In (inches), length: 255 )
• Pipe2In ( type: esriFieldTypeString, alias: Pipe 2 In (inches), length: 255 )
• Pipe3In ( type: esriFieldTypeString, alias: Pipe 3 In (inches), length: 255 )
• Pipe4In ( type: esriFieldTypeString, alias: Pipe 4 In (inches), length: 255 )
• Pipe5In ( type: esriFieldTypeString, alias: Pipe 5 In (inches), length: 255 )
• Pipe1Out ( type: esriFieldTypeString, alias: Pipe 1 Out (inches), length: 255 )
• Pipe2Out ( type: esriFieldTypeString, alias: Pipe 2 Out (inches), length: 255 )
• Pipe3Out ( type: esriFieldTypeString, alias: Pipe 3 Out (inches), length: 255 )
• Pipe4Out ( type: esriFieldTypeString, alias: Pipe 4 Out (inches), length: 255 )
• DrainstoMS4 ( type: esriFieldTypeString, alias: Drains to MS4, length: 255 , Coded Values: [Yes: Yes] , [No: No] )
• OwnedBy ( type: esriFieldTypeString, alias: Owned By, length: 255 , Coded Values: [City: City] , [Other: Other] )
• MaintainedBy ( type: esriFieldTypeString, alias: Maintained By, length: 255 , Coded Values: [City: City] , [Other: Other] )
• LastInspectionDate ( type: esriFieldTypeDate, alias: Last Inspection Date, length: 8 )
• Condition ( type: esriFieldTypeSmallInteger, alias: Condition )
• ConditionDate ( type: esriFieldTypeDate, alias: Condition Date, length: 8 )
• Enabled ( type: esriFieldTypeSmallInteger, alias: Enabled )
• Attachment ( type: esriFieldTypeString, alias: Attachment, length: 255 )
• PlanLink ( type: esriFieldTypeString, alias: Plan Link, length: 255 )
• InspectionLink ( type: esriFieldTypeString, alias: Inspection Link, length: 255 )
• InstallDate ( type: esriFieldTypeDate, alias: Install Date, length: 8 )
• Status ( type: esriFieldTypeString, alias: Status, length: 255 , Coded Values: [Active: Active] , [Abandoned: Abandoned] , [Removed: Removed] , ...1 more... )
• Location ( type: esriFieldTypeString, alias: Location, length: 255 )
• NewDepth ( type: esriFieldTypeDouble, alias: Depth )
• UniqueID ( type: esriFieldTypeString, alias: Unique ID, length: 50 )
• created_user ( type: esriFieldTypeString, alias: created_user, length: 255 )
• created_date ( type: esriFieldTypeDate, alias: created_date, length: 8 )
• last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, length: 255 )
• last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, length: 8 )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )

Layer: Low Lying Areas (4)

Name: Low Lying Areas

Display Field: Name

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: 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 DataName – street name low lying area is on.Address – closest address to the low area.Enabled – 1 or 0UniqueID - unique identifying value assigned to a feature, generally same as OBJECTID.Location – location of low lying area.Shape – geometric shape of these features are points.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 RecommendationsTitle ofHandlingTopic #1[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #2[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #3[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #4[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandling Topic #5[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] 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 Questions- N/AD. Other- N/A

Copyright Text: The Low Lying Areas data layer was created by Kathy Walker in the Department of Community Development of the City of Harrisonburg, in 2016. This information was created under the supervision of the Systems Analyst and in association with the City of Harrisonburg.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 15000.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 1.136516876418817E7
YMin: 6829994.426449984
XMax: 1.1388547007785916E7
YMax: 6857289.690100819
Spatial Reference: 102746  (2283)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false


HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• Name ( type: esriFieldTypeString, alias: Name, length: 500 )
• Address ( type: esriFieldTypeString, alias: Address, length: 255 )
• Enabled ( type: esriFieldTypeSmallInteger, alias: Enabled )
• UniqueID ( type: esriFieldTypeString, alias: Unique ID, length: 50 )
• Location ( type: esriFieldTypeString, alias: Location, length: 50 )
• created_user ( type: esriFieldTypeString, alias: created_user, length: 255 )
• created_date ( type: esriFieldTypeDate, alias: created_date, length: 8 )
• last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, length: 255 )
• last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, length: 8 )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )

Layer: Drop Inlets (5)

Name: Drop Inlets

Display Field: Type

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: 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 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 DataType– type of drop inlet that the point represents.CombinationCurb InletGrate InletOtherUnknownNotes:- Domain: “DI_Type”Other– Information on VDOT drop inlet structure type, usually identified in the site plansLength– Length of Face of Drop InletPipe1In - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe2In - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe3In - [Pipe size in inches] [Pipe type] – Ex: 36” CMP Pipe4In - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe5In - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe1Out - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe2Out - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe3Out - [Pipe size in inches] [Pipe type] – Ex: 36” CMPPipe4Out - [Pipe size in inches] [Pipe type] – Ex: 36” CMPDrainstoMS4 – Drop Inlet drains to the cities MS4YesNoNotes:- Domain: “Drains_To_MS4”InstallDate- this is the year that the drop inlet was physically installed.OwnedBy- designation of the entity that has ownership of the drop inlet.CityOtherNotes:- Domain: “DI_Owned_By”MaintainedBy- designation of the entity that is responsible for maintaining the drop inlet.CityOtherNotes:- Domain: “DI_Maintained_By”LastInspectionDate- date of the last inspection on the drop inlet.Condition– conditional status that describes the drop inlet - this should be found in the Inspection Report.ConditionDate– date that the condition of the drop inlet was inspected.Enabled– 1 or 0Attachment– static photo of the drop inlet.InspectionLink- link to the City Works report form.Plan Link– file path to location where site plans for the corresponding drop inlet is found.Status – Status of the drop inletActiveAbandonedRemovedProposedNotes:- Domain: “Storm_Structure_Status”Location – closest address to the drop inlets location, full address - without ZIP code.PlanDate – date of the site plan where the corresponding drop inlet is found.InstallationType – type of drop inlet installationPrecastCast in PlaceNotes:- Domain: “DIInstallationType”NewDepth – depth of drop inletThroatLength – length of drop inlet throat ThroatHeight – height of drop inlet throat (ft)GrateLength – length of drop inlet grate (ft)GrateWidth – width of drop inlet grate (ft)RimElevation – To be Determined (ft) 6/18/2018Grate Diameter– diameter of drop inlet grateUniqueID - unique identifying value assigned to a feature, generally same as OBJECTID.Shape– geometric shape of these features are points.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.Reinstall_Date – date drop inlet was reinstalledSECTION 3Handling of Data and RecommendationsTitle ofHandlingTopic #1[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #2[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #3[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #4[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandling Topic #5[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] 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 Notes- Cityworks will need to track:Last Inspection DateCondition - NumericLast Maintenance DateSchedule MaintenanceC. Unresolved Questions- Geometric Network (Direction of Flow)—Is this possible?D. Other- N/A

Copyright Text: The Drop Inlets data layer was created by Kathy Walker in the Department of Community Development of the City of Harrisonburg, on 6/7/2016. This information was created under the supervision of the Systems Analyst and in association with the City of Harrisonburg.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 15000.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 1.1363537219879076E7
YMin: 6825788.151069894
XMax: 1.1387953615271911E7
YMax: 6860925.582107231
Spatial Reference: 102746  (2283)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false


HasZ: true

HasM: false

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• Type ( type: esriFieldTypeString, alias: Type, length: 255 , Coded Values: [Combination: Combination] , [Curb Inlet: Curb Inlet] , [Grate Inlet: Grate Inlet] , ...2 more... )
• Other ( type: esriFieldTypeString, alias: Other, length: 255 )
• Length ( type: esriFieldTypeString, alias: Length of Face of DI, length: 255 )
• Pipe1In ( type: esriFieldTypeString, alias: Pipe 1 In (inches), length: 255 )
• Pipe2In ( type: esriFieldTypeString, alias: Pipe 2 In (inches), length: 255 )
• Pipe3In ( type: esriFieldTypeString, alias: Pipe 3 In (inches), length: 255 )
• Pipe4In ( type: esriFieldTypeString, alias: Pipe 4 In (inches), length: 255 )
• Pipe5In ( type: esriFieldTypeString, alias: Pipe 5 In (inches), length: 255 )
• Pipe1Out ( type: esriFieldTypeString, alias: Pipe 1 Out (inches), length: 255 )
• Pipe2Out ( type: esriFieldTypeString, alias: Pipe 2 Out (inches), length: 255 )
• Pipe3Out ( type: esriFieldTypeString, alias: Pipe 3 Out (inches), length: 255 )
• Pipe4Out ( type: esriFieldTypeString, alias: Pipe 4 Out (inches), length: 255 )
• DrainstoMS4 ( type: esriFieldTypeString, alias: Drains to MS4, length: 255 , Coded Values: [Yes: Yes] , [No: No] )
• InstallDate ( type: esriFieldTypeDate, alias: Install Date, length: 8 )
• OwnedBy ( type: esriFieldTypeString, alias: Owned By, length: 255 , Coded Values: [City: City] , [Other: Other] )
• MaintainedBy ( type: esriFieldTypeString, alias: Maintained By, length: 255 , Coded Values: [City: City] , [Other: Other] )
• LastInspectionDate ( type: esriFieldTypeDate, alias: Last Inspection Date, length: 8 )
• Condition ( type: esriFieldTypeSmallInteger, alias: Condition )
• ConditionDate ( type: esriFieldTypeDate, alias: Condition Date, length: 8 )
• Enabled ( type: esriFieldTypeSmallInteger, alias: Enabled )
• Attachment ( type: esriFieldTypeString, alias: Attachment, length: 255 )
• InspectionLink ( type: esriFieldTypeString, alias: Inspection Link, length: 255 )
• PlanLink ( type: esriFieldTypeString, alias: Plan Link, length: 255 )
• Status ( type: esriFieldTypeString, alias: Status, length: 255 , Coded Values: [Active: Active] , [Abandoned: Abandoned] , [Removed: Removed] , ...1 more... )
• Location ( type: esriFieldTypeString, alias: Location, length: 255 )
• PlanDate ( type: esriFieldTypeString, alias: Plan Date, length: 255 )
• InstallationType ( type: esriFieldTypeString, alias: Installation Type, length: 255 , Coded Values: [Precast: Precast] , [Cast in Place: Cast in Place] )
• NewDepth ( type: esriFieldTypeDouble, alias: Depth )
• ThroatLength ( type: esriFieldTypeDouble, alias: Throat Length )
• ThroatHeight ( type: esriFieldTypeDouble, alias: Throat Height (ft) )
• GrateLength ( type: esriFieldTypeDouble, alias: Grate Length (ft) )
• GrateWidth ( type: esriFieldTypeDouble, alias: Grate Width (ft) )
• RimElevation ( type: esriFieldTypeSmallInteger, alias: Rim Elevation (ft) )
• GrateDiameter ( type: esriFieldTypeDouble, alias: Grate Diameter (ft) )
• UniqueID ( type: esriFieldTypeString, alias: Unique ID, length: 50 )
• created_user ( type: esriFieldTypeString, alias: created_user, length: 255 )
• created_date ( type: esriFieldTypeDate, alias: created_date, length: 8 )
• last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, length: 255 )
• last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, length: 8 )
• Reinstall_Date ( type: esriFieldTypeDate, alias: Reinstall Date, length: 8 )
• In_Out_Pit ( type: esriFieldTypeString, alias: In_Out_Pit, length: 50 , Coded Values: [Yes: Yes] , [No: No] )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )

Layer: BMPs (6)

Name: BMPs

Display Field: ProjectName

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: 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 Specialist is responsible for updating both layers for all new BMPs installed from site plans- MS4 Coordinator/Public Works Environmental Compliance Manager will update Property Type and Agreement date if maintenance agreement was signed for stormwater utilitySECTION 2Explanation of Attribute DataProject Name – enter name of development project BMP is associated withTax MapNumber – 3-part tax map identification number where the point is located, Sheet# Block# Parcel # Longitude – this is required for DEQ reporting Latitude – this is required for DEQ reportingDeedBookNumber – manual entry. This is the number where BMP agreements filed at the Court House. Pre 2008/2010 BMPs may not have this number. DateofAgreement – month/date/year that maintenance agreement was recordedAgreementType – Private BMP without Agreement: These BMPs willnothave anything filed here U:\Stormwater\Construction-Post Construction BMPs-E&S-VSMP\Project - Facilities - Private With Maint AgreePrivate BMP required with development, Agreement signed at time of development: These BMPs will be filed here U:\Stormwater\Construction-Post Construction BMPs-E&S-VSMP\Project - Facilities - Private With Maint AgreePrivate BMP required with development, Agreement signed for stormwater utility credit: These BMPs are part of the Public Works stormwater utility fee program and all approved agreements will be filed here U:\Stormwater\Construction-Post Construction BMPs-E&S-VSMP\Project Facilities - Private Existing for SWM Utility Fee (There will not be many of them)Private BMP not required with development/ voluntary, Agreement signed for stormwater utility credit: These BMPs are part of the Public Works stormwater utility fee program and all approved agreements will be filed by Tax Map ID here U:\Stormwater\Utility Fee - Management\Application InformationPublic BMP (City-Owned)Nutrient Credit PurchasedNotes:- Kathy/Chip/Nancy? should populate ii. from new plans- Kelley/Rebecca will populate iii. And iv. From sw utility fee program- Nancy/Kelley will populate v. and vi.- Patrick (2017 Summer Intern) should have i. handled through his work reviewing the Historical BMP Database (this should only be historical BMPs – all new BMPs have agreements)BMPType – type of BMP facility installedDisconnectionSheet FlowGrass ChannelsSoil AmendmentVegetated RoofRainwater HarvestingPermeable PavementInfiltrationBioretentionDry SwaleWet SwaleFiltering PracticesConstructed WetlandWet PondsExtended Detention PondDetention BasinRetention BasinSand FiltersManufactured BMP SystemsRegenerative Stormwater Conveyance SystemStream RestorationNutrient Credit PurchasedNotes: - If Manufactured BMP System, then add field for manual entry of system name. ManufacturedBMPSystem – type of BMP system installed, refer to supervisor on specifications for this fieldTotal AcresTreated – acres draining to BMP – look at DEQ BMP Historical data excel submittalImperviousAcresTreated – This field refers to the impervious acres that fall within the drainage area leading to each BMP.Notes:- This number impacts the water quantity requirements for these BMPs.- For historical BMPs, Patrick (2017 Summer Intern) should have pulled these numbers that were available. For new BMPs, the only way to populate this field is from the stormwater calculations. Dominant Watershed(VAHU6) PS22 – Blacks RunPS23 – Cooks CreekPS26 – North River-Mill CreekPS33 – Cub RubPS56 – Linville CreekPS59 – Dry ForkWatershed(HUC 8)02070005 – South Fork Shenandoah02070006 – North Fork Shenandoah InstallDate - this is the year that the BMP was physically installed.Notes:- Isn’t always the same as year the agreement was signed.- For old BMPs, this might be the date of plans.- For new BMPs, this is the date the as built has been approved.OwnedBy – designation of the entity that has ownership of the BMPPrivateCityMaintainedBy - designation of the entity that is responsible for maintaining the BMPPrivateCityLastInspectionDate - date of the last inspection on the BMP site Condition – conditional status the BMP is in, pulls from Inspection Report ConditionDate - date of condition Report filingEnabled – 1 or 0Attachment– static photo taken in the field during inspectionsPlanLink - file path to location where site plans for the corresponding BMP are foundInspectionLink – link to City Works report formStatus – refer to supervisor on specifications for this fieldLocation – closest address to incident location, full address - without ZIP codePlanDate – date of the site plan where the corresponding outfalls are foundUnique_ID - Unique identifying value assigned to a feature, generally same as OBJECTIDSECTION 3Handling of Data and RecommendationsTax Map ID#The "Tax Map Number" field should correspond to the location of the BMP- NOT the parcel that it services.If a BMP that handles runoff from one parcel, but is located in another parcel, then the "Tax Map Number" field should contain the parcel it is located in.BMP's in City Right-Of-WayThis pertains to any BMP's that fall outside of Tax Parcels, but are within the city ROW. ***Notation: Sheet# Block# ‘City ROW’(Example: 124 B City ROW)***Sheet and Block numbers should correspond to the closest and most appropriate parcels, relative to the location of the BMP.Overlapping BMP'sOnly 1 instance of a particular BMP should be mapped, unless otherwise directed. If multiple points are being used to describe 1 BMP, any new or existing points should be discussed, as to their necessity in consolidation of data.Site Plans - BMP LocationsThe locations of BMP's are delineated directly from their location as shown in their corresponding site plan.Digitizing point locations is easiest by using an up-to-date aerial imagery layer.Site Plans / Plan Links - ResearchSite plans are found in the P-drive ("Parcellookup"), in the "scans" folder. "Site Development Project Archives" is a subfolder that should also to be searched.**The content in "P:\scans\Site Development Project Archives" should be used and linked before content from "P:\scans"Plan Links - Which Site Plans to UseThe site plans used in the attributes table contains direct visual representation of the BMP to be mapped in GIS, w/out any detailing information.Using Plan LinksOnly 1 site plan should be linked in the Plan Link field at any time. If conflict with more than 1, the plan that best pertains to the BMP should be used.If folder is in "scans" folder, include file path with pdf doc. name, ending in ".pdf" If folder is in "Site Development Project Archives," link the folder's file path.Total Acres TreatedThis applies to any type of BMP that handles surface runoff. The value for this field may be found in the site plan.These values need to be recalculated in most instances.Impervious Acres TreatedThis applies to any type of BMP that handles surface runoff from impervious surfaces. The value for this field may be found in the site plan.Nutrient Credit PurchaseFor more information on how to handle Nutrient Credit Purchases in GIS, please contact Kelley Junco, MS4 Program Coordinator, at Public Works Dept.It is unclear as to whether these events should be mapped at this time.SECTION 4Additional ConsiderationsA. History & Logic of the Data- 10/18/2018 (KELLEY:) I think the BMP layer should have only ONE single point representing the BMP. Inspectors should not be using the GIS’ BMP point to inspect, only to [generally] locate and track BMPs. They should be using the as-built and/or plan set showing the BMP components. B. Department Notes- Wouldn’t the various structures (aside from ponds, of course) be reflected if the following layers were turned on? There is no need to repeat points in the swBMPs layer when structures are mapped in the following layers:swPIPESTRUCTURESswSTORMPIPESswDROPINLETC. Unresolved Questions- [Include any questions about or related to the data.]D. OtherCityworks Tracking Needs – we need to discuss these items furtherInspection DateSee Details within Inspection Forms – unique forms for each BMPMaintenance DatesWhat was performed …Cost…. Reports – how would these reports get generated?List of BMPs with owner information, HUC codes, etc. See DEQ Historic BMP spreadsheet for idea. List of City owned BMPs onlyWhere would department ownership information be visible? Questions / Considerations about:Nancy’s ID numbers vs Cityworks?Send Mark copy of Nancy’s Access DatabasesShare DEQ Historical Database with Sam – summer intern project to update GIS layers?Purchased Nutrient Credits to meet development stormwater quality requirementsSome hydrodynamic separators have been saved in stormstructures layer instead of BMPs. These need to move into BMPs. Parent – Child Features List (In CityWorks) for Detention/Retention/Bioretention PondsTrash Rack PresentYesNoTrash Rack MaterialMetalPlasticOrifice PresentYesNoSize: (Manual Entry)Sediment ForebayYesNoEmergency SpillwayYesNoForebay SpillwayYes NoSpillway MaterialGrass-linedRiprapConcrete

Copyright Text: City of Harrisonburg Public Works Department

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 15000.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 1.1362864306198657E7
YMin: 6825919.220689639
XMax: 1.1388543692175746E7
YMax: 6860542.996586308
Spatial Reference: 102746  (2283)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false


HasZ: false

HasM: false

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• ProjectName ( type: esriFieldTypeString, alias: Project Name, length: 255 )
• TaxMapNumber ( type: esriFieldTypeString, alias: Tax Map Number, length: 50 )
• Longitude ( type: esriFieldTypeDouble, alias: Longitude )
• Latitude ( type: esriFieldTypeDouble, alias: Latitude )
• DeedBookNumber ( type: esriFieldTypeString, alias: Deed Book Number, length: 50 )
• DateofAgreement ( type: esriFieldTypeString, alias: Date of Agreement, length: 50 )
• AgreementType ( type: esriFieldTypeString, alias: Agreement Type, length: 255 , Coded Values: [Private BMP without Agreement: Private BMP without Agreement] , [Private BMP required with development, Agreement signed at time of development: Private BMP required with development, Agreement signed at time of development] , [Private BMP required with development, Agreement signed for stormwater utility credit: Private BMP required with development, Agreement signed for stormwater utility credit] , ...3 more... )
• BMPType ( type: esriFieldTypeString, alias: BMP Type, length: 255 , Coded Values: [Disconnection: Disconnection] , [Sheet Flow: Sheet Flow] , [Grass Channel: Grass Channel] , ...24 more... )
• ManufacturedBMPSystem ( type: esriFieldTypeString, alias: Manufactured BMP System, length: 255 )
• TotalAcresTreated ( type: esriFieldTypeString, alias: Total Acres Treated, length: 255 )
• ImperviousAcresTreated ( type: esriFieldTypeDouble, alias: Impervious Acres Treated )
• DominantWatershedVAHU6 ( type: esriFieldTypeString, alias: Dominant Watershed VAHU6, length: 100 , Coded Values: [PS22 – Blacks Run: PS22 – Blacks Run] , [PS23 – Cooks Creek: PS23 – Cooks Creek] , [PS26 – North River-Mill Creek: PS26 – North River-Mill Creek] , ...3 more... )
• WatershedHUC8 ( type: esriFieldTypeString, alias: Watershed HUC8, length: 100 , Coded Values: [02070005 - South Fork Shenandoah: 02070005 - South Fork Shenandoah] , [02070006 - North Fork Shenandoah: 02070006 - North Fork Shenandoah] )
• InstallDate ( type: esriFieldTypeDate, alias: Install Date, length: 8 )
• OwnedBy ( type: esriFieldTypeString, alias: Owned By, length: 50 , Coded Values: [City: City] , [Other: Other] , [TMDL: TMDL] )
• MaintainedBy ( type: esriFieldTypeString, alias: Maintained By, length: 50 , Coded Values: [City: City] , [Other: Other] )
• LastInspectionDate ( type: esriFieldTypeDate, alias: Last Inspection Date, length: 8 )
• Condition ( type: esriFieldTypeSmallInteger, alias: Condition )
• ConditionDate ( type: esriFieldTypeDate, alias: Condition Date, length: 8 )
• Enabled ( type: esriFieldTypeSmallInteger, alias: Enabled )
• Attachment ( type: esriFieldTypeString, alias: Attachment, length: 50 )
• PlanLink ( type: esriFieldTypeString, alias: Plan Link, length: 255 )
• InspectionLink ( type: esriFieldTypeString, alias: Inspection Link, length: 255 )
• Status ( type: esriFieldTypeString, alias: Status, length: 255 , Coded Values: [Active: Active] , [Abandoned: Abandoned] , [Removed: Removed] , ...1 more... )
• Location ( type: esriFieldTypeString, alias: Location, length: 255 )
• PlanDate ( type: esriFieldTypeString, alias: Plan Date, length: 50 )
• UniqueID ( type: esriFieldTypeString, alias: Unique ID, length: 50 )
• created_user ( type: esriFieldTypeString, alias: created_user, length: 255 )
• created_date ( type: esriFieldTypeDate, alias: created_date, length: 8 )
• last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, length: 255 )
• last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, length: 8 )
• BMPIDNBR ( type: esriFieldTypeString, alias: BMP ID Number, length: 15 )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )
• Notes ( type: esriFieldTypeString, alias: Notes, length: 255 )

Layer: Ditches (7)

Name: Ditches

Display Field: DitchType

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: 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 Systems Analyst at the Public Works Department is responsible for updating and maintaining this layer. Addition or editing of features within this layer should be administered or approved by the Systems Analyst.SECTION 2Explanation of Attribute DataDitchType– type of ditch that the line represents.AsphaltConcreteEarthenOtherRiprapUnknownNotes:- Domain: “Ditch_Type”Length– (feet) the total length or the ditch feature.InstallDate- this is the year that the ditch was physically installed.OwnedBy- designation of the entity that has ownership of the ditch.CityOtherNotes:- Domain: “Ditch_Owned_By”MaintainedBy- designation of the entity that is responsible for maintaining the ditch.CityOtherNotes:- Domain: “Ditch_Maintained_By”LastInspectionDate- date of the last inspection on the ditch.Condition– conditional status that describes the ditch - this should be found in the Inspection Report.ConditionDate– date that the condition of the ditch was inspected.Enabled– 1 or 0Attachment– static photo of the ditch.Plan Link– file path to location where site plans for the corresponding ditch is found.InspectionsLink- link to the City Works report form.Status- status of the storm ditches.ActiveAbandonedRemovedProposedNotes:- Domain: “Storm_Structure_Status”Location – closest address to the ditches location, full address - without ZIP code.PlanDate – date of the site plan where the corresponding ditch is found.UniqueID - 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.Shape.STLength()– default field, length of the polyline.SECTION 3Handling of Data and RecommendationsTitle ofHandlingTopic #1[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #2[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #3[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandlingTopic #4[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] Title ofHandling Topic #5[Brief advice/description of how to address a specific component of/issue related to the data.][Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] 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- Cityworks will need to track:Last Inspection DateCondition - NumericLast Maintenance DateSchedule MaintenanceC. Unresolved Questions-Geometric Network (direction of flow) – See if we can do this- Definition of ditches?D. Other- N/A

Copyright Text: The Ditches data layer was created by Kathy Walker in the Department of Community Development of the City of Harrisonburg, on 6/7/2016. This information was created under the supervision of the Systems Analyst and in association with the GIS Specialist at the Department of Community.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 15000.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 1.136349935446924E7
YMin: 6825902.117705479
XMax: 1.1389417831175491E7
YMax: 6861410.774378315
Spatial Reference: 102746  (2283)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSLSSolid
Color: [230, 0, 169, 255]
Width: 1
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false


HasZ: false

HasM: false

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• DitchType ( type: esriFieldTypeString, alias: Ditch Type, length: 100 , Coded Values: [Asphalt: Asphalt] , [Concrete: Concrete] , [Earthen: Earthen] , ...3 more... )
• Length ( type: esriFieldTypeDouble, alias: Length (ft) )
• InstallDate ( type: esriFieldTypeDate, alias: Install Date, length: 8 )
• OwnedBy ( type: esriFieldTypeString, alias: Owned By, length: 100 , Coded Values: [City: City] , [Other: Other] )
• MaintainedBy ( type: esriFieldTypeString, alias: Maintained By, length: 100 , Coded Values: [City: City] , [Other: Other] )
• LastInspectionDate ( type: esriFieldTypeDate, alias: Last Inspection Date, length: 8 )
• Condition ( type: esriFieldTypeSmallInteger, alias: Condition )
• ConditionDate ( type: esriFieldTypeDate, alias: Condition Date, length: 8 )
• Enabled ( type: esriFieldTypeSmallInteger, alias: Enabled )
• Attachment ( type: esriFieldTypeString, alias: Attachment, length: 255 )
• PlanLink ( type: esriFieldTypeString, alias: Plan Link, length: 255 )
• InspectionLink ( type: esriFieldTypeString, alias: Inspection Link, length: 255 )
• Status ( type: esriFieldTypeString, alias: Status, length: 255 , Coded Values: [Active: Active] , [Abandoned: Abandoned] , [Removed: Removed] , ...1 more... )
• Location ( type: esriFieldTypeString, alias: Location, length: 50 )
• PlanDate ( type: esriFieldTypeDate, alias: Plan Date, length: 8 )
• UniqueID ( type: esriFieldTypeString, alias: Unique ID, length: 50 )
• created_user ( type: esriFieldTypeString, alias: created_user, length: 255 )
• created_date ( type: esriFieldTypeDate, alias: created_date, length: 8 )
• last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, length: 255 )
• last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, length: 8 )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )
• SHAPE.STLength() ( type: esriFieldTypeDouble, alias: SHAPE.STLength() )

Layer: Stormwater BMPs (8)

Name: Stormwater BMPs

Display Field: ProjectName

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: 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 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 DataProjectName – Name of project farm pond or BMP is associated withTaxMapNumber– 3-part tax map identification number where the feature is located, Sheet# Block# Parcel #Longitude– this is required for DEQ reportingLatitude - this is required for DEQ reportingDeedBookNumber– manual entry. This is the number where BMP agreements filed at the Court House. Pre 2008/2010 BMPs may not have this number.Date of Agreement – month/date/year that maintenance agreement was recordedAgreementType Private BMP without Agreement: These BMPs will not have anything filed here U:\Stormwater\Construction-Post Construction BMPs-E&S-VSMP\Project - Facilities - Private With Maint AgreePrivate BMP required with development, Agreement signed at time of development: These BMPs will be filed here U:\Stormwater\Construction-Post Construction BMPs-E&S-VSMP\Project - Facilities - Private With Maint AgreePrivate BMP required with development, Agreement signed for stormwater utility credit: These BMPs are part of the Public Works stormwater utility fee program and all approved agreements will be filed here U:\Stormwater\Construction-Post Construction BMPs-E&S-VSMP\Project Facilities - Private Existing for SWM Utility Fee (There will not be many of them)Private BMP not required with development/ voluntary, Agreement signed for stormwater utility credit: These BMPs are part of the Public Works stormwater utility fee program and all approved agreements will be filed by Tax Map ID here U:\Stormwater\Utility Fee - Management\Application InformationPublic BMP (City-Owned)Nutrient Credit PurchasedNotes:- Kathy/Chip/Nancy? should populate ii. from new plans- Kelley/Rebecca will populate iii. And iv. From sw utility fee program- Nancy/Kelley will populate v. and vi.- Patrick (2017 Summer Intern) should have i. handled through his work reviewing the Historical BMP Database (this should only be historical BMPs – all new BMPs have agreements)BMPType – type of BMP facility installedDisconnectionSheet FlowGrass ChannelSoil AmendmentVegetated RoofRainwater HarvestingPermeable PavementInfiltrationBioretentionDry SwaleWet SwaleFiltering PracticesConstructed WetlandsWet PondsExtended Detention PondsDetention BasinRetention BasinManufactured BMP SystemsRegenerative Stormwater Conveyance SystemNutrient Credit PurchasedSand FilterUnderground Detention BasinNotes:- If Manufactured BMP System, then add field for manual entry of system name. - Domain: “BMP_Type”ManufacturedBMPSystem- type of BMP system installed, refer to supervisor on specifications for this fieldTotalAcresTreated- acres draining to BMP – look at DEQ BMP Historical data excel submittalImperviousAcresTreated – This field refers to the impervious acres that fall within the drainage area leading to each BMP.Notes:- This number impacts the water quantity requirements for these BMPs.- For historical BMPs, Patrick (2017 Summer Intern) should have pulled these numbers that were available. For new BMPs, the only way to populate this field is from the stormwater calculations.HyrdrologicUnitCode6 – dominantwatershed farm pond or BMP is located inPS22 – Blacks RunPS23 – Cooks CreekPS26 – North River-Mill CreekPS33 – Cub RubPS56 – Linville CreekPS59 – Dry ForkNotes:- Domain: “BMP_Dominant_Watershed_VAHU6”HyrdrologicUnitCode12 – watershed farm pond or BMP is located inInstallDate- this is the year that the BMP was physically installed.Notes:- Isn’t always the same as year the agreement was signed.- For old BMPs, this might be the date of plans.- For new BMPs, this is the date the as built has been approved.OwnedBy- designation of the entity that has ownership of the BMP.CityOtherNotes:- Domain: “BMP_Owned_By”MaintainedBy- designation of the entity that is responsible for maintaining the BMP.CityOtherNotes:- Domain: “BMP_Maintained_By”Attachment– static photo of the BMP.Plan Link– file path to location where site plans for the corresponding BMP is found.InspectionLink- link to the City Works report form.Status – Status of the BMP.ActiveAbandonedRemovedProposedNotes:- Domain: “Storm_Structure_Status”Location - closest address to BMP's location, full address - without ZIP code.PlanDate – date of the site plan where the corresponding BMP is found.UniqueID - unique identifying value assigned to a feature, generally same as OBJECTID.Shape - geometric shape of these features are polygonsGlobalID- 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.Shape.STArea() - default field, area of the polygonShape.STLength() – default field, length of the polygonSECTION 3Handling of Data and RecommendationsTax Map ID#The "Tax Map Number" field should correspond to the location of the BMP- NOT the parcel that it services.If a BMP that handles runoff from one parcel, but is located in another parcel, then the "Tax Map Number" field should contain the parcel it is located in.BMP's in City Right-Of-WayThis pertains to any BMP's that fall outside of Tax Parcels, but are within the city ROW. ***Notation: Sheet# Block# ‘City ROW’ (Example: 124 B City ROW)***Sheet and Block numbers should correspond to the closest and most appropriate parcels, relative to the location of the BMP.Overlapping BMP'sOnly 1 instance of a particular BMP should be mapped, unless otherwise directed. If multiple points are being used to describe 1 BMP, any new or existing points should be discussed, as to their necessity in consolidation of data.Site Plans - BMP LocationsThe locations of BMP's are delineated directly from their location as shown in their corresponding site plan.Digitizing point locations is easiest by using an up-to-date aerial imagery layer.Site Plans / Plan Links - ResearchSite plans are found in the P-drive ("Parcellookup"), in the "scans" folder. "Site Development Project Archives" is a subfolder that should also to be searched.**The content in "P:\scans\Site Development Project Archives" should be used and linked before content from "P:\scans"Plan Links - Which Site Plans to UseThe site plans used in the attributes table contains direct visual representation of the BMP to be mapped in GIS, w/out any detailing information.Using Plan LinksOnly 1 site plan should be linked in the Plan Link field at any time. If conflict with more than 1, the plan that best pertains to the BMP should be used.If folder is in "scans" folder, include file path with pdf doc. name, ending in ".pdf" If folder is in "Site Development Project Archives," link the folder's file path.Total Acres TreatedThis applies to any type of BMP that handles surface runoff. The value for this field may be found in the site plan.These values need to be recalculated in most instances.Impervious Acres TreatedThis applies to any type of BMP that handles surface runoff from impervious surfaces. The value for this field may be found in the site plan.Nutrient Credit PurchaseFor more information on how to handle Nutrient Credit Purchases in GIS, please contact Kelley Junco, MS4 Program Coordinator, at Public Works Dept.It is unclear as to whether these events should be mapped at this time.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 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- Cityworks will need to track:Last Inspection DateConditionLast Maintenance DateSchedule MaintenanceC. Unresolved Questions- Link Unique_ID with that of Stormwater BMPs?D. Other- Not all BMPs will exist in this polygon layer. - Only BMPs greater than 4’x4’ will be in this layer. - Both above and underground BMPs will be here.- This layer is primarily for map making.

Copyright Text: The Drop Inlets data layer was created by Kathy Walker in the Department of Community Development of the City of Harrisonburg, on 6/21/2016. This information was created under the supervision of the Systems Analyst and in association with the City of Harrisonburg.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 15000.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 1.1362858944660828E7
YMin: 6825940.954898149
XMax: 1.139012131664516E7
YMax: 6860625.86092189
Spatial Reference: 102746  (2283)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [190, 210, 255, 255]
Outline:
Style: esriSLSSolid
Color: [64, 101, 235, 255]
Width: 0
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false


HasZ: true

HasM: false

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• ProjectName ( type: esriFieldTypeString, alias: Project_Name, length: 255 )
• TaxMapNumber ( type: esriFieldTypeString, alias: Tax_Map_Number, length: 50 )
• Longitude ( type: esriFieldTypeDouble, alias: Longitude )
• Latitude ( type: esriFieldTypeDouble, alias: Latitude )
• DeedBookNumber ( type: esriFieldTypeString, alias: Deed_Book_Number, length: 50 )
• DateofAgreement ( type: esriFieldTypeDate, alias: Date_of_Agreement, length: 8 )
• AgreementType ( type: esriFieldTypeString, alias: Agreement Type, length: 255 , Coded Values: [Private BMP without Agreement: Private BMP without Agreement] , [Private BMP required with development, Agreement signed at time of development: Private BMP required with development, Agreement signed at time of development] , [Private BMP required with development, Agreement signed for stormwater utility credit: Private BMP required with development, Agreement signed for stormwater utility credit] , ...3 more... )
• BMPType ( type: esriFieldTypeString, alias: BMP Type, length: 255 , Coded Values: [Disconnection: Disconnection] , [Sheet Flow: Sheet Flow] , [Grass Channel: Grass Channel] , ...24 more... )
• ManufacturedBMPSystem ( type: esriFieldTypeString, alias: Manufactured BMP System, length: 255 )
• TotalAcresTreated ( type: esriFieldTypeDouble, alias: Total Acres Treated )
• ImperviousAcresTreated ( type: esriFieldTypeDouble, alias: Impervious Acres Treated )
• HydrologicUnitCode6 ( type: esriFieldTypeString, alias: Hydrologic Unit Code 6, length: 100 , Coded Values: [PS22 – Blacks Run: PS22 – Blacks Run] , [PS23 – Cooks Creek: PS23 – Cooks Creek] , [PS26 – North River-Mill Creek: PS26 – North River-Mill Creek] , ...3 more... )
• HydrologicUnitCode12 ( type: esriFieldTypeString, alias: Hydrologic Unit Code 12, length: 100 )
• InstallDate ( type: esriFieldTypeDate, alias: Install Date, length: 8 )
• OwnedBy ( type: esriFieldTypeString, alias: Owned By, length: 50 , Coded Values: [City: City] , [Other: Other] , [TMDL: TMDL] )
• MaintainedBy ( type: esriFieldTypeString, alias: Maintained By, length: 50 , Coded Values: [City: City] , [Other: Other] )
• Attachment ( type: esriFieldTypeString, alias: Attachment, length: 50 )
• PlanLink ( type: esriFieldTypeString, alias: Plan Link, length: 255 )
• InspectionLink ( type: esriFieldTypeString, alias: Inspection Link, length: 255 )
• Status ( type: esriFieldTypeString, alias: Status, length: 255 , Coded Values: [Active: Active] , [Abandoned: Abandoned] , [Removed: Removed] , ...1 more... )
• Location ( type: esriFieldTypeString, alias: Location, length: 255 )
• PlanDate ( type: esriFieldTypeDate, alias: PlanDate, length: 8 )
• UniqueID ( type: esriFieldTypeString, alias: Unique ID, length: 50 )
• created_user ( type: esriFieldTypeString, alias: created_user, length: 255 )
• created_date ( type: esriFieldTypeDate, alias: created_date, length: 8 )
• last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, length: 255 )
• last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, length: 8 )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )
• SHAPE.STArea() ( type: esriFieldTypeDouble, alias: SHAPE.STArea() )
• SHAPE.STLength() ( type: esriFieldTypeDouble, alias: SHAPE.STLength() )

Layer: Flood Sensors (9)

Name: Flood Sensors

Display Field: SensorID

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description:

Copyright Text:

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 15000.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 1.1366314350807741E7
YMin: 6829811.633508474
XMax: 1.1384822896467745E7
YMax: 6852030.547403902
Spatial Reference: 102746  (2283)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Simple Renderer:
Symbol:
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false


HasZ: true

HasM: false

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• SensorID ( type: esriFieldTypeString, alias: SensorID, length: 255 )
• NearestLandmark ( type: esriFieldTypeString, alias: Nearest Landmark, length: 255 )
• LastServiceDate ( type: esriFieldTypeDate, alias: Last Service Date, length: 8 )
• RainGauge ( type: esriFieldTypeString, alias: Rain Gauge, length: 255 )
• SensorLocatedOn ( type: esriFieldTypeString, alias: Property Sensor is Located On, length: 255 )
• SpecialAccessNotes ( type: esriFieldTypeString, alias: Special Access Notes, length: 255 )
• UniqueID_INT ( type: esriFieldTypeInteger, alias: UniqueID Integer )
• UniqueID ( type: esriFieldTypeString, alias: UniqueID, length: 50 )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
• created_user ( type: esriFieldTypeString, alias: created_user, length: 255 )
• created_date ( type: esriFieldTypeDate, alias: created_date, length: 8 )
• last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, length: 255 )
• last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, length: 8 )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )

Layer: Stream Restoration Inspection Locations (10)

Name: Stream Restoration Inspection Locations

Display Field: RestProj

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description:

Copyright Text:

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 15000.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
XMin: 1.1370735968604907E7
YMin: 6833804.714761153
XMax: 1.1381279641415164E7
YMax: 6853797.014343396
Spatial Reference: 102746  (2283)  LatestVCSWkid(0)



Drawing Info:
Renderer:
Unique Value Renderer:
Field 1: Type
Field 2: N/A
Field 3: N/A
Field Delimiter: ,
Default Symbol:
N/A
Default Label: N/A
UniqueValueInfos:
• Value: XS
  Label: Cross Section
  Description: N/A
  Symbol:
  
• Value: PS
  Label: Photo Station
  Description: N/A
  Symbol:
  
Transparency: 0
Labeling Info:
Advanced Query Capabilities:
Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false


HasZ: true

HasM: false

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• RestProj ( type: esriFieldTypeString, alias: Restoration Project, length: 100 )
• Type ( type: esriFieldTypeString, alias: Location Type, length: 30 , Coded Values: [PS: Photo Station] , [XS: Cross Section] )
• RestYear ( type: esriFieldTypeDate, alias: Last Restoration Date, length: 8 )
• ActDate ( type: esriFieldTypeDate, alias: CorrectiveActDate, length: 8 )
• UniqueID ( type: esriFieldTypeString, alias: UniqueID, length: 50 )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
• created_user ( type: esriFieldTypeString, alias: created_user, length: 255 )
• created_date ( type: esriFieldTypeDate, alias: created_date, length: 8 )
• last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, length: 255 )
• last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, length: 8 )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )