ArcGIS REST Services Directory Login
Home > services > PublicWorks > SignsforFieldMaps (MapServer) > Sign Posts > iteminfo API Reference
JSON

ItemInfo

Item Information

snippet: The traffic Signs Posts layer is a point layer that displays the locations of all the COH-PW maintained traffic sign posts 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. This information used to be stored in a single layer combined with Signs information but in March of 2024, we separated the layers. One layer for Signs, One layer for sign posts
summary: The traffic Signs Posts layer is a point layer that displays the locations of all the COH-PW maintained traffic sign posts 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. This information used to be stored in a single layer combined with Signs information but in March of 2024, we separated the layers. One layer for Signs, One layer for sign posts
accessInformation:
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 /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Roadside_Location</SPAN></SPAN><SPAN><SPAN> – location of sign in relation to road.</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>Curb</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Grass</SPAN></SPAN></P></LI></UL><P STYLE="margin:0 0 0 0;"><SPAN>Parking Lot</SPAN></P><UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Sidewalk</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Street</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Traffic Signal</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Fence</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Median</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><SPAN>- Domain: “Roadside_Location_1”</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Support_Type</SPAN></SPAN><SPAN><SPAN> – type of sign support.</SPAN></SPAN></P><UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI><P STYLE="margin:0 0 0 0;"><SPAN>Anchor and Sleeve</SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN>Kleen Break</SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN>Traffic Signal</SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Delineator</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Diverter</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN>U Channel</SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN>Other</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><SPAN>- Domain: “Sign_Support_Type”</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Support_Material</SPAN></SPAN><SPAN><SPAN> – material used to support 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>Galvanized Steel</SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN>Black Epoxy Coated Steel</SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN>Other</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: “Support_Material_1”</SPAN></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 /></P><P STYLE="margin:0 0 0 0;"><SPAN /></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN>Location – Road the sign is on</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Date_Installed </SPAN></SPAN><SPAN>– date the asset was installed.</SPAN></P><P STYLE="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 /></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><SPAN> - default editor tracking field, unique serial number for the feature.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Signs_Count</SPAN></SPAN><SPAN><SPAN> – number of signs located on the pole/support</SPAN></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 /><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><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>Topic #2</SPAN></P></TD><TD><P><SPAN>[Brief advice/description of how to address a specific component of/issue related to the data.]</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 #3</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><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 #4</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><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 /></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></DIV></DIV></DIV>
licenseInfo:
catalogPath:
title: Traffic Sign Posts
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: 150000000
spatialReference: