ArcGIS REST Services Directory Login | Get Token
Home > services > Test_DPW_Streets (FeatureServer) > Fences Help | API Reference
JSON

Layer: Fences (ID: 11)

View In:   ArcGIS Online Map Viewer

Name: Fences

Display Field: UniqueID

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 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 - OBJECTIDMaterial– material that fence is constructed ofChain LinkWoven WireSplit RailNotes:- Domain: “Fence_Material”Length–(feet) length of fence.Height– (feet) height of fence.BarbWire– does the fence have barbed wire on itYesNoNotes:- Domain: “Fence_Barb_Wire”InstallDate– date the fence was installed.OwnedBy- designation of the entity that has ownership of the fence.CityPrivateNotes:- Domain: “Fence_Owned_By”MaintainedBy- designation of the entity that is responsible for maintaining the fence.CityPrivateNotes:- Domain: “Fence_Maintained_By”Condition– conditional status that describes the fence - this should be found in the Inspection Report.ConditionDate– date that the condition of the fence was inspected.Enabled– 1 or 0Attachment– static photo of the fence.PlanLink– file path to location where site plans for the corresponding fence is found, not applicable for all.InspectionLink- link to the City Works report form.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.GlobalID- default editor tracking field, unique serial number for the feature.Shape– geometric shape of these features are points.Shape.STLength()– default field, length of the featureSECTION 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 #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 #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 #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 #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]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 fence.C. Unresolved QuestionsD. Other- N/A

Copyright Text: The Fence data layer was created by Alfredo Velasquez in the Public Works Department of the City of Harrisonburg, on 7/25/2017. This information was created under the supervision of the Systems Analyst and in association with the City of Harrisonburg.

Default Visibility: false

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0.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: false

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