ArcGIS REST Services Directory Login | Get Token
Home > services > Test_DPW_Stormwater (FeatureServer) > Storm Pipes Help | API Reference
JSON

Layer: Storm Pipes (ID: 2)

View In:   ArcGIS Online Map Viewer

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

Can Scale Symbols: false

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: true

Supports Datum Transformation: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: true

HasM: false

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field:

Fields: Templates:
Capabilities: Query,Create,Update,Delete,Uploads,Editing

Sync Can Return Changes: true

Is Data Versioned: true

Supports Rollback On Failure: false

Supports ApplyEdits With Global Ids: false

Supports ApplyEdits By Upload Id: true

Edit Fields Info:
Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Supported Operations:   Query   Query Attachments   Query Analytic   Apply Edits   Add Features   Update Features   Delete Features   Calculate   Validate SQL   Generate Renderer   Return Updates   Iteminfo   Thumbnail   Metadata