{ "culture": "en-US", "name": "", "guid": "", "catalogPath": "", "snippet": "The traffic Junction Boxes layer is a point layer that displays only the locations of all the COH-PW maintained Junction Boxes at intersections in the City of Harrisonburg. Junction Boxes are a box used to pull wire from one signal/intersection to another for fiber, DSL, electrical, etc. 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><\/SPAN><\/P>

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

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

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

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

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

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

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

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

Condition<\/SPAN><\/SPAN> \u2013 conditional status that describes the junction box.<\/SPAN><\/SPAN><\/P>

Enable \u2013 <\/SPAN><\/SPAN>1 or 0.<\/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>

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>

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

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

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

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

Topic #1<\/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 #2<\/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 #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<\/SPAN><\/SPAN><\/P>

  • Shawn determined he wanted Junction Boxes as a layer in GIS since the field crews frequently perform work on them around Mid-April<\/SPAN><\/SPAN><\/P>

    • He determined he didn\u2019t want any specific information on it (like JB depth, width, etc.), just where they are physically located in the field<\/SPAN><\/SPAN><\/P><\/LI><\/UL><\/LI>

    • Will Vint sat down for two days digitizing existing junction boxes using 2015 aerial imagery<\/SPAN><\/SPAN><\/P>

      • He collected JBs that didn\u2019t exist in imagery, but are currently in field<\/SPAN><\/SPAN><\/P><\/LI>

      • For the few that he couldn\u2019t find in imagery, such as updated intersection and road corridors, I set him up with a map service using the collector app on a tablet.<\/SPAN><\/SPAN><\/P>

        • He collected about 119 junction boxes in one day.<\/SPAN><\/SPAN><\/P><\/LI><\/UL><\/LI><\/UL><\/LI>

        • Shawn and Jim are aware that not all junction boxes will have been documented in GIS since some are covered with dirt, grass, etc.<\/SPAN><\/SPAN><\/P>

          • As field crews find JBs that are NOT in the GIS, they will notify me or send me update GSI work orders via CityWorks<\/SPAN><\/SPAN><\/P><\/LI><\/UL><\/LI><\/UL>

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

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

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

              Data to be Collected:<\/SPAN><\/SPAN><\/P>

              • Vine and Old Furnace Rd<\/SPAN><\/SPAN><\/P><\/LI>

              • Reservoir St and E Market St<\/SPAN><\/SPAN><\/P><\/LI>

              • Chicago Ave and Gay St<\/SPAN><\/SPAN><\/P><\/LI>

              • Erickson Ave and Garbers Church Rd<\/SPAN><\/SPAN><\/P><\/LI><\/UL>

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

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

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

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

                Data to be Collected: as of 7/11/2018<\/SPAN><\/SPAN><\/P>

                - Vine and Old Furnace Rd<\/SPAN><\/SPAN><\/P>

                - Reservoir St and E Market St<\/SPAN><\/SPAN><\/P>

                - Chicago Ave and Gay St<\/SPAN><\/SPAN><\/P>

                - Erickson Ave and Garbers Church Rd<\/SPAN><\/SPAN><\/P>

                <\/P><\/DIV><\/DIV><\/DIV>", "summary": "The traffic Junction Boxes layer is a point layer that displays only the locations of all the COH-PW maintained Junction Boxes at intersections in the City of Harrisonburg. Junction Boxes are a box used to pull wire from one signal/intersection to another for fiber, DSL, electrical, etc. 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 Junction Boxes", "tags": [ "City of Harrisonburg", "Harrisonburg", "Public Works Department", "Traffic", "TRAFFIC", "Junction Boxes", "local government", "Virginia", "street", "streets", "public", "public works", "works", "CityWorks", "City Works", "city works", "Asset Management", "traffic", "traffic assets", "junction boxes", "boxes", "junction", "wires", "fiber", "DSL", "electrical" ], "type": "", "typeKeywords": [], "thumbnail": "", "url": "", "minScale": 150000000, "maxScale": 5000, "spatialReference": "", "accessInformation": "The Junction Box data layer was created by Alfredo Velasquez in the Public Works Department of the City of Harrisonburg, on 5/1/2018. This information was created under the supervision of the Systems Analyst and in association with the City of Harrisonburg.\n\nAsset Editor: Asset Manager (PW) & Systems Analyst (PW)", "licenseInfo": "" }