SGID Index Validation Issues

[github-actions]

Validation errors have been detected in the SGID Index. This issue will be used to track the resolution of these issues.

GitHub Actions should post a comment with the details shortly...

To rerun the validation script, add a new comment that starts with the following text: /validate-sgid-index.

[github-actions]

SGID Index Validation

2024-05-15 17:05:18

Script Output

using ci credentials
loading spreadsheet
building duplicate lookups
checking 526 rows

total errors: 32
updated 1 rows

Validation Errors

displayName	id	Error
DSHW Solid Haz Waste Oil Facilities	b5a5f4ac-8a7a-4d84-9a72-63233a00681e	No "productPage" or "itemId"
DWQNPDES Dischargers	8e5fd42a-0963-455f-a642-677c25c664e1	No "productPage" or "itemId"
Earthquake Epicenters 1850 To 2016	48957ec8-87d4-417b-8b4c-21735ccf186f	inActionUrl: failed request with error: fetch failed
Earthquake Epicenters Mining Induced 1928 To 2016	280499f8-04d1-46d4-b058-af4893704af1	inActionUrl: failed request with error: fetch failed
Epicenters Modern	9693ca92-f099-4222-bc14-f8fe7e969a47	inActionUrl: failed request with error: fetch failed
Hillshade base map	b7b0ab2b-2526-49fe-9960-22845f278ef1	itemId hub request error: Request failed with status code 404 Not Found
Landslide Compilation Debris Flow Paths	1ecdf0d0-24a5-4cbb-905f-74fd67373484	inActionUrl: failed request with error: fetch failed
Landslide Compilation Polygons	5e17df07-3217-4388-b56b-3813c164e7be	inActionUrl: failed request with error: fetch failed
Landslide Compilation Scarps	c782b968-2512-42c2-afaa-889fbfd55996	inActionUrl: failed request with error: fetch failed
Landslide Inventory Mapped Areas	a161f05a-23ce-4c75-8025-5ab68653d55b	inActionUrl: failed request with error: fetch failed
Landslide Inventory Polygons	b74acad5-8a72-46f1-8fab-b886145dc1a9	inActionUrl: failed request with error: fetch failed
NFHL Hazard Areas	833d52f3-ad52-499f-a95e-64fcdf84a956	itemId hub request error: Request failed with status code 404 Not Found
Oil Gas Wells Paths	9cee6dde-92e7-4477-9679-89145249d29a	message: Cannot read properties of undefined (reading 'split') stack: TypeError: Cannot read properties of undefined (reading 'split') at itemId (file:///home/runner/work/gis.utah.gov/gis.utah.gov/scripts/validate-sgid-index.mjs:181:51) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.all (index 3) at async file:///home/runner/work/gis.utah.gov/gis.utah.gov/scripts/validate-sgid-index.mjs:302:28
Overlay Base Map	aacb1b96-d6a7-4e5b-8b14-a8bc9a0ca8d5	itemId hub request error: Request failed with status code 404 Not Found
Pony Express	1f62a035-edf1-436a-869b-6c280fe5253c	No "productPage" or "itemId"
Potential Liquefaction Wasatch Front	26fba16f-d55b-4dce-ae92-9e566fc20988	inActionUrl: failed request with error: fetch failed
Quaternary Faults	d2786ded-8fb5-4d4b-87d0-1015e238520d	inActionUrl: failed request with error: fetch failed
Shallow Ground Water	42bbbd72-1fd2-4ceb-9c14-c4be105b8ebc	inActionUrl: failed request with error: fetch failed
Signal Cabinets	998934d6-1023-4c52-b559-3d45fa0129b1	productPage: open data item not found
Signal Poles	5b4313a2-a194-45ae-a290-94208b0960c6	productPage: open data item not found
SMS Safety Index	8d8c0e70-9989-4527-af42-49d57f86a7f7	No "productPage" or "itemId"
SMS Severe Crashes Per Mile	d7f54d25-8781-4162-8666-690b3eb6688a	No "productPage" or "itemId"
State Boundary Snap Points	6c80a6ba-8202-411f-b5f0-abb9905ecef3	No "productPage" or "itemId"
State Highway Power Pedestals	7f78a085-ea29-4fd9-81ce-7914077bb0b5	itemId hub request error: Request failed with status code 404 Not Found
Terrain Base Map	30a04fba-45a4-4b3e-a836-09254fbb631b	itemId hub request error: Request failed with status code 404 Not Found
Topo Base Map	87768706-e43c-4003-8021-83c2be5f4db0	itemId hub request error: Request failed with status code 404 Not Found
UDOT Map Neighbor Counties	05a07006-c9b6-45ad-93f2-7b2a8738ad71	No "productPage" or "itemId"
UDOT Map State Parks	477f9da7-6b6c-4e1d-9f68-80aa5e3f4a7f	No "productPage" or "itemId"
UHP Dispatch	3af36877-8bd8-4a0a-bb03-a43ad8b76fea	No "productPage" or "itemId"
Walls Located Along Utah State Highways	6b75f772-11c7-4a4a-b45a-3bcf92945849	productPage: open data item not found
Watershed Restoration Initiative Treatment Areas	bfa1fa62-19b9-4315-aad1-54a23cb7968e	No "productPage" or "itemId"
Watershed Restoration Initiative Treatment Areas	bfa1fa62-19b9-4315-aad1-54a23cb7968e	inActionUrl: failed request with error: fetch failed

[gregbunce]

I attempted to fix the 3 drinking water issues (the first 3 records in this issue)

please verify that I used the correct fields/syntax in the sgid index sheet (rows 108 - 110)

[stdavis]

/validate-sgid-index

[stdavis]

please verify that I used the correct fields/syntax in the sgid index sheet (rows 108 - 110)

It looks good to me. I reran the script and those issues went away.

BTW - These fields are auto-populated by the validation script:

hubName | hubOrganization | serverHost | serverServiceName | serverLayerId

So you don't need to worry about filling those in. I added notes to their headers about this.

Also, you are welcome to rerun the validation script manually by adding a comment to this issue that starts with the following text:

/validate-sgid-index

[gregbunce]

Great, thanks scott. this is super handy for managing and maintaining the sgid index sheet.

for my understanding, when we run /validate-sgid-index the newest results overwrite the previous results in this issue? aka: this issue (2712) persists as the issue relating to sgid index issue?

[steveoh]

Yes that is correct. We can close this issue and have a new one created when it get's too cluttered.

[stdavis]

/validate-sgid-index

[stdavis]

FYI - It looks like the validation workflow that is scheduled to run nightly is getting rate-limited. It appears to be this same issue: JasonEtco/create-an-issue#142. I submitted a support ticket to GitHub to see if they will give me more specifics of what the problem is. But for now, it appears to work if you trigger it manually. I'm going to close this issue and see if creating a new issue allows it to run successfully tonight.