{ "culture": "en-US", "name": "", "guid": "", "catalogPath": "", "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.\n\nThe 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.", "description": "

INDEX<\/SPAN><\/SPAN><\/P>

Section 1: <\/SPAN><\/SPAN>Responsible Parties<\/SPAN><\/SPAN><\/P>

Section 2: <\/SPAN><\/SPAN>Explanation of Attribute Data<\/SPAN><\/SPAN><\/P>

Section 3: <\/SPAN><\/SPAN>Handling of Data and Recommendations<\/SPAN><\/SPAN><\/P>

Section 4: <\/SPAN><\/SPAN>Additional Considerations<\/SPAN><\/P>

SECTION 1<\/SPAN><\/SPAN> <\/SPAN><\/SPAN><\/P>

Responsible Parties<\/SPAN><\/SPAN><\/P>

Parties responsible for updating this layer:<\/SPAN><\/SPAN><\/P>

- 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>

- The Traffic Superintendent or the Signs Supervisor should be consulted regarding information on specific items.<\/SPAN><\/P>

SECTION 2<\/SPAN><\/SPAN><\/P>

Explanation of Attribute Data<\/SPAN><\/P>

MUTCD_Name \u2013 <\/SPAN>*Will be left blank<\/SPAN><\/SPAN><\/P>

MUTCD_Category <\/SPAN><\/SPAN>\u2013 classification of sign based on MUTCD types.<\/SPAN><\/SPAN><\/P>

  • R - Regulatory (Red/White)<\/SPAN><\/SPAN><\/P><\/LI>

  • W - Warning (Orange/Yellow)<\/SPAN><\/SPAN><\/P><\/LI>

  • G - Warning Sign (RoadWork)<\/SPAN><\/SPAN><\/P><\/LI>

  • E - Warning Sign (ExitSign)<\/SPAN><\/SPAN><\/P><\/LI>

  • M - Warning\\Guide (Detours)<\/SPAN><\/SPAN><\/P><\/LI>

  • D - Guide Sign (Street/Dest)<\/SPAN><\/SPAN><\/P><\/LI>

  • I - Info. Sign (RoadUserServive)<\/SPAN><\/SPAN><\/P><\/LI>

  • EM - Emrg.Mng&CivilDef (Disaster)<\/SPAN><\/SPAN><\/P><\/LI>

  • S - School Sign (RFYellow)<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

    Notes:<\/SPAN><\/SPAN><\/P>

    - Domain: Sign_MUTCD_Type<\/SPAN><\/SPAN><\/P>

    Roadside_Location<\/SPAN><\/SPAN> \u2013 location of sign in relation to road.<\/SPAN><\/SPAN><\/P>

    • Curb<\/SPAN><\/SPAN><\/P><\/LI>

    • Grass<\/SPAN><\/SPAN><\/P><\/LI>

    • Grass Strip<\/SPAN><\/SPAN><\/P><\/LI>

    • Sidewalk<\/SPAN><\/SPAN><\/P><\/LI>

    • Street<\/SPAN><\/SPAN><\/P><\/LI>

    • Signal Support<\/SPAN><\/SPAN><\/P><\/LI>

    • Fence<\/SPAN><\/SPAN><\/P><\/LI>

    • Traffic Pole<\/SPAN><\/SPAN><\/P><\/LI>

    • Median<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

      Notes:<\/SPAN><\/SPAN><\/P>

      - Domain: \u201cRoadside_Location_1\u201d<\/SPAN><\/SPAN><\/P>

      Support_Type<\/SPAN><\/SPAN> \u2013 type of sign support.<\/SPAN><\/SPAN><\/P>

      • 10 Anchor and Sleeve (2x2)<\/SPAN><\/SPAN><\/P><\/LI>

      • 12 Anchor and Sleeve (2x2)<\/SPAN><\/SPAN><\/P><\/LI>

      • 14 Anchor and Sleeve (2x2)<\/SPAN><\/SPAN><\/P><\/LI>

      • 6 ft U-Channel<\/SPAN><\/SPAN><\/P><\/LI>

      • 10 ft U-Channel<\/SPAN><\/SPAN><\/P><\/LI>

      • 12 ft Clean Break Post<\/SPAN><\/SPAN><\/P><\/LI>

      • Brick<\/SPAN><\/SPAN><\/P><\/LI>

      • Fence<\/SPAN><\/SPAN><\/P><\/LI>

      • Signal Support<\/SPAN><\/SPAN><\/P><\/LI>

      • Traffic Pole<\/SPAN><\/SPAN><\/P><\/LI>

      • Wood<\/SPAN><\/SPAN><\/P><\/LI>

      • 10 ft Clean Break<\/SPAN><\/SPAN><\/P><\/LI>

      • 14 ft Clean Break<\/SPAN><\/SPAN><\/P><\/LI>

      • Delineator<\/SPAN><\/SPAN><\/P><\/LI>

      • Diverter<\/SPAN><\/SPAN><\/P><\/LI>

      • Light Pole<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

        Notes:<\/SPAN><\/SPAN><\/P>

        - Domain: \u201cSign_Support_Type\u201d<\/SPAN><\/SPAN><\/P>

        Support_Material<\/SPAN><\/SPAN> \u2013 material used to support sign.<\/SPAN><\/SPAN><\/P>

        • 14 Gauge Galvanized Steel<\/SPAN><\/SPAN><\/P><\/LI>

        • 14 Gauge Black Epoxy Coated Steel<\/SPAN><\/SPAN><\/P><\/LI>

        • N/A<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

          Notes:<\/SPAN><\/SPAN><\/P>

          - Domain: \u201cSupport_Material_1\u201d<\/SPAN><\/SPAN><\/P>

          created_user<\/SPAN><\/SPAN> \u2013 default editor tracking field, who created the feature.<\/SPAN><\/SPAN><\/P>

          created_date<\/SPAN><\/SPAN> \u2013 default editor tracking field, when the feature was created.<\/SPAN><\/SPAN><\/P>

          last_edited_user<\/SPAN><\/SPAN> \u2013 default editor tracking field, who last edited the feature.<\/SPAN><\/SPAN><\/P>

          last_edited_date<\/SPAN><\/SPAN> - default editor tracking field, when the feature was last edited.<\/SPAN><\/SPAN><\/P>

          Sign_Type \u2013 <\/SPAN><\/SPAN>rough category that describes the type of sign.<\/SPAN><\/SPAN><\/P>

          • StreetName<\/SPAN><\/SPAN><\/P><\/LI>

          • No Parking<\/SPAN><\/SPAN><\/P><\/LI>

          • Permit Parking<\/SPAN><\/SPAN><\/P><\/LI>

          • One Way<\/SPAN><\/SPAN><\/P><\/LI>

          • Yield<\/SPAN><\/SPAN><\/P><\/LI>

          • WayFinding<\/SPAN><\/SPAN><\/P><\/LI>

          • Dead End<\/SPAN><\/SPAN><\/P><\/LI>

          • Bus Stop<\/SPAN><\/SPAN><\/P><\/LI>

          • Bike/Pedestrian<\/SPAN><\/SPAN><\/P><\/LI>

          • Flashing Lights Sign<\/SPAN><\/SPAN><\/P><\/LI>

          • Multiple<\/SPAN><\/SPAN><\/P><\/LI>

          • Other<\/SPAN><\/SPAN><\/P><\/LI>

          • Railroad<\/SPAN><\/SPAN><\/P><\/LI>

          • School Signs<\/SPAN><\/SPAN><\/P><\/LI>

          • Shared Use<\/SPAN><\/SPAN><\/P><\/LI>

          • SpeedLimit<\/SPAN><\/SPAN><\/P><\/LI>

          • Stop Sign<\/SPAN><\/SPAN><\/P><\/LI>

          • Streets Intersection<\/SPAN><\/SPAN><\/P><\/LI>

          • Tow Away Zone<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

            Notes:<\/SPAN><\/SPAN><\/P>

            - Domain: \u201cSign_Type\u201d<\/SPAN><\/SPAN><\/P>

            Sign_Text \u2013 <\/SPAN><\/SPAN>text on the 1st sign.<\/SPAN><\/SPAN><\/P>

            Location \u2013 <\/SPAN><\/SPAN>closest address to the sign\u2019s location, full address - without ZIP code<\/SPAN><\/SPAN>.<\/SPAN><\/SPAN><\/P>

            Date_Installed <\/SPAN><\/SPAN>\u2013 date the asset was installed.<\/SPAN><\/SPAN><\/P>

            Condition<\/SPAN><\/SPAN> \u2013 conditional status that describes the sign<\/SPAN><\/SPAN><\/P>

            Enable \u2013 <\/SPAN><\/SPAN>1 or 0.<\/SPAN><\/SPAN><\/P>

            Support_Count<\/SPAN><\/SPAN> \u2013 number of supports for sign.<\/SPAN><\/SPAN><\/P>

            • Range: 0-20<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

              Notes:<\/SPAN><\/SPAN><\/P>

              - Domain: \u201cNo_of_Cameras\u201d<\/SPAN><\/SPAN><\/P>

              UniqueID - <\/SPAN><\/SPAN>unique identifying value assigned to a feature, generally same as OBJECTID.<\/SPAN><\/SPAN> <\/SPAN><\/SPAN><\/P>

              2<\/SPAN><\/SPAN>nd<\/SPAN><\/SPAN> Sign Text \u2013 <\/SPAN><\/SPAN>text of second sign.<\/SPAN><\/SPAN><\/P>

              3<\/SPAN><\/SPAN>rd<\/SPAN><\/SPAN> Sign Text \u2013 <\/SPAN><\/SPAN>text of third sign.<\/SPAN><\/SPAN><\/P>

              4<\/SPAN><\/SPAN>th<\/SPAN><\/SPAN> Sign Text \u2013 <\/SPAN><\/SPAN>text of fourth sign.<\/SPAN><\/SPAN><\/P>

              5<\/SPAN><\/SPAN>th<\/SPAN><\/SPAN> Sign Text \u2013 <\/SPAN><\/SPAN>text of fifth sign.<\/SPAN><\/SPAN><\/P>

              Lighted Street Sign?<\/SPAN><\/SPAN> \u2013 is the street sign lit.<\/SPAN><\/SPAN><\/P>

              • Yes<\/SPAN><\/SPAN><\/P><\/LI>

              • No<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

                Notes:<\/SPAN><\/SPAN><\/P>

                - Domain: \u201cYesNo_1\u201d<\/SPAN><\/SPAN><\/P>

                Reinstall_Date \u2013 <\/SPAN><\/SPAN>if the sign was removed and then reinstalled, the date of its re-installation.<\/SPAN><\/SPAN><\/P>

                Shape<\/SPAN><\/SPAN> \u2013 geometric shape of these features are points.<\/SPAN><\/SPAN><\/P>

                GlobalID<\/SPAN><\/SPAN> - default editor tracking field, unique serial number for the feature.<\/SPAN><\/SPAN><\/P>

                6<\/SPAN><\/SPAN>th<\/SPAN><\/SPAN> Sign Text \u2013 <\/SPAN><\/SPAN>text of sixth sign.<\/SPAN><\/SPAN><\/P>

                7<\/SPAN><\/SPAN>th<\/SPAN><\/SPAN> Sign Text \u2013 <\/SPAN><\/SPAN>text of seventh sign.<\/SPAN><\/SPAN><\/P>

                8<\/SPAN><\/SPAN>th<\/SPAN><\/SPAN> Sign Text \u2013 <\/SPAN><\/SPAN>text of eighth sign.<\/SPAN><\/SPAN><\/P>

                Signs_Count<\/SPAN><\/SPAN> \u2013 number of signs located on the pole/support<\/SPAN><\/SPAN><\/P>

                Status<\/SPAN><\/SPAN> \u2013 specify the existence status of the sign.<\/SPAN><\/SPAN><\/P>

                • Active<\/SPAN><\/SPAN><\/P><\/LI>

                • Inactive<\/SPAN><\/SPAN><\/P><\/LI>

                • Removed<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

                  Notes:<\/SPAN><\/SPAN><\/P>

                  - Domain: \u201cTraffic Status Code\u201d<\/SPAN><\/SPAN><\/P>

                  SECTION 3<\/SPAN><\/SPAN><\/P>

                  Handling of Data and Recommendations<\/SPAN><\/SPAN><\/P>

                  Multiple signs per pole - Each sign gets a point<\/SPAN><\/P><\/TD>

                  One point per sign<\/SPAN><\/P><\/TD>

                  <\/P><\/TD><\/TR>

                  Reflectivity Failures<\/SPAN><\/P><\/TD>

                  At start of each month, Asset Manager creates WO based on which signs failed the reflectivity test<\/SPAN><\/P><\/TD>

                  [Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] <\/SPAN><\/SPAN><\/P><\/TD><\/TR>

                  Title of<\/SPAN><\/SPAN><\/P>

                  Handling<\/SPAN><\/SPAN><\/P>

                  Topic #3<\/SPAN><\/SPAN><\/P><\/TD>

                  [Brief advice/description of how to address a specific component of/issue related to the data.]<\/SPAN><\/SPAN><\/P><\/TD>

                  [Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] <\/SPAN><\/SPAN><\/P><\/TD><\/TR>

                  Title of<\/SPAN><\/SPAN><\/P>

                  Handling<\/SPAN><\/SPAN><\/P>

                  Topic #4<\/SPAN><\/SPAN><\/P><\/TD>

                  [Brief advice/description of how to address a specific component of/issue related to the data.]<\/SPAN><\/SPAN><\/P><\/TD>

                  [Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] <\/SPAN><\/SPAN><\/P><\/TD><\/TR>

                  Title of<\/SPAN><\/SPAN><\/P>

                  Handling <\/SPAN><\/SPAN><\/P>

                  Topic #5<\/SPAN><\/SPAN><\/P><\/TD>

                  [Brief advice/description of how to address a specific component of/issue related to the data.]<\/SPAN><\/SPAN><\/P><\/TD>

                  [Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] <\/SPAN><\/SPAN><\/P><\/TD><\/TR><\/TBODY><\/TABLE>

                  SECTION 4<\/SPAN><\/SPAN><\/P>

                  Additional Considerations<\/SPAN><\/SPAN><\/P>

                  A. History & Logic of the Data<\/SPAN><\/SPAN><\/P>

                  [For future reference, please list facets of the history of the decision-making process related to the data\u2019s use \u2013 the <\/SPAN><\/SPAN>how<\/SPAN><\/SPAN> and <\/SPAN><\/SPAN>why<\/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>

                  ------<\/SPAN><\/SPAN><\/P>

                  7/11/2018\u2014MUTCD fields were discussed about removing, but MUTCD fields will be kept and will not be populated.<\/SPAN><\/P>

                  9/13/2018\u2014MUTCD_Category field will be population with values, for more specific searching criteria. \u201cType\u201d field was renamed to \u201cSign_Type\u201d 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. \u201cSupport_Type\u201d was updated to include delimiters, diverters, and light poles. \u201cSupport_Material\u201d has been restricted in its selection since \u201cSupport_Type\u201d describes the supporting material for most of the signs. Diverters\u2019 material type is always plastic.<\/SPAN><\/SPAN><\/P>

                  <\/P>

                  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>

                  B. Department Notes<\/SPAN><\/SPAN><\/P>

                  - Cityworks will need to track:<\/SPAN><\/SPAN><\/P>

                  • Money, Labor, and Equipment attributed to each Sign.<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

                    C. Unresolved Questions<\/SPAN><\/SPAN><\/P>

                    - N/A<\/SPAN><\/SPAN><\/P>

                    D. Other<\/SPAN><\/SPAN><\/P>

                    -N/A<\/SPAN><\/SPAN><\/P>

                    <\/P>

                    <\/P><\/DIV><\/DIV><\/DIV>", "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.\n\nThe 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.", "title": "Traffic Signs Current", "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" ], "type": "", "typeKeywords": [], "thumbnail": "", "url": "", "minScale": 50000, "maxScale": 5000, "spatialReference": "", "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.", "licenseInfo": "" }