Layer: Ped Assembly (ID: 3)

View In: ArcGIS Online Map Viewer

Name: Ped Assembly

Display Field: Type

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 DataType – type of pedestrian assembly<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>APA</LI><LI>APS w/ BlueTooth</LI><LI>Regular Push Button</LI></UL>Notes:- Domain: “Ped_Model_Type”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.LocationType – location of pedestrian assembly<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>Pole</LI><LI>Stand Alone</LI></UL>Notes:- Domain: “Ped_Location”Location – closest address to the pedestrian assembly’s location, full address - without ZIP code.Date_Installed – date the asset was installed.Condition – conditional status that describes the pedestrian assembly.Enable – 1 or 0.No. of Ped Heads – number of heads on pedestrian assembly<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>Range: 0-3</LI></UL>Notes:- Domain: “No_of_PedHeads”UniqueID - unique identifying value assigned to a feature, generally same as OBJECTID. Decorative Pad? – does the pedestrian assembly have a decorative pad.<UL STYLE="margin:0 0 0 0;padding:0 0 0 0;"><LI>Yes</LI><LI>No</LI></UL>Notes:- Domain: “YesNo_1”Reinstall_Date – if the pedestrian assembly was removed and then reinstalled, the date of its re-installation.GlobalID - default editor tracking field, unique serial number for the feature.Shape – geometric shape of these features are points.SECTION 3Handling of Data and Recommendations<TABLE><TBODY><TR><TD>Placement of Ped Assembly Points</TD><TD>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</TD><TD>In other words, place point on left or right side in order to distinguish</TD></TR><TR><TD>Ped. Assemblies with two or more signal heads.</TD><TD>Do NOT drop two points for ped assemblies that have more than one head, drop only one point per assembly. </TD><TD>There is a field called “No. of Ped. Heads”, this will track the no. of ped. heads attached to the assembly.</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.)------- N/AB. 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 pedestrian assembly</LI></UL>C. Unresolved Questions- N/AD. Other- N/A</DIV></DIV></DIV>

Service Item Id: 339f28fce59f4c60a551a9b6bc40a5c6

Copyright Text: 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)

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: true

Supports Datum Transformation: true

Extent:

Drawing Info:

Renderer:

Simple Renderer:

Symbol:

Style:

Color:

Size:

Angle:

XOffset:

YOffset:

Outline:

Width:

Label:

Description:

Transparency:

Labeling Info:

Advanced Query Capabilities:

HasZ: false

HasM: false

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field:

Fields:

OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID, editable: false, nullable: false, defaultValue: null, modelName: OBJECTID )
Unique_ID ( type: esriFieldTypeString, alias: Unique ID, editable: true, nullable: true, length: 50, defaultValue: null, modelName: Unique_ID )
Status ( type: esriFieldTypeString, alias: Status, editable: true, nullable: true, length: 50, defaultValue: Active, modelName: Status , Coded Values: [Active: Active] , [Removed: Removed] )
Type ( type: esriFieldTypeString, alias: Type, editable: true, nullable: true, length: 50, defaultValue: null, modelName: Type , Coded Values: [APS: APS] , [ApsBT: APS w/ BlueTooth] , [Reg: Regular Push Button] )
Location ( type: esriFieldTypeString, alias: Location, editable: true, nullable: true, length: 50, defaultValue: null, modelName: Location )
Location_Type ( type: esriFieldTypeString, alias: Location Type, editable: true, nullable: true, length: 50, defaultValue: null, modelName: Location_Type , Coded Values: [Pole: Pole] , [StandAlone: Stand Alone] )
No_of_Ped_Heads ( type: esriFieldTypeSmallInteger, alias: No. of Ped Heads, editable: true, nullable: true, defaultValue: null, modelName: No_of_Ped_Heads , Range: [0, 3] )
Date_Installed ( type: esriFieldTypeDate, alias: Date Installed, editable: true, nullable: true, length: 8, defaultValue: null, modelName: Date_Installed , Range: [-2208988800000, 4102272000000] )
Condition ( type: esriFieldTypeSmallInteger, alias: Condition, editable: true, nullable: true, defaultValue: null, modelName: Condition )
Enable ( type: esriFieldTypeSmallInteger, alias: Enable, editable: true, nullable: true, defaultValue: null, modelName: Enable )
Decorative_Ped ( type: esriFieldTypeString, alias: Decorative Ped?, editable: true, nullable: true, length: 50, defaultValue: null, modelName: Decorative_Ped , Coded Values: [Yes: Yes] , [No: No] )
Reinstall_Date ( type: esriFieldTypeDate, alias: Reinstall Date, editable: true, nullable: true, length: 8, defaultValue: null, modelName: Reinstall_Date )
created_user ( type: esriFieldTypeString, alias: created_user, editable: false, nullable: true, length: 255, defaultValue: null, modelName: created_user )
created_date ( type: esriFieldTypeDate, alias: created_date, editable: false, nullable: true, length: 8, defaultValue: null, modelName: created_date )
last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, editable: false, nullable: true, length: 255, defaultValue: null, modelName: last_edited_user )
last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, editable: false, nullable: true, length: 8, defaultValue: null, modelName: last_edited_date )
GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, editable: false, nullable: false, length: 38, defaultValue: null, modelName: GlobalID )
ADAComp ( type: esriFieldTypeString, alias: ADA Compliant, editable: true, nullable: true, length: 75, defaultValue: null, modelName: ADAComp , Coded Values: [Compliant: Compliant] , [Maximum Extent Feasible: Maximum Extent Feasible] , [Non-Compliant: Non-Compliant] )

Templates:

Name: Ped Assembly
Description:
Prototype:
Drawing Tool: esriFeatureEditToolPoint

Capabilities: Query,Create,Update,Delete,Uploads,Editing

Sync Can Return Changes: true

Is Data Versioned: true

Supports Rollback On Failure: false

Supports ApplyEdits With Global Ids: false

Supports ApplyEdits By Upload Id: true

Edit Fields Info:

Creation Date Field: created_date
Creator Field: created_user
Edit Date Field: last_edited_date
Editor Field: last_edited_user

Supports Query With Historic Moment: false

Supports Coordinates Quantization: true

Supported Operations: Query Query Attachments Query Analytic Apply Edits Add Features Update Features Delete Features Calculate Validate SQL Generate Renderer Return Updates Iteminfo Thumbnail Metadata