ArcGIS REST Services Directory Login
Home > services > PublicWorks > PedAssembly (MapServer) > Ped Assembly > iteminfo Help | API Reference
JSON

ItemInfo

Item Information

snippet: The traffic Pedestrian Assembly layer is a point layer that displays the locations of all the COH-PW maintained traffic pedestrian assemblies at intersections 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 Pedestrian Assembly layer is a point layer that displays the locations of all the COH-PW maintained traffic pedestrian assemblies at intersections 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 Pedestrian Assembly data layer was created by Alfredo Velasquez in the Public Works Department of the City of Harrisonburg, on 1/17/2018. 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)
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><SPAN>Additional Considerations</SPAN></SPAN></P><P /><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 11 0;"><SPAN><SPAN>- 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></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /></P><P STYLE="font-weight:bold;"><SPAN><SPAN>SECTION 2</SPAN></SPAN></P><P STYLE="font-weight:bold;"><SPAN><SPAN>Explanation of Attribute Data</SPAN></SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Type</SPAN></SPAN><SPAN><SPAN> – type of pedestrian assembly</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>APA</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>APS w/ BlueTooth</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Regular Push Button</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: “Ped_Model_Type”</SPAN></SPAN></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 STYLE="font-weight:bold;"><SPAN>LocationType</SPAN></SPAN><SPAN><SPAN> – location of pedestrian assembly</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>Pole</SPAN></SPAN></P></LI><LI><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>Stand Alone</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: “Ped_Location”</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Location – </SPAN></SPAN><SPAN><SPAN>closest address to the pedestrian assembly’s location, full address - without ZIP code</SPAN></SPAN><SPAN><SPAN>.</SPAN></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><SPAN>Condition</SPAN></SPAN><SPAN><SPAN> – conditional status that describes the pedestrian assembly.</SPAN></SPAN></P><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>Enable – </SPAN></SPAN><SPAN><SPAN>1 or 0.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>No. of Ped Heads </SPAN></SPAN><SPAN><SPAN>– number of heads on pedestrian assembly</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>Range: 0-3</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: “No_of_PedHeads”</SPAN></SPAN></P><P /><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN><SPAN>UniqueID - </SPAN></SPAN><SPAN><SPAN>unique identifying value assigned to a feature, generally same as OBJECTID.</SPAN></SPAN><SPAN><SPAN> </SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Decorative Pad?</SPAN></SPAN><SPAN><SPAN> – does the pedestrian assembly have a decorative pad.</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>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 /><P STYLE="margin:0 0 0 0;"><SPAN STYLE="font-weight:bold;"><SPAN>Reinstall_Date – </SPAN></SPAN><SPAN><SPAN>if the pedestrian assembly was removed and then reinstalled, the date of its re-installation.</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 STYLE="font-weight:bold;"><SPAN>Shape</SPAN></SPAN><SPAN><SPAN> – geometric shape of these features are points.</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><SPAN>Placement of Ped Assembly Points</SPAN></SPAN></P></TD><TD><P STYLE="font-style:italic;"><SPAN><SPAN>Just by looking at point you can see if the ped. head is attached to pole or not. If ped. assembly attached to pole, then place point on the side which it is attached to</SPAN></SPAN></P><P /></TD><TD><P STYLE="font-style:italic;"><SPAN><SPAN>In other words, place point on left or right side in order to distinguish</SPAN></SPAN></P></TD></TR><TR><TD><P STYLE="text-align:Center;font-weight:bold;"><SPAN><SPAN>Ped. Assemblies with two or more signal heads.</SPAN></SPAN></P></TD><TD><P><SPAN><SPAN>Do NOT drop two points for ped assemblies that have more than one head, drop only one point per assembly. </SPAN></SPAN></P></TD><TD><P STYLE="font-style:italic;"><SPAN><SPAN>There is a field called “No. of Ped. Heads”, this will track the no. of ped. heads attached to the assembly.</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><SPAN>- N/A</SPAN></SPAN></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 pedestrian assembly</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="margin:0 0 0 48;"><SPAN><SPAN>- N/A</SPAN></SPAN></P><P><SPAN /></P></DIV></DIV></DIV>
licenseInfo:
catalogPath:
title: Traffic Pedestrian Assembly
type:
url:
tags: ["City of Harrisonburg","Harrisonburg","Public Works Department","Traffic","TRAFFIC","Pedestrian Assembly","local government","Virginia","street","streets","public","public works","works","CityWorks","City Works","city works","Asset Management","traffic","traffic assets","pedestrian","Ped Assembly","crosswalk"]
culture: en-US
name:
guid:
minScale: 50000
spatialReference: