ArcGIS REST Services Directory Login | Get Token
Home > services > Archive_PW (MapServer) > Signs Archived Help | API Reference
JSON

Layer: Signs Archived (ID: 0)

Name: Signs Archived

Display Field: MUTCD_Category

Type: Feature Layer

Geometry Type: esriGeometryPoint

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 DataMUTCD_Name – *Will be left blankMUTCD_Category – classification of sign based on MUTCD types.R - Regulatory (Red/White)W - Warning (Orange/Yellow)G - Warning Sign (RoadWork)E - Warning Sign (ExitSign)M - Warning\Guide (Detours)D - Guide Sign (Street/Dest)I - Info. Sign (RoadUserServive)EM - Emrg.Mng&CivilDef (Disaster)S - School Sign (RFYellow)Notes:- Domain: Sign_MUTCD_TypeRoadside_Location – location of sign in relation to road.CurbGrassGrass StripSidewalkStreetSignal SupportFenceTraffic PoleMedianNotes:- Domain: “Roadside_Location_1”Support_Type – type of sign support.10 Anchor and Sleeve (2x2)12 Anchor and Sleeve (2x2)14 Anchor and Sleeve (2x2)6 ft U-Channel10 ft U-Channel12 ft Clean Break PostBrickFenceSignal SupportTraffic PoleWood10 ft Clean Break14 ft Clean BreakDelineatorDiverterLight PoleNotes:- Domain: “Sign_Support_Type”Support_Material – material used to support sign.14 Gauge Galvanized Steel14 Gauge Black Epoxy Coated SteelN/ANotes:- Domain: “Support_Material_1”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.Sign_Type – rough category that describes the type of sign.StreetNameNo ParkingPermit ParkingOne WayYieldWayFindingDead EndBus StopBike/PedestrianFlashing Lights SignMultipleOtherRailroadSchool SignsShared UseSpeedLimitStop SignStreets IntersectionTow Away ZoneNotes:- Domain: “Sign_Type”Sign_Text – text on the 1st sign.Location – closest address to the sign’s location, full address - without ZIP code.Date_Installed – date the asset was installed.Condition – conditional status that describes the signEnable – 1 or 0.Support_Count – number of supports for sign.Range: 0-20Notes:- Domain: “No_of_Cameras”UniqueID - unique identifying value assigned to a feature, generally same as OBJECTID. 2nd Sign Text – text of second sign.3rd Sign Text – text of third sign.4th Sign Text – text of fourth sign.5th Sign Text – text of fifth sign.Lighted Street Sign? – is the street sign lit.YesNoNotes:- Domain: “YesNo_1”Reinstall_Date – if the sign was removed and then reinstalled, the date of its re-installation.Shape – geometric shape of these features are points.GlobalID - default editor tracking field, unique serial number for the feature.6th Sign Text – text of sixth sign.7th Sign Text – text of seventh sign.8th Sign Text – text of eighth sign.Signs_Count – number of signs located on the pole/supportStatus – specify the existence status of the sign.ActiveInactiveRemovedNotes:- Domain: “Traffic Status Code”SECTION 3Handling of Data and RecommendationsMultiple signs per pole.The top most sign will be filed under “Sign_Text”. The second sign from the top will be filed under “2nd Sign Text” and the 3rd sign from the top will be filed under the “3rd Sign Text” and so on.Do NOT put two points if signs are on same support pole. Place one point and use method described to the left. 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.)------7/11/2018—MUTCD fields were discussed about removing, but MUTCD fields will be kept and will not be populated.9/13/2018—MUTCD_Category field will be population with values, for more specific searching criteria. “Type” field was renamed to “Sign_Type” and its values were applied with domains for consistent type categories. The status field was added for CityWorks asset cost tracking, if a sign has been removed then its UniqueID and associated work order(s) tied to the asset are not lost like when it is deleted. “Support_Type” was updated to include delimiters, diverters, and light poles. “Support_Material” has been restricted in its selection since “Support_Type” describes the supporting material for most of the signs. Diverters’ material type is always plastic.B. Department Notes- Cityworks will need to track:Money, Labor, and Equipment attributed to each Sign.C. Unresolved Questions- N/AD. Other-N/A

Copyright Text: The Signs data layer was created by Alfredo Velasquez in the Public Works Department of the City of Harrisonburg, on 11/2/2017. This information was created under the supervision of the Systems Analyst and in association with the City of Harrisonburg. Asset Editor: Asset Manager (PW) & Systems Analyst (PW)

Default Visibility: true

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON

Min Scale: 8000.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   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata