Layer: Junction Boxes (ID: 0)

Name: Junction Boxes

Display Field: Unique_ID

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: <DIV STYLE="text-align:Left;"><DIV><DIV>INDEXSection 1: Responsible PartiesSection 2: Explanation of Attribute DataSection 3: Handling of Data and RecommendationsSection 4: Additional ConsiderationsSECTION 1 Responsible PartiesParties responsible for updating this layer:- 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.SECTION 2Explanation of Attribute DataUniqueID - unique identifying value assigned to a feature, generally same as OBJECTID. Location – closest address to the junction box’s location, full address - without ZIP code.Condition – conditional status that describes the junction box.Enable – 1 or 0.created_user – default editor tracking field, who created the feature.created_date – default editor tracking field, when the feature was created.last_edited_user – default editor tracking field, who last edited the feature.last_edited_date - default editor tracking field, when the feature was last edited.Shape – geometric shape of these features are points.GlobalID - default editor tracking field, unique serial number for the feature.SECTION 3Handling of Data and Recommendations<TABLE><TBODY><TR><TD>Title ofHandlingTopic #1</TD><TD>[Brief advice/description of how to address a specific component of/issue related to the data.]</TD><TD>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </TD></TR><TR><TD>Title ofHandlingTopic #2</TD><TD>[Brief advice/description of how to address a specific component of/issue related to the data.]</TD><TD>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </TD></TR><TR><TD>Title ofHandlingTopic #3</TD><TD>[Brief advice/description of how to address a specific component of/issue related to the data.]</TD><TD>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </TD></TR><TR><TD>Title ofHandlingTopic #4</TD><TD>[Brief advice/description of how to address a specific component of/issue related to the data.]</TD><TD>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </TD></TR><TR><TD>Title ofHandling Topic #5</TD><TD>[Brief advice/description of how to address a specific component of/issue related to the data.]</TD><TD>[Additional description of the handling -OR- comments -OR- brief notes on planning considerations for the data] </TD></TR></TBODY></TABLE>SECTION 4Additional ConsiderationsA. History & Logic of the Data[For future reference, please list facets of the history of the decision-making process related to the data’s use – the how and why 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.)------7/11/2018<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>Shawn determined he wanted Junction Boxes as a layer in GIS since the field crews frequently perform work on them around Mid-April<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>He determined he didn’t want any specific information on it (like JB depth, width, etc.), just where they are physically located in the field</LI></UL></LI><LI>Will Vint sat down for two days digitizing existing junction boxes using 2015 aerial imagery<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>He collected JBs that didn’t exist in imagery, but are currently in field</LI><LI>For the few that he couldn’t 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.<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>He collected about 119 junction boxes in one day.</LI></UL></LI></UL></LI><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.<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>As field crews find JBs that are NOT in the GIS, they will notify me or send me update GSI work orders via CityWorks</LI></UL></LI></UL>B. Department Notes- Cityworks will need to track:<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>Money, Labor, and Equipment attributed to each Junction Box.</LI></UL>Data to be Collected:<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>Vine and Old Furnace Rd</LI><LI>Reservoir St and E Market St</LI><LI>Chicago Ave and Gay St</LI><LI>Erickson Ave and Garbers Church Rd</LI></UL>C. Unresolved Questions- N/AD. Other Data to be Collected: as of 7/11/2018 - Vine and Old Furnace Rd - Reservoir St and E Market St - Chicago Ave and Gay St - Erickson Ave and Garbers Church Rd</DIV></DIV></DIV>

Service Item Id: b3196c81dc754afd88d501b43635608e

Copyright Text: 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. Asset Editor: Asset Manager (PW) & Systems Analyst (PW)

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

Drawing Info:

Renderer:

Simple Renderer:

Symbol:

Label:

Description:

Transparency:

Labeling Info:

Advanced Query Capabilities:

HasZ: false

HasM: false

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
Unique_ID ( type: esriFieldTypeString, alias: Unique_ID, length: 255 )
Location ( type: esriFieldTypeString, alias: Location, length: 50 )
Condition ( type: esriFieldTypeSmallInteger, alias: Condition )
Enable ( type: esriFieldTypeSmallInteger, alias: Enable )
created_user ( type: esriFieldTypeString, alias: created_user, length: 255 )
created_date ( type: esriFieldTypeDate, alias: created_date, length: 8 )
last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, length: 255 )
last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, length: 8 )
Status ( type: esriFieldTypeString, alias: Status, length: 50 , Coded Values: [Active: Active] , [Removed: Removed] )
SHAPE ( type: esriFieldTypeGeometry, alias: SHAPE )
GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, length: 38 )

Supported Operations: Query Query Attachments Query Analytic Generate Renderer Return Updates

Iteminfo Thumbnail Metadata