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

Layer: Streets (ID: 15)

Name: Streets

Display Field: RoadName

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.- The Street Division Superintendent at the Public Works Department is responsible for updating and maintaining paving schedule spreadsheet(s)/information.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 - OBJECTIDRoadName– name of the individual road segment identified in the paving schedule.Lanes - number of traffic lanes in segment.SpeedLimit– speed limit in mph of the segment.StreetClassification– VDOT classification of StreetPrincipal ArterialMinor ArterialMajor CollectorMinor CollectorLocalNon-VDOT StreetAlleyNotes:- Domain: “Street_Classification”StreetDesignation– Whether street is NHS or Non-NHSNHSNon-NHSNotes:- Domain: “Street_Designation”BikeLanes– Does the street have bike lanes along segment?YesNoNotes:- Domain: “Street_Bike_Lanes”CenterTurnLane– whether or not there is a center turn lane in the segment.YesNoNotes:- Domain: “Center_Turn_Lane”Length– (feet) the total length or the street featureInstallDate- this is the year that the street segment was last paved.VDOTConditionAssesment– VDOT CCI rating value.VCADate– date of the VDOT Condition Assesment.LastInspectionDate- date of the last inspection on the street.Condition– conditional status that describes the street - this should be found in the Inspection Report.ConditionDate– date that the condition that the street was inspected.Enabled– 1 or 0Attachment– static photo of the street.Plan Link– file path to location where site plans for the corresponding street is found.InspectionsLink- link to the City Works report form.Location – closest address to street ‘s location, full address - without ZIP code.PlanDate – date of the site plan where the corresponding street is found.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 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- N/AC. Unresolved Questions- N/AD. Other- N/A

Copyright Text: The Streets data layer was created by Nate Rexrode in the Public Works Department of the City of Harrisonburg, on 5/1/2017. This information was created under the supervision of the Systems Analyst and in association with the GIS Administrator for the City of Harrisonburg.

Default Visibility: true

MaxRecordCount: 5000

Supported Query Formats: JSON, geoJSON

Min Scale: 0.0

Max Scale: 0.0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: true

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   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata