Add Utah Telecom Boundaries from URTA and FCC

[ZachBeck]

Summary

• Proposed Readable Name: Utah Telecom Boundaries
• Proposed Internal Dataset Name: SGID.UTILITIES.TelecomBoundaries
• Proposed External Dataset Name: opensgid.utilities.telecom_boundaries
• Proposed Data Category: Utilities
• Data Description: Urban and rural telecom boundaries of Utah
• Source Agency/Entity: URTA / FCC
• Contact: Jim Nelson jim.nelson@jsitel.com
• Update Frequency: As needed

This data is current and will replace outdated UTILITIES.RuralTelecomBoundaries once they have been shelved

The data should be available in

1 Check [x] all the areas where you expect the data to show up.

• [x] Internal SGID
• [x] Open SGID
• [x] ArcGIS Online
• [x] Open Data

The data is of high quality

• [x] Sweeper checks have run and passed (@ZachBeck on 2024/01/02)
• [x] The minimum requirements for metadata are populated (@ZachBeck on 2024/01/02)
• [x] The data complies with our domain rules (@ZachBeck on 2024/01/02)

Where is the data source

Choose one.

• [x] Internal SGID
• [ ] Farm from AGOL (agol item url)

Action items

1. Assign a person who should complete the task by replacing name with their github @name.
2. Check [x] the box when the task is completed and add the date of completion.
3. ~Strike~ out all items that do not apply.

• [x] Add data to the Internal SGID (@ZachBeck , completed: 2024/01/02)
• ~[ ] Configure forklift for Farm from AGOL (name, completed: 2023/00/00)~
• [x] Update relevant gis.utah.gov data pages (@ZachBeck , completed: 2024/01/25)
• [x] Add a Stewardship record (@ZachBeck, completed: 2024/01/02)
• [x] Complete a SGID.META.AGOLItems record (@ZachBeck, completed: 2024/01/02)
  • AGOL_ITEM_ID will be populated by Forklift after it publishes the new AGOL item.
• [x] Complete an AGOLItems_shelved record for any static or shelved item (@ZachBeck, completed: 2024/01/29) ~- [ ] Define a record set with archives (@brigsz, completed: 2023/00/00)~

:robot: Automation validation

1. Assign yourself or someone to check the item by replacing name with their github @name.
2. Check [x] the box and add the date of verification 2020/01/01 when the task is verified.
3. ~Strike~ out all items that do not apply.

• [x] Open SGID via cloudb (@steveoh on 2024/01/22)
• [x] ArcGIS Online via forklift (@stdavis on 2024/01/08)
• [x] Auditor ran successfully (@jacobdadams on 2024/01/05)
• [x] Open Data (@ZachBeck on 2023/01/08)
• [x] gis.utah.gov data pages (@ZachBeck on 2024/01/25)
• [x] sgid-index (@steveoh on 2024/01/22)

Notification

• [x] Twitter (@steveoh)

Group Task Assignments

1. Check [x] the box when you have assigned all the tasks relevant to your group.

• [x] Data Team (@gregbunce)
• [x] Dev Team (@steveoh)
• [x] Cadastre Team (@rkelson)

[steveoh]

Not having an update schedule and steward contact seems a bit problematic don't we think?

[ZachBeck]

Not really. It's a mash up of data from the URTA and FCC so there is no steward and the boundaries don't change very often so I don't think that it needs to be put on a schedule.

[nathankota]

Possible "stewards": URTA:

FCC: https://www.fcc.gov/reports-research/maps/study-area-boundaries/

[nathankota]

...the boundaries don't change very often so I don't think that it needs to be put on a schedule.

perhaps we look at the FCC posted date and check-in with URTA annually

[steveoh]

It's a mash up of data from the URTA and FCC so there is no steward

It would be ideal to have a contact from each of those places for the data they are providing that is getting mashed up.

...the boundaries don't change very often so I don't think that it needs to be put on a schedule.

I like the idea of checking the FCC date and URTA annually. As needed seems like a catch all that is ignored. It doesn't fit into the grading process greg has been working on to validate that data is still of high quality.

[agrc-conductor]

conductor results for tasks - 281

check	status
@gregbunce has completed 0 out of 4 tasks	:no_entry:
@ZachBeck has completed 0 out of 6 tasks	:no_entry:
@brigsz has completed 0 out of 1 tasks	:no_entry:
@steveoh has completed 1 out of 4 tasks	:no_entry:
@stdavis has completed 0 out of 1 tasks	:no_entry:
@jacobdadams has completed 0 out of 1 tasks	:no_entry:
rkelson has completed 1 out of 1 tasks	:+1:

[gregbunce]

