ArcGIS REST Services Directory Login
Home > services > PublicWorks > SignsforFieldMaps (FeatureServer) > Signs > iteminfo API Reference
JSON

ItemInfo

Item Information

snippet: The traffic Signs Current layer is a point layer that displays the locations of all the COH-PW maintained traffic signs for asset management in the City of Harrisonburg. This layer will be used in conjunction with Cityworks. The data can be digitized using aerial imagery, or can be collected using a GPS-compatible device. Each point in the database should be an accurate representation of what is in the field. The information already contained within the dataset has been manually collected by the City of Harrisonburg, which has employed the means mentioned above to create and populate the data layer.
summary: The traffic Signs Current layer is a point layer that displays the locations of all the COH-PW maintained traffic signs for asset management in the City of Harrisonburg. This layer will be used in conjunction with Cityworks. The data can be digitized using aerial imagery, or can be collected using a GPS-compatible device. Each point in the database should be an accurate representation of what is in the field. The information already contained within the dataset has been manually collected by the City of Harrisonburg, which has employed the means mentioned above to create and populate the data layer.
accessInformation: The Signs Current data layer was created by Tyler Berry in the Public Works Department of the City of Harrisonburg, on 3/25/2024. This information was created under the supervision of the Asset Manager and GIS Coordinator and in association with the City of Harrisonburg.
thumbnail:
maxScale: 5000
typeKeywords: []
description: <DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>INDEX</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Section 1: </SPAN></SPAN><SPAN><SPAN>Responsible Parties</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Section 2: </SPAN></SPAN><SPAN><SPAN>Explanation of Attribute Data</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Section 3: </SPAN></SPAN><SPAN><SPAN>Handling of Data and Recommendations</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Section 4: </SPAN></SPAN><SPAN>Additional Considerations</SPAN></P><P><SPAN STYLE="font-weight:bold;"><SPAN>SECTION 1</SPAN></SPAN><SPAN><SPAN> </SPAN></SPAN></P><P STYLE="font-weight:bold;"><SPAN><SPAN>Responsible Parties</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-style:italic;"><SPAN>Parties responsible for updating this layer:</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN>- The Asset Manager 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 Asset Manager.</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN>- The Traffic Superintendent or the Signs Supervisor should be consulted regarding information on specific items.</SPAN></P><P STYLE="font-weight:bold;"><SPAN><SPAN>SECTION 2</SPAN></SPAN></P><P STYLE="font-weight:bold;"><SPAN>Explanation of Attribute Data</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;">UniqueParentID</SPAN><SPAN> – UniqueID of the sign post the sign is on</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>MUTCD_Category </SPAN></SPAN><SPAN><SPAN>– classification of sign based on MUTCD types.</SPAN></SPAN></P><UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>R - Regulatory (Red/White)</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN>W - Warning (Orange/Yellow)</SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>D - Guide Sign (Street/Dest)</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN>I - Info. Sign (RoadUserServive): Mostly used for City of Harrisonburg specific wayfinding signs/bus stop signs</SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>S - School Sign (RFYellow)</SPAN></SPAN></P></LI></UL><P STYLE="font-weight:bold;margin:0 0 0 24;"><SPAN><SPAN>Notes:</SPAN></SPAN></P><P STYLE="text-indent:24;margin:0 0 0 0;"><SPAN>- Domain: Sign_MUTCD_Type</SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>created_user</SPAN></SPAN><SPAN><SPAN> – default editor tracking field, who created the feature.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>created_date</SPAN></SPAN><SPAN><SPAN> – default editor tracking field, when the feature was created.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>last_edited_user</SPAN></SPAN><SPAN><SPAN> – default editor tracking field, who last edited the feature.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>last_edited_date</SPAN></SPAN><SPAN><SPAN> - default editor tracking field, when the feature was last edited.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /><SPAN /></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Sign_Type – </SPAN></SPAN><SPAN><SPAN>rough category that describes the type of sign.</SPAN></SPAN></P><UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 0 0;"><SPAN>StreetName</SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>No Parking</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Permit Parking</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>One Way</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Yield</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>WayFinding</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Dead End</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Bus Stop</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Bike/Pedestrian</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Flashing Lights Sign</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Multiple</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Other</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Railroad</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>School Signs</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Shared Use</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>SpeedLimit</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Stop Sign</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Streets Intersection</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Tow Away Zone</SPAN></SPAN></P></LI></UL><P STYLE="font-weight:bold;margin:0 0 0 24;"><SPAN><SPAN>Notes:</SPAN></SPAN></P><P STYLE="text-indent:24;margin:0 0 0 0;"><SPAN>- Domain: “Sign_Type”</SPAN></P><P STYLE="text-indent:24;margin:0 0 0 0;"><SPAN /></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Sign_Text – </SPAN></SPAN><SPAN>text on sign</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Date_Installed </SPAN></SPAN><SPAN><SPAN>– date the asset was installed.</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN /></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>UniqueID - </SPAN></SPAN><SPAN>unique identifying value assigned to a feature, MMYY-Object ID (Month and Year of Install), If unknown, use 00YY-Object ID of when it was added to GIS </SPAN></P><P STYLE="font-weight:bold;text-indent:20;margin:0 0 0 20;"><SPAN>&gt; We had to start using this method because during a GIS database upgrade, all of our ObjectIDs were reset, therefore creating duplicates if we were to keep numbering off of Object ID</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Lighted Street Sign?</SPAN></SPAN><SPAN> – is the street sign lit. Only used for the Lighted Street Signs at intersections</SPAN></P><UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Yes</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>No</SPAN></SPAN></P></LI></UL><P STYLE="font-weight:bold;margin:0 0 0 24;"><SPAN><SPAN>Notes:</SPAN></SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN><SPAN>- Domain: “YesNo_1”</SPAN></SPAN></P><P><SPAN STYLE="font-weight:bold;"><SPAN>Sign Reflectivity Number</SPAN></SPAN><SPAN><SPAN> – Number the retroreflectometer reads on the sign</SPAN></SPAN></P><P><SPAN STYLE="font-weight:bold;">Sign Reflectivity Rating</SPAN><SPAN> – Rating we came up with based on the number the gun gives us. Schema is in Asset Management folder on N drive</SPAN></P><P><SPAN STYLE="font-weight:bold;">Eye Test</SPAN><SPAN> – Does the sign look good to the naked eye? Not cracked up, not peeling, looks not faded out</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Shape</SPAN></SPAN><SPAN><SPAN> – geometric shape of these features are points.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>GlobalID</SPAN></SPAN><SPAN> - default editor tracking field, unique serial number for the feature.</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Status</SPAN></SPAN><SPAN><SPAN> – specify the existence status of the sign.</SPAN></SPAN></P><UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Active</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Inactive</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Removed</SPAN></SPAN></P></LI></UL><P STYLE="font-weight:bold;margin:0 0 0 24;"><SPAN><SPAN>Notes:</SPAN></SPAN></P><P STYLE="margin:0 0 0 24;"><SPAN><SPAN>- Domain: “Traffic Status Code”</SPAN></SPAN></P><P /><P STYLE="font-weight:bold;"><SPAN><SPAN>SECTION 3</SPAN></SPAN></P><P><SPAN><SPAN>Handling of Data and Recommendations</SPAN></SPAN></P><P /><TABLE><TBODY><TR><TD><P STYLE="text-align:Center;font-weight:bold;"><SPAN>Multiple signs per pole - Each sign gets a point</SPAN></P></TD><TD><P><SPAN>One point per sign</SPAN></P></TD><TD><P STYLE="font-style:italic;"><SPAN /></P></TD></TR><TR><TD><P STYLE="text-align:Center;font-weight:bold;"><SPAN /></P><P STYLE="text-align:Center;font-weight:bold;"><SPAN>Reflectivity Failures</SPAN></P></TD><TD><P><SPAN>At start of each month, Asset Manager creates WO based on which signs failed the reflectivity test</SPAN></P></TD><TD><P STYLE="font-style:italic;"><SPAN><SPAN>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="text-align:Center;font-weight:bold;"><SPAN /></P><P STYLE="text-align:Center;font-weight:bold;"><SPAN>Flashing Lights Signs</SPAN></P></TD><TD><P><SPAN><SPAN>A flashing lights assembly may have 4 signs on it, Map only one of these main signs as "Flashing Lights Sign"</SPAN></SPAN></P></TD><TD><P STYLE="font-style:italic;"><SPAN>Doing this will allow an export of all flashing signs to account for 1 Flashing sign assembly instead of 4</SPAN></P></TD></TR><TR><TD><P STYLE="text-align:Center;font-weight:bold;"><SPAN /></P><P STYLE="text-align:Center;font-weight:bold;"><SPAN>Lighted Street Signs</SPAN></P></TD><TD><P><SPAN>Strictly pertains to lighted street signs at signalized intersections. NOT Flashing Lights Signs</SPAN></P></TD><TD><P STYLE="font-style:italic;"><SPAN><SPAN>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Title of</SPAN></SPAN></P><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Handling </SPAN></SPAN></P><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Topic #5</SPAN></SPAN></P></TD><TD><P><SPAN><SPAN>[Brief advice/description of how to address a specific component of/issue related to the data.]</SPAN></SPAN></P></TD><TD><P STYLE="font-style:italic;"><SPAN><SPAN>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </SPAN></SPAN></P></TD></TR></TBODY></TABLE><P /><P /><P STYLE="font-weight:bold;"><SPAN><SPAN>SECTION 4</SPAN></SPAN></P><P><SPAN><SPAN>Additional Considerations</SPAN></SPAN></P><P /><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>A. History &amp; Logic of the Data</SPAN></SPAN></P><P STYLE="font-style:italic;margin:0 0 0 48;"><SPAN><SPAN>[For future reference, please list facets of the history of the decision-making process related to the data’s use – the </SPAN></SPAN><SPAN STYLE="font-weight:bold;"><SPAN>how</SPAN></SPAN><SPAN><SPAN> and </SPAN></SPAN><SPAN STYLE="font-weight:bold;"><SPAN>why</SPAN></SPAN><SPAN><SPAN> 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.)</SPAN></SPAN></P><P STYLE="margin:0 0 0 48;"><SPAN><SPAN>------</SPAN></SPAN></P><P STYLE="margin:0 0 0 48;"><SPAN>7/11/2018—MUTCD fields were discussed about removing, but MUTCD fields will be kept and will not be populated.</SPAN></P><P STYLE="margin:0 0 0 48;"><SPAN><SPAN>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.</SPAN></SPAN></P><P STYLE="margin:0 0 0 48;"><SPAN /><SPAN /></P><P STYLE="margin:0 0 0 48;"><SPAN>March 2024 - Signs layer was split into Sign Posts and Signs Current, Sign Post will now only represent the sign post, Signs Current will represent all of the current signs. The signs layer is archived, DO NOT edit the signs layer, it is for historical Cityworks purposes only. We bought a RetroReflectometer and added the appropriate field s to track the reflectiveness of signs.</SPAN></P><P /><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>B. Department Notes</SPAN></SPAN></P><P STYLE="margin:0 0 0 48;"><SPAN><SPAN>- Cityworks will need to track:</SPAN></SPAN></P><UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Money, Labor, and Equipment attributed to each Sign.</SPAN></SPAN></P></LI></UL><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>C. Unresolved Questions</SPAN></SPAN></P><P STYLE="margin:0 0 0 48;"><SPAN><SPAN>- N/A</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>D. Other</SPAN></SPAN></P><P STYLE="text-indent:48;margin:0 0 0 0;"><SPAN><SPAN>-N/A</SPAN></SPAN></P><P /><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN /></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN /></P></DIV></DIV></DIV>
licenseInfo:
catalogPath:
title: Traffic Signs Current
type:
url:
tags: ["City of Harrisonburg","Harrisonburg","Public Works Department","Traffic","TRAFFIC","Signs","local government","Virginia","street","streets","public","public works","works","CityWorks","City Works","city works","Asset Management","traffic","traffic assets","signs","sign","traffic signs","street signs"]
culture: en-US
portalUrl:
name:
guid:
minScale: 50000
spatialReference: