Create Beacon Data Audit Map

[johnclary]

Ability to:

• create new beacons
• edit existing beacons
• mark beacons as deleted
• use Nearmap aerials basemap

Next steps:

• John to send schema
• Jaime to review schema with Billy. Ask if they want to do field checks/use Collector.

[johnclary]

Ability to:

• create new beacons
• edit existing beacons
• mark beacons as deleted
• use Nearmap aerials basemap

[johnclary]

@jaime-mckeown here's a list of the fields and controlled values we need for this layer. It also includes the sample data that is in the app today: https://docs.google.com/spreadsheets/d/1NpPK1Icqpgfcfh17i2uZVNAzCBFwYX_eYa_kV-fpk4Y/edit#gid=1110700016

You can make a copy of the existing beacons layer and just hide/remove the other fields in that layer. Let me know if this doesn't make sense and I'm happy to talk more.

[jaime-mckeown]

Meeting with Billy Friday morning to go over the current fields that are in Knack.

[jaime-mckeown]

Knack Schema

Bold fields are fields that Billy definitely wants included in Audit

• BEACON_ID - program calculated (Zone, Clock_ID, Beacon_ID_Short), does Beacon ID populate fields or do fields populate Beacon ID?
• ZONE_NAME_INT - field I added to show the first 4 digits of the Beacon ID?
• ZONE_NAME - Integer field, first 4 digits of Beacon ID, shows as text in table
• ZONE_STATUS
• ZONE_ID - text name field for school
• CLOCK_ID - middle 3 digits of Beacon_ID
• CLOCK - Yes/No field, yes indicates the clock controls all the beacons in that zone
• BEACON_ID_SHORT - last 2 digits of Beacon_ID
• DIRECTION - EB/NB/SB/WB, direction the beacon faces
• _HEIGHTINCHES - don't need, unless it's needed for something Billy is not aware of
• POLE_TYPE - 2_IN/4_IN/STREET/WOOD, Billy said this depends on what the data is used for...
• POWER_FEED - OH/UG (overhead, underground)
• MOUNT_LOCATION - POLE/SP/MA (Pole, Span Wire, Mast Arm), waiting to hear back from Billy to see if he would now like to include this field
• POWER_SOURCE - AC/Solar (if solar, power feed should be blank)
• ATD_LOCATION_ID - program calculated
• Editor Tracking Fields
  • CREATED_DATE
  • CREATED_BY
  • MODIFIED_DATE
  • MODIFIED_BY
• How are the time fields updated, Knack to elsewhere or elsewhere to Knack???
  • AM_START
  • AM_END
  • PM_START
  • PM_END
  • PM_START_2
  • PM_END_2
• Program calculated by John?
  • LOCATION - is this the physical address where the beacon is located??? Research this. Tech's will need to verify addresses!
  • LOCATION: Street 1
  • LOCATION: Street 2
  • LOCATION: City
  • LOCATION: State
  • LOCATION: Zip
  • LOCATION: Country
  • LOCATION: Latitude
  • LOCATION: Longitude
  • _LOCATIONNAME - Block is not needed, they need physical address
  • _PRIMARY_ST_SEGMENT_DISPLAYNAME
  • _CROSS_ST_SEGMENT_DISPLAYNAME
  • _PRIMARYST
  • _CROSSST
  • _CROSS_STBLOCK
  • _PRIMARY_STBLOCK
  • _COA_INTERSECTIONID - field is blank throughout data
  • JURISDICTION_LABEL
  • COUNCIL_DISTRICT
• LANDMARK
• Are Plans concatenated from the above AM/PM times?
  • AM_PLAN
  • PM_PLAN
  • PM_PLAN_2_DISPLAY
• MODIFIED_DATE - editor tracking field
• OTHER
• NOTES - this field won't be needed after they can do work orders down to the beacon level

[jaime-mckeown]

@johnclary I met with Billy this morning and discussed, which has brought more questions about the process. I was thinking that we could use my 1:1 next Tuesday to talk about School Zone Beacons in greater detail if that's ok.

[jaime-mckeown]

Meeting Notes

• The signal technicians that will be working on the school zone beacons data will work in the office and in the field, will need to create Web App and Collector App for editing.
• The work order system currently goes down to the zone, i.e. 7101, but they need it to go down to the Beacon ID so they can more easily pinpoint which beacon needs maintenance, has a problem, etc.
• Each beacon needs to have an exact address assigned to it, street blocks are not useful. Billy imagines that address of the property that the beacon is closest to as the address to be used.
• Notes from attribute fields are in a comment above.

[johnclary]

thanks @jaime-mckeown. good stuff. let me know if you need any help/input from me.