I believe sweeper will run on this layer once it's added to Internal. correct me if i'm wrong.

[steveoh]

It was my understanding that you run it and fix the issues prior to adding it to internal.

[agrc-conductor]

conductor results for tasks - 281

check	status
@ZachBeck has completed 0 out of 10 tasks	:no_entry:
@brigsz has completed 0 out of 1 tasks	:no_entry:
@steveoh has completed 1 out of 4 tasks	:no_entry:
@stdavis has completed 0 out of 1 tasks	:no_entry:
@jacobdadams has completed 0 out of 1 tasks	:no_entry:
gregbunce has completed 1 out of 1 tasks	:+1:
rkelson has completed 1 out of 1 tasks	:+1:

[agrc-conductor]

conductor results for tasks - 281

check	status
@ZachBeck has completed 0 out of 10 tasks	:no_entry:
@brigsz has completed 0 out of 1 tasks	:no_entry:
@steveoh has completed 1 out of 4 tasks	:no_entry:
@stdavis has completed 0 out of 1 tasks	:no_entry:
@jacobdadams has completed 0 out of 1 tasks	:no_entry:
gregbunce has completed 1 out of 1 tasks	:+1:
rkelson has completed 1 out of 1 tasks	:+1:

[agrc-conductor]

conductor results for tasks - 281

check	status
@ZachBeck has completed 6 out of 10 tasks	:no_entry:
@brigsz has completed 0 out of 1 tasks	:no_entry:
@steveoh has completed 2 out of 4 tasks	:no_entry:
@stdavis has completed 0 out of 1 tasks	:no_entry:
jacobdadams has completed 1 out of 1 tasks	:+1:
gregbunce has completed 1 out of 1 tasks	:+1:
rkelson has completed 1 out of 1 tasks	:+1:

[agrc-conductor]

conductor results for tasks - 281

check	status
@ZachBeck has completed 7 out of 10 tasks	:no_entry:
@brigsz has completed 0 out of 1 tasks	:no_entry:
@steveoh has completed 2 out of 4 tasks	:no_entry:
stdavis has completed 1 out of 1 tasks	:+1:
jacobdadams has completed 1 out of 1 tasks	:+1:
gregbunce has completed 1 out of 1 tasks	:+1:
rkelson has completed 1 out of 1 tasks	:+1:

[agrc-conductor]

conductor results for UTILITIES.TelecomBoundaries

check	status
internal sgid	:+1:
meta table
- item id	:+1:
- item name	:+1:
- geometry type	:+1:
open sgid	:+1:
open data	:+1:
arcgis online	:+1:
stewardship
- Description	:+1:
- Data Source	:+1:
- Website URL	:+1:
- Endpoint	:+1:
- Data Type	:+1:

[agrc-conductor]

conductor results for tasks - 281

check	status
@ZachBeck has completed 7 out of 10 tasks	:no_entry:
@brigsz has completed 0 out of 1 tasks	:no_entry:
@steveoh has completed 2 out of 4 tasks	:no_entry:
stdavis has completed 1 out of 1 tasks	:+1:
jacobdadams has completed 1 out of 1 tasks	:+1:
gregbunce has completed 1 out of 1 tasks	:+1:
rkelson has completed 1 out of 1 tasks	:+1:

[agrc-conductor]

conductor results for UTILITIES.TelecomBoundaries

check	status
internal sgid	:+1:
meta table
- item id	:+1:
- item name	:+1:
- geometry type	:+1:
open sgid	:+1:
open data	:+1:
arcgis online	:+1:
stewardship
- Description	:+1:
- Data Source	:+1:
- Website URL	:+1:
- Endpoint	:+1:
- Data Type	:+1:

[agrc-conductor]

conductor results for tasks - 281

check	status
@ZachBeck has completed 9 out of 10 tasks	:no_entry:
@brigsz has completed 0 out of 1 tasks	:no_entry:
steveoh has completed 4 out of 4 tasks	:+1:
stdavis has completed 1 out of 1 tasks	:+1:
jacobdadams has completed 1 out of 1 tasks	:+1:
gregbunce has completed 1 out of 1 tasks	:+1:
rkelson has completed 1 out of 1 tasks	:+1:

[agrc-conductor]

conductor results for UTILITIES.TelecomBoundaries

check	status
internal sgid	:+1:
meta table
- item id	:+1:
- item name	:+1:
- geometry type	:+1:
open sgid	:+1:
open data	:+1:
arcgis online	:+1:
stewardship
- Description	:+1:
- Data Source	:+1:
- Website URL	:+1:
- Endpoint	:+1:
- Data Type	:+1:

[ZachBeck]

Done