Closed gregbunce closed 4 months ago
check | status |
---|---|
@DenisePeterson has completed 7 out of 11 tasks | :no_entry: |
@stdavis has completed 0 out of 4 tasks | :no_entry: |
@steveoh has completed 1 out of 4 tasks | :no_entry: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
@gregbunce has completed 1 out of 2 tasks | :no_entry: |
@rkelson has completed 0 out of 1 tasks | :no_entry: |
check | status |
---|---|
internal sgid | :no_entry: |
meta table | :+1: |
stewardship | |
- deprecation issue link | :no_entry: |
@gregbunce this layer is in the base maps. Will there be a replacement layer in Internal?
check | status |
---|---|
@DenisePeterson has completed 7 out of 11 tasks | :no_entry: |
@stdavis has completed 0 out of 4 tasks | :no_entry: |
@steveoh has completed 1 out of 4 tasks | :no_entry: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
@gregbunce has completed 1 out of 2 tasks | :no_entry: |
@rkelson has completed 0 out of 1 tasks | :no_entry: |
check | status |
---|---|
internal sgid | :no_entry: |
meta table | :+1: |
stewardship | |
- deprecation issue link | :no_entry: |
@gregbunce what is your plan for the base maps if you delete this feature class from Internal?
check | status |
---|---|
DenisePeterson has completed 11 out of 11 tasks | :+1: |
@stdavis has completed 0 out of 4 tasks | :no_entry: |
@steveoh has completed 1 out of 4 tasks | :no_entry: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
@gregbunce has completed 1 out of 2 tasks | :no_entry: |
rkelson has completed 1 out of 1 tasks | :+1: |
check | status |
---|---|
internal sgid | :+1: |
meta table | :+1: |
stewardship | |
- deprecation issue link | :+1: |
@ZachBeck do you want the new data to be imported into the internal or are you okay to pull it from the udot service?
Internal please.
@stdavis how would you like us to proceed with wiring up udot's freeway exit web service to internal sgid? a new porter issue, or is that overkill?
or is the Honeycomb fgdb updater (base maps) able to work with udot's web service (aka: maybe we don't need to bring it into Internal)? this layer is used in the base maps
Honeycomb will pick it up once I add it to the Pro project.
If the only reason we want it in internal is for the base maps, we can come up with a different way to put it in the base maps. I'll work with Zach to get it added to the honeycomb forklift stuff and just get it directly from the service.
check | status |
---|---|
DenisePeterson has completed 11 out of 11 tasks | :+1: |
@stdavis has completed 0 out of 4 tasks | :no_entry: |
@steveoh has completed 1 out of 4 tasks | :no_entry: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
@gregbunce has completed 1 out of 2 tasks | :no_entry: |
rkelson has completed 1 out of 1 tasks | :+1: |
check | status |
---|---|
internal sgid | :+1: |
meta table | :+1: |
stewardship | |
- deprecation issue link | :+1: |
check | status |
---|---|
DenisePeterson has completed 11 out of 11 tasks | :+1: |
stdavis has completed 2 out of 2 tasks | :+1: |
steveoh has completed 4 out of 4 tasks | :+1: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
@gregbunce has completed 1 out of 2 tasks | :no_entry: |
rkelson has completed 1 out of 1 tasks | :+1: |
check | status |
---|---|
internal sgid | :+1: |
meta table | :+1: |
stewardship | |
- deprecation issue link | :+1: |
I'm in the process of verifying this data is not linked to any 911 dispatch center or Motorola maps. I have a feeling it is.
I'm in the process of verifying this data is not linked to any 911 dispatch center or Motorola maps. I have a feeling it is.
All the other tasks have been completed already so it's pretty much gone. What is the plan?
Okay, I already fixed those. Let's close this out.
thanks everyone.
Summary
A short summary of the situation.
We are no longer getting updates from UDOT for this Internal SGID layer. It has been replaced by a UDOT-managed web service. The gis.utah.gov transportation data page points users to the latest and greatest UDOT data, which is also searchable/findable in the UGRC Open SGID (Hub) site.
At this point, we just need to clean up Internal SGID by removing/deprecating this outdated layer.
Migration Guide
All users should be pointing to UDOT's newest web service for this layer.
Action items
name
with their github@name
.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:
SGID.META.AGOLItems
table (@DenisePeterson, completed:2024/01/25
)2024/01/25
)2024/01/25
)2024/01/25
)Authoritative
field tod
inSGID.META.AGOLItems
to automatically set theDeprecated
AGOL flag. Allow thed
to persist through one run of Auditor - currently, Auditor runs daily at 5:00am (@DenisePeterson, completed:2024/01/25
)SGID.META.AGOLItems
table. This will trigger the removal of this item in Open SGID (@DenisePeterson, completed:2024/01/26
)2024/01/26
)Hard Delete
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.
2024/02/08
) ~- [ ] Deprecated database layers should be backed up on Google Drive > AGRC Projects > SGID > deprecated layers > internal_db_sgid_layers (name, completed:2023/00/00
).~2024/02/08
)AGOL_ITEM_ID
field inSGID.META.AGOLItems
to something other than an Item ID and manaually changing the sharing settings (remove the item from all SGID groups, remove Public sharing),SGID.META.AGOLItems
to theAGOLItems_shelved
table in AGOL and changing theAGOL_ITEM_ID
field inSGID.META.AGOLItems
toshelved
or some other note.~2023/00/00
)~ (not applicable) ~- [ ] Update relevant gis.utah.gov data pages (name, completed:2023/00/00
)~Deprecated
field of the Stewardship record (@DenisePeterson, completed:2024/02/08
)SGID.META.AGOLItems
table (@DenisePeterson, completed:2024/02/08
)AGOLItems_shelved
table if shelving (see below)AGOL_ITEM_ID
field tohosted by <agency>
for Farm from AGOLAGOL_ITEM_ID
field toexclude from AGOL
to not publish to ArcGIS Online ~- [ ] Delete Google Drive data (name, completed:2023/00/00
)~ ~- [ ] Remove row fromSGID.META.ChangeDetection
(@stdavis, completed:2024/00/00
)~ (was not present)2024/02/20
)data/hashed/changedetection.gdb/TableHashes
(@stdavis, completed:2024/02/20
)Shelve/Static
Choose one based on situation.
UtahAGRC/AGRC_Shelved
folder in AGOL (New shelved item not already in AGOL) (name, completed:2023/00/00
)AGRC_Shelved
AGOL folder (shelving an item already in AGOL) (name, completed:2023/00/00
)UtahAGRC/{SGID Category}
folder in AGOL (forstatic
datasets) (name, completed:2023/00/00
)Add record to table.
AGOLItems_shelved
table in ArcGIS Online withshelved
orstatic
in theCATEGORY
field (name, completed:2023/00/00
):robot: Automation validation
name
with their github@name
.2020/01/01
when the task is verified.2024/02/20
)2024/02/20
)Deprecated
information (@jacobdadams on2024/01/26
)Are there service dependencies
2024/02/27
)Notification
Group Task Assignments