ArcGIS REST Services Directory Login | Get Token
JSON

Layer: Mowing Areas (ID: 9)

Name: Mowing Areas

Display Field: UniqueID

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 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 DataUniqueID - 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 - OBJECTIDCityROW– shows if the mowing area is in the city Right of Way.YesNoNotes:- Domain: “Mowing_Areas_CityROW”CityProperty– shows if the mowing area is on a city owned propertyYesNoNotes:- Domain: “Mowing_Areas-CityProperty”Condition– conditional status that describes the mowing area - this should be found in the Inspection Report.ConditionDate– date that the condition of the mowing area was inspected.Enabled– 1 or 0Attachment– static photo of the mowing area.Plan Link– file path to location where site plans for the corresponding mowing area is found, not applicable for all.InspectionLink- link to the City Works report form.Location – closest address to mowing area’s location, full address - without ZIP code.Acres – acreage of mowing areaSize – size of mowing area in acrescreated_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 polygons.Shape.STArea() – default field, area of the polygon.Shape.STLength()– default field, length of the polygon.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.)------B. Department Notes- Cityworks will need to track:Money, Labor and Equipment attributed to each mowing area.How many times per year each mowing area was mowed.C. Unresolved QuestionsD. Other- N/A

Copyright Text: The mowing areas data layer was created by Nate Rexrode in the Public Works Department of the City of Harrisonburg, on 2/15/2017. 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: 24000.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