Remove Ports Of Entry from SGID

[eneemann]

Summary

• Internal Dataset Name: SGID.TRANSPORTATION.PortsOfEntry
• External Dataset Name: Utah Ports of Entry
• ArcGIS Online Url: https://utah.maps.arcgis.com/home/item.html?id=73441947b3f342b880edcb3d8cdd7ea2

The Ports of Entry layer is old and not maintained. UDOT has Ports of Entry data in a Facility Inventory layer that is more accurate and regularly maintained, so we will reference their data as a replacement. However, we are waiting for the Facility Inventory layer to become available via their AGOL and UDOT Open Data Portal offerings.

Migration Guide

This dataset will be replaced by a UDOT Facility Inventory layer that contains Ports of Entry. The UDOT Facility Inventory is currently available as a Map Service, but is not yet in AGOL or the UDOT Open Data Portal. We will standby while UDOT updates their Open Data Portal and eventually replace our internal layer with their Facility Inventory layer when/if it is published.

The existing map service can be queried with FACILITIES_CLASS_CODE_NAME = 'Port of Entry' to extract just the Ports of Entry.

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.

Soft Delete

The purpose of the soft delete is to ensure that all of our users and applications have gracefully migrated off of the dataset. Soft deletes will remain in effect for 14 days. During this time, we will have the ability to restore the dataset to its original SGID offering(s). After these 14 days, the item is then ready for a hard delete.

Note: If this dataset is being replaced, then wait until the new data is publicly available before completing these steps:

• Append "(Mature Support)" to the end of the item title in the SGID.META.AGOLItems table (name, completed: 2025/00/00)
• Remove all tags other than "Deprecated" in the SDE metadata (name, completed: 2025/00/00)
• Add note to SDE description noting when layer will be deleted and any replacement layer (name, completed: 2025/00/00)
• Update the SGID Index row as deprecated by pasting the related Porter issue URL in the "porterUrl" field and setting the value of the "indexStatus" field as "removed". Also update the "refreshCycle" field (name, completed: 2025/00/00)
• Change Authoritative field to d in SGID.META.AGOLItems to automatically set the Deprecated AGOL flag. Allow the d to persist through one run of Auditor - currently, Auditor runs daily at 5:00am (name, completed: 2025/00/00)
  • After at least one successful run of Auditor:
    • Remove the row from the SGID.META.AGOLItems table. This will trigger the removal of this item in Open SGID (name, completed: 2025/00/00)
    • Unshare the item from its SGID group, which will remove it from the SGID on ArcGIS (name, completed: 2025/00/00)
• Check if this layer in the base maps. If so, work with Zach to develop a path forward before you proceed with a Hard Delete (name, completed: 2025/00/00).

Hard Delete

Target Date: 2025/00/00

Hard deletes are final. It is recommended to complete the soft delete process before moving on to these steps. If you decide to skip the soft delete, note that you will need to incorporate some of those steps here.

• Manually remove data from the Internal SGID (name, completed: 2025/00/00)
  • Deprecated database layers should be backed up on Google Drive > AGRC Projects > SGID > deprecated layers > internal_db_sgid_layers (name, completed: 2025/00/00).
• Remove ArcGIS Online item: (name, completed: 2025/00/00)
  • Manually delete the AGOL item
  • -OR-
  • Unshare by changing the AGOL_ITEM_ID field in SGID.META.AGOLItems to something other than an Item ID and manually changing the sharing settings (remove the item from all SGID groups, remove Public sharing),
  • -OR-
  • Shelve the data by copying the row from SGID.META.AGOLItems to the AGOLItems_shelved table in AGOL and changing the AGOL_ITEM_ID field in SGID.META.AGOLItems to shelved or some other note.
  • Deprecated AGOL items can be backed up on Google Drive > AGRC Projects > SGID > deprecated layers > agol_sgid_layers.
• Remove Farm from AGOL connection (name, completed: 2025/00/00)
• Update the SGID Index fields: "arcGisOnline", "openSgid", "openSgidTableName"
• Update relevant gis.utah.gov product pages (including downloadMetadata.ts and public/_redirects) (name, completed: 2025/00/00)
• Update SGID.META.AGOLItems table (name, completed: 2025/00/00)
  • cut and paste row to AGOLItems_shelved table if shelving (see below)
  • set the AGOL_ITEM_ID field to hosted by <agency> for Farm from AGOL
  • set the AGOL_ITEM_ID field to exclude from AGOL to not publish to ArcGIS Online
• Delete Google Drive data (name, completed: 2025/00/00)
• Remove row from SGID.META.ChangeDetection (name, completed: 2025/00/00)
• Remove data from forklift hashing and receiving (name, completed: 2025/00/00)
• Remove row from data/hashed/changedetection.gdb/TableHashes (name, completed: 2025/00/00)
• Remove data from record series with archives (@eneemann, completed: 2025/00/00)

Shelve/Static

Choose one based on situation.

• Upload to UtahAGRC/AGRC_Shelved folder in AGOL (New shelved item not already in AGOL) (name, completed: 2025/00/00)
• Move existing AGOL item to AGRC_Shelved AGOL folder (shelving an item already in AGOL) (name, completed: 2025/00/00)
• Upload to appropriate UtahAGRC/{SGID Category} folder in AGOL (for static datasets) (name, completed: 2025/00/00)

Add record to table.

• Add record to AGOLItems_shelved table in ArcGIS Online with shelved or static in the CATEGORY field (name, 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.

• Remove data from Open SGID (name on 2025/00/00)
• sgid-index (@steveoh on 2025/00/00)
• Auditor sets appropriate shelved/static/Deprecated information (@jacobdadams on 2025/00/00)

Are there service dependencies

• Are clients querying this data with the UGRC API search endpoint? This dashboard may be helpful.
• Notify Don Jackson (don.jackson1 at motorolasolutions.com) if the data is in the Next-Generation 911 Motorola Aware Map? (@mhchou on 2025/00/00)
• Does any other application depend on this data?
  • dependency 1

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)