ArcGIS REST Services Directory Login | Get Token
Home > services > Test_DPW_Stormwater (MapServer) > Drop Inlets Help | API Reference
JSON

Layer: Drop Inlets (ID: 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:
Drawing Info: Advanced Query Capabilities:
HasZ: true

HasM: false

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

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

  Iteminfo   Thumbnail   Metadata