[jaime-mckeown]

Talked to John about the School Zone Beacon data after talking with Billy.

• Location address field is currently geocoded through HERE service which can give unusual results. We are going to allow the Signal Tech's to assign an address to each SZB, with the address fields broken up for cleaner editing (Street Number, Street Pre-Direction, Street Name, Street Type). Domains can be added on Street Pre-Direction and Street Type fields.
• John helped me figure out what the domain for Mount Location meant. Added to field description above, sent Billy email.

[jaime-mckeown]

Domains for Data Audit

ATD_SZB_BEACON_ID

• 0, 1, 2, 3, 4, 5, 6, 7, 8, 9

ATD_SZB_BEACON_STATUS

• OK (OK)
• NEW (New)
• REMOVE (Remove)

ATD_SZB_CLOCK

• Yes
• No

ATD_SZB_DIRECTION

• EB (East Bound)
• NB (North Bound)
• SB (South Bound)
• WB (West Bound)

ATD_SZB_MOUNT_LOCATION

• MA (Mast Arm)
• POLE (Pole)
• SP (Span Wire)

ATD_SZB_POLE_TYPE

• 2_IN (2 Inch)
• 4_IN (4 Inch)
• STREET (Street)
• WOOD (Wood)

ATD_SZB_POWER_FEED

• OH (Overhead)
• UG (Underground)

ATD_SZB_POWER_SOURCE

• AC (AC)
• SOLAR (Solar)

ATD_SZB_PREFIX_DIRECTION

• E (East)
• N (North)
• S (South)
• W (West)

*ATD_SZB_PREFIX_TYPE**

• CR (County Road)
• FM (Farm to Market Road)
• IH (Interstate Highway)
• SH (State Highway)
• US (U.S. Highway)

ATD_SZB_STREET_TYPE

• ALY (Alley)
• AVE (Avenue)
• BLVD (Boulevard)
• BND (Bend)
• BR (Branch)
• BRG (Bridge)
• CIR (Circle)
• CRES (Crescent)
• CT (Court)
• CTOF (Cutoff)
• CV (Cove)
• CYN (Canyon)
• DR (Drive)
• EXPY (Expressway)
• GDNS (Gardens)
• GLN (Glen)
• HOLW (Hollow)
• HWY (Highway)
• LN (Lane)
• LOOP (Loop)
• PARK (Park)
• PASS (Pass)
• PATH (Path)
• PKWY (Parkway)
• PL (Place)
• PLZ (Plaza)
• PT (Point)
• RACE (Race)
• RAMP (Ramp)
• RD (Road)
• ROW (ROW)
• RUN (Run)
• SKWY (Skyway)
• SPUR (Spur)
• SQ (Square)
• ST (Street)
• SVRD (Service Road)
• TER (Terrace)
• TRCE (Trace)
• TRL (Trail)
• TRN (Turnaround)
• VW (View)
• WALK (Walk)
• WAY (Way)
• XING (Crossing)

ATD_SZB_ZONE_STATUS

• Active
• Inactive

[jaime-mckeown]

Created a Spreadsheet, emailed to Billy so he can verify the fields that they will be modifying before I create the dataset in AGOL.

[jaime-mckeown]

• Billy said the fields were good.
• Created the feature class, included some of the fields he didn't need for future use and turned them off for the edit project.
• Created the School Zone Beacon Audit Map and configured. Added Bookmarks for each school to make it easier for the tech's to get around in the map.
• Created the School Zone Beacon Audit Web App for desktop editing.
• Checked the Web Map in Collector, changed Basemap to World Street Map as State Plane Maps don't draw in Collector.
• Created COA_ATD_School_Zone_Beacons_Audit Group in AGOL to ensure only the specified people can edit the data.

[jaime-mckeown]

• [x] Go over Web App with Billy, get Tech names to add to Group.

[jaime-mckeown]

Added Installation Date to Feature Layer and configured Pop-up.

[jaime-mckeown]

Discussion with Billy about Audit Map

• He said that all the fields were good
• All data they needed to do the audit is included ( I can always add more layers if needed)
• We discussed the ability to add their own addresses and I shared with him the idea of CTM Addressing Group assigning physical addresses to the beacons. I'm waiting to hear back from Jacquie regarding that request.
• He will get with his staff to figure out exactly who will be starting work on this project.
• Schedule training for next week based on their schedules.
• I will need to add users to the AGOL Group to have access to the Web App.
• Web Application is only Shared with SZB Audit Group https://austin.maps.arcgis.com/apps/webappviewer/index.html?id=a54f7230cf5749e4b3a805b7d16bec01