Name: 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

Service Item Id: a98d922fc72947b3a54cb4b46166e585

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: 5000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.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
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Current User: true

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 )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )
• SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )

Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata