Closed gregbunce closed 4 months ago
Did we want to keep this in opensgid and internal for base maps etc or wipe it all out?
Good point on the basemaps. I should have made that more clear. Yup, the replacement data for this dataset is also in the Internal SGID named, Transportation.UDOT_MileReferencePosts. The basemaps, etc should point to that layer.
I’ll update the content above to clarify that.
Thanks.
check | status |
---|---|
@DenisePeterson has completed 0 out of 9 tasks | :no_entry: |
gregbunce has completed 6 out of 6 tasks | :+1: |
@steveoh has completed 0 out of 5 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 0 out of 1 tasks | :no_entry: |
check | status |
---|---|
@DenisePeterson has completed 0 out of 9 tasks | :no_entry: |
gregbunce has completed 6 out of 6 tasks | :+1: |
@steveoh has completed 0 out of 5 tasks | :no_entry: |
@stdavis has completed 0 out of 1 tasks | :no_entry: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
@rkelson has completed 0 out of 1 tasks | :no_entry: |
check | status |
---|---|
@DenisePeterson has completed 5 out of 9 tasks | :no_entry: |
gregbunce has completed 6 out of 6 tasks | :+1: |
@stdavis has completed 0 out of 3 tasks | :no_entry: |
@steveoh has completed 2 out of 3 tasks | :no_entry: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
@rkelson has completed 0 out of 1 tasks | :no_entry: |
check | status |
---|---|
@DenisePeterson has completed 5 out of 9 tasks | :no_entry: |
gregbunce has completed 6 out of 6 tasks | :+1: |
@stdavis has completed 0 out of 3 tasks | :no_entry: |
@steveoh has completed 2 out of 3 tasks | :no_entry: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
@rkelson has completed 0 out of 1 tasks | :no_entry: |
check | status |
---|---|
internal sgid | :no_entry: |
meta table | :+1: |
stewardship | |
- deprecation issue link | :+1: |
@ZachBeck Should I add a task for you to update the base maps before this dataset is removed from internal? Or is it something that a GIS-monkey like me could do?
Either way.... I think this layer uses a python label expression so it might be a little more involved than repointing to a new data source.
check | status |
---|---|
DenisePeterson has completed 9 out of 9 tasks | :+1: |
gregbunce has completed 6 out of 6 tasks | :+1: |
@stdavis has completed 0 out of 3 tasks | :no_entry: |
@steveoh has completed 2 out of 3 tasks | :no_entry: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
@rkelson has completed 0 out of 1 tasks | :no_entry: |
check | status |
---|---|
internal sgid | :+1: |
meta table | :+1: |
stewardship | |
- deprecation issue link | :+1: |
check | status |
---|---|
DenisePeterson has completed 9 out of 9 tasks | :+1: |
gregbunce has completed 6 out of 6 tasks | :+1: |
@stdavis has completed 0 out of 3 tasks | :no_entry: |
steveoh has completed 3 out of 3 tasks | :+1: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
@ZachBeck has completed 0 out of 1 tasks | :no_entry: |
@rkelson has completed 0 out of 1 tasks | :no_entry: |
check | status |
---|---|
internal sgid | :+1: |
meta table | :+1: |
stewardship | |
- deprecation issue link | :+1: |
check | status |
---|---|
DenisePeterson has completed 9 out of 9 tasks | :+1: |
gregbunce has completed 6 out of 6 tasks | :+1: |
stdavis has completed 3 out of 3 tasks | :+1: |
steveoh has completed 3 out of 3 tasks | :+1: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
@ZachBeck has completed 0 out of 1 tasks | :no_entry: |
@rkelson has completed 0 out of 1 tasks | :no_entry: |
check | status |
---|---|
internal sgid | :+1: |
meta table | :+1: |
stewardship | |
- deprecation issue link | :+1: |
check | status |
---|---|
DenisePeterson has completed 9 out of 9 tasks | :+1: |
gregbunce has completed 6 out of 6 tasks | :+1: |
stdavis has completed 3 out of 3 tasks | :+1: |
steveoh has completed 3 out of 3 tasks | :+1: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
ZachBeck has completed 1 out of 1 tasks | :+1: |
rkelson has completed 1 out of 1 tasks | :+1: |
check | status |
---|---|
internal sgid | :+1: |
meta table | :+1: |
stewardship | |
- deprecation issue link | :+1: |
Summary
A short summary of the situation. This layer has been deprecated by UDOT and has been replaced by the following service: Physical Location of Reference Post (RP) Open Data. UGRC's Transportation page points users to this new service.
The replacement data for this dataset is also in the Internal SGID named, Transportation.UDOT_MileReferencePosts. The basemaps, etc should point to that layer.
Migration Guide
Users should be using UDOT's Physical Location of Reference Post (RP) Open Data as a replacement or Transportation.UDOT_MileReferencePosts who is in Internal SGID.
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/03
)2024/01/03
)2024/01/03
)2023/12/22
)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 (@gregbunce, completed:2023/12/22
)SGID.META.AGOLItems
table. This will trigger the removal of this item in Open SGID (@DenisePeterson, completed:2024/01/03
)2024/01/03
)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/01/18
)2024/01/18
).2024/01/18
)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.~ ~- 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:2023/00/00
)~2023/12/21
)Deprecated
field of the Stewardship record (@gregbunce, completed:2023/12/21
)SGID.META.AGOLItems
table (@DenisePeterson, completed:2024/01/18
) ~- cut and paste row toAGOLItems_shelved
table if shelving (see below)~ ~- set theAGOL_ITEM_ID
field tohosted by <agency>
for Farm from AGOL~ ~- set theAGOL_ITEM_ID
field toexclude from AGOL
to not publish to ArcGIS Online~ ~- [ ] Delete Google Drive data (name, completed:2023/00/00
)~SGID.META.ChangeDetection
(@stdavis, completed:2023/00/00
)2024/01/29
)data/hashed/changedetection.gdb/TableHashes
(@stdavis, completed:2024/01/29
)Shelve/Static
Choose one based on situation.
~- [ ] Upload to
UtahAGRC/AGRC_Shelved
folder in AGOL (New shelved item not already in AGOL) (name, completed:2023/00/00
)~ ~- [ ] Move existing AGOL item toAGRC_Shelved
AGOL folder (shelving an item already in AGOL) (name, completed:2023/00/00
)~ ~- [ ] Upload to appropriateUtahAGRC/{SGID Category}
folder in AGOL (forstatic
datasets) (name, completed:2023/00/00
)~Add record to table.
~- [ ] Add record to
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/01/22
)2024/01/22
)Deprecated
information (@jacobdadams on2023/12/23
)Are there service dependencies
2023/12/022
)2024/01/30
)Notification
Group Task Assignments