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

Layer: Curbs (ID: 5)

Name: Curbs

Display Field: Length

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 1 Responsible 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 DataLength – (feet) the total length or the curb featureInstallDate - this is the year that the curb was physically installed.OwnedBy - designation of the entity that has ownership of the curb.CityOtherNotes:- Domain: “Curb_Owned_By”MaintainedBy - designation of the entity that is responsible for maintaining the curb.CityOtherNotes:- Domain: “Curb_Maintained_By”LastInspectionDate - date of the last inspection on the curb.Condition – conditional status that describes the curb - this should be found in the Inspection Report.ConditionDate – date that the condition of the curb was inspected.Enabled – 1 or 0Attachment – static photo of the curb.Plan Link – file path to location where site plans for the corresponding curb is found.InspectionsLink - link to the City Works report form.Location – closest address to curb’s location, full address - without ZIP code.PlanDate – date of the site plan where the corresponding curb is found.UniqueID - 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 - OBJECTIDcreated_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.CurbType – type of curb that the line represents.CurbCurb and GutterNotes:- Domain: “Curb_Type_1”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 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 how and why things 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.)------- Initial Planning: Image below shows how curb segments will be defined. 8/27/2018 – Curb segments are now to be grouped into block-lengths, or from street intersection to street intersection. This does not include driveway or commercial entrances, if a segment is divided by these features then both segments on either side of the feature are to be merged together. Segments should end on the corner of an adjoining street intersection. Additionally, segments on the other side of the road should be included in the feature, if there is a segment on the opposite side of the street, within the length of the block, then the features should be merged together.B. Department Notes- Cityworks will need to track:Last Inspection DateConditionLast Maintenance DateSchedule MaintenanceC. Unresolved Questions- Geometric Network & Drains to MS4?D. Other- N/A

Copyright Text: The Curbs data layer was created by Alfredo Gutierrez Velasquez in the Public Works Department of the City of Harrisonburg, on 6/1/2016. 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

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