Add High Risk Wildland Urban Interface from DNR FFSL

[eneemann]

Summary

• Proposed Readable Name: Utah High Risk Wildland Urban Interface
• Proposed Internal Dataset Name: HighRiskWildlandUrbanInterface
• Proposed External Dataset Name: high_risk_wildland_urban_interface
• Proposed Data Category: Boundaries, secondary of Bioscience
• Data Description: Polygons representing the high risk wildland urban interface as defined by DNR FFSL.
• Source Agency/Entity: DNR FFSL
• Contact: Tommy Thompson
• Update Frequency: As Needed, will get clarification from DNR

This data layer will originate from DNR Forestry, Fire, and State Lands to represent "High Risk" areas in the Wildand Urban Interface and is one result of HB 48 from the 2025 legislative session.

The data should be available in

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

• Internal SGID
• Open SGID
• ArcGIS Online
• Open Data

The data is of high quality

• Sweeper checks have run and passed (@eneemann on 2025/12/16)
• The minimum requirements for metadata are populated (@eneemann on 2025/12/16)
• The data complies with our domain rules (@eneemann on 2025/12/16)

Where is the data source

Choose one.

• Internal SGID
• Farm from AGOL (agol item url) - will be shared publicly on 12/18/2025
• UGRC AGOL

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.

- [ ] Add data to the Internal SGID (name, completed: 2025/00/00)

• Add new entry to MATT (@eneemann, completed: 2025/12/18)
• Configure forklift for Farm from AGOL (@stdavis, completed: 2025/12/18) (https://github.com/agrc/warehouse/pull/164)
• Update relevant gis.utah.gov data pages (@eneemann, completed: 2025/12/18)
• Add a SGID Index record (@eneemann, completed: 2025/12/18)
• Complete a SGID.META.AGOLItems record (@eneemann, completed: 2025/12/18)
  • AGOL_ITEM_ID will be populated by Forklift after it publishes the new AGOL item.

[ ] Complete an AGOLItems_shelved record for any static or shelved item (name, completed: 2025/00/00)
[ ] Data is assigned to a record series with archives (@eneemann, completed: 2025/00/00)

• Since this isn't "our" layer and we are just sharing/republishing, it don't think we need a record series entry

[ ] If data is hosted in AGOL exclusively, add Backup tag to hosted feature layer so that it will be backed up by moonwalk (@eneemann, completed: 2025/00/00)

🤖 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 2025/01/01 when the task is verified.
3. Strike out all items that do not apply.

• Open SGID via cloudb (@steveoh on 2025/12/23)
• ArcGIS Online via forklift (@stdavis on 2025/00/00)
• Auditor ran successfully (@jacobdadams on 2025/00/00)
• SGID on ArcGIS (@eneemann on 2025/12/24)
• gis.utah.gov data pages (@steveoh on 2025/12/23)
• sgid-index (@steveoh on 2025/12/23)

Notification

• X (@steveoh)

Group Task Assignments

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

• Data Team (@eneemann)
• Dev Team (@steveoh)
• Cadastre Team (@rkelson)

[chriswnek]

Discussed in team meeting on 12/11: Will need to set up the farm from AGOL, sweeping, etc. services after the data can be available on 12/18/25.

[eneemann]

@steveoh FYI...there's a discrepancy between the name we were asked to publish for the data and the name it has in AGOL. We are using "High Risk Wildland Urban Interface". The item in AGOL name is Utah "High Risk WUI Properties". Since it's a Farm from AGOL, In the META.AGOLItems table, I used our name in the AGOL_PUBLISHED_NAME field (see image below) because that is our desired name for the opensgid layer. Let me know if that won't work.

[steveoh]

I can't think of a reason that will be a problem. Where is your concern?

[eneemann]

I wasn't sure if there were any validations or potential issues that would arise from the name in the AGOL_PUBLISHED_NAME field not actually matching the name of the item in AGOL.

[steveoh]

it's after 12/18. removing the block

[agrc-conductor]

conductor results for tasks - 453

check	status
eneemann has completed 9 out of 9 tasks	👍
@stdavis has completed 1 out of 2 tasks	⛔
steveoh has completed 5 out of 5 tasks	👍
@jacobdadams has completed 0 out of 1 tasks	⛔
rkelson has completed 1 out of 1 tasks	👍

[agrc-conductor]

conductor results for Boundaries.HighRiskWildlandUrbanInterface

check	status
internal sgid	👍
meta table
- item id	👍
- item name	👍
- geometry type	👍
open sgid	👍
open data	👍
arcgis online	⛔
SGID Index
- displayName	👍
- description	👍
- justification	👍
- category	👍
- productType	👍
- ugrcSteward	👍
- dataContactName	👍
- dataContactEmail	👍

[eneemann]

This layer is hosted in DNR's AGOL org, so I think we can ignore that automated validation.