ArcGIS REST Services Directory Login | Get Token
JSON

Layer: Ditches (ID: 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:
Drawing Info: Advanced Query Capabilities:
HasZ: false

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