ArcGIS REST Services Directory Login
JSON

Layer: Shared Use Paths (ID: 2)

Name: Shared Use Paths

Display Field: TrailName

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. Additions or editing of features within this layer should be administered or approved by the Systems Analyst.SECTION 2Explanation of Attribute DataUniqueID - unique identifying value assigned to a feature, generally same as OBJECTID.ConstructionMaterial– material that the shared use path is constructed of.AsphaltStonePaver BrickConcreteNotes:- Domain: “Shared_Use_Paths_Construction_Material”Width– (feet) width of shared use paths.RejuvenatedDate– date of last maintenance. InstallDate– date the path was installed.OwnedBy- designation of the entity that has ownership of the shared use path.CityPrivateNotes:- Domain: “Shared_Use_Path_Owned_By”MaintainedBy- designation of the entity that is responsible for maintaining the shared use path.CityPrivateNotes:- Domain: “Shared_Use_Path_Maintained_By”Condition– conditional status that describes the shared use path - this should be found in the Inspection Report.ConditionDate– date that the condition of the path was inspected.Enabled– 1 or 0Attachment– static photo of the shared use path.PlanLink– file path to location where site plans for the corresponding path 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 polylines.Shape.STLength()– default field, length of the feature.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 #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 shared use path.C. Unresolved QuestionsD. Other- N/A

Service Item Id: 2ab0d8ab0ff24b3e9454b000aec640e3

Copyright Text: The Shared Use Path data layer was created by Alfredo Velasquez in the Public Works Department of the City of Harrisonburg, on 7/12/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: 0

Max Scale: 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