Closed gregbunce closed 3 years ago
@stdavis this data passed the sweeper checks and is ready to be brought into Internal (forklift pallet). let me know if you have any questions.
If the schema is the same or a superset of what we are serving we do not need to deal with porter.
rule 1. no one cares
check | status |
---|---|
@gregbunce has completed 7 out of 12 tasks | :no_entry: |
@steveoh has completed 3 out of 6 tasks | :no_entry: |
@stdavis has completed 2 out of 3 tasks | :no_entry: |
@jacobdadams has completed 0 out of 1 tasks | :no_entry: |
check | status |
---|---|
internal sgid | :no_entry: |
meta table | |
- item id | :no_entry: |
- item name | :no_entry: |
stewardship | :no_entry: Did not find Transportation.UDOTRoutesALRS in the worksheet |
@stdavis this data passed the sweeper checks and is ready to be brought into Internal (forklift pallet). let me know if you have any questions.
Forklift doesn't create datasets in SGID. It only updates existing ones. @ZachBeck would need to load it first. I'll add a task to the issue description for it.
This checked box "- [x] Internal SGID (wait until sweeper checks pass)" made me think that you had already added it to internal SGID.
This checked box "- [x] Internal SGID (wait until sweeper checks pass)" made me think that you had already added it to internal SGID.
The verification heading is where you should look to know what has been added where.
meeting update
This has been loaded into internal-sgid but the permissions have not been shared out to the internal user. The source UDOT data had a stale OBJECTID
field that I deleted and a field named SUB_ROUTE_
that I renamed to SUB_ROUTE
. I don't know if that will foul things up on the forklift side of things. There was no metadata that came with the shapefile download either.
While I agree that the dangling underscore should go and is probably not necessary, unless it's a reserved sql term, it might cause more issue with the import than it is worth to remove it.
We can still test forklift with the owner connection right?
Too late, I put the underscore back
This PR will complete the wiring up of forklift for this issue: https://github.com/agrc/warehouse/pull/125
check | status |
---|---|
@gregbunce has completed 7 out of 12 tasks | :no_entry: |
@steveoh has completed 3 out of 6 tasks | :no_entry: |
@ZachBeck has completed 0 out of 1 tasks | :no_entry: |
@stdavis has completed 2 out of 3 tasks | :no_entry: |
@jacobdadams has completed 0 out of 1 tasks | :no_entry: |
check | status |
---|---|
internal sgid | :no_entry: |
meta table | |
- item id | :no_entry: |
- item name | :no_entry: |
stewardship | :no_entry: Did not find Transportation.UDOTRoutesALRS in the worksheet |
blocked by SGID sharing.
this dataset now as the appropriate sgid sharing permissions. it should be ready for the open sgid db.
Has your triage finished @gregbunce?
yup, i'm just working on getting udot to add a little more metadata and also i need to update our data page (tomorrow). but, that should be everything on my end.
check | status |
---|---|
@gregbunce has completed 10 out of 12 tasks | :no_entry: |
@steveoh has completed 4 out of 6 tasks | :no_entry: |
stdavis has completed 2 out of 2 tasks | :+1: |
@jacobdadams has completed 0 out of 1 tasks | :no_entry: |
check | status |
---|---|
internal sgid | :+1: |
meta table | |
- item id | :no_entry: |
- item name | :no_entry: |
- geometry type | :no_entry: |
stewardship | |
- Description | :+1: |
- Data Source | :+1: |
- Website URL | :+1: |
- Data Type | :+1: |
- Endpoint | :+1: |
this dataset now as the appropriate sgid sharing permissions. it should be ready for the open sgid db.
We're missing all the meta table information. Will you add that so the other automation will run.
the metatable has been updated. i'm not sure if i added the correct agol name - i removed the parenthesis b/c that's what i had to do to get data page to work . if that doesn't work, I'll include the parens.
You could try to quote the string containing the parens to get them in the website? But the open data url does not contain the parens so I think you used the correct text for the meta table. Did you also set the geometry type?
Hey @gregbunce. Next time put something like hosted by UDOT
in the AGOL_ITEM_ID
field for data that we farm from AGOL. If there's a valid guid in that field, then forklift attempts to update it. It threw an error in this case because the item is owned by UDOT. I've updated the table to look like this:
Yes, @steveoh the geometry type is in there.
thanks, @stdavis. and yup, @steveoh i did set the geom type.
check | status |
---|---|
@gregbunce has completed 11 out of 13 tasks | :no_entry: |
@steveoh has completed 4 out of 5 tasks | :no_entry: |
stdavis has completed 2 out of 2 tasks | :+1: |
@jacobdadams has completed 0 out of 1 tasks | :no_entry: |
check | status |
---|---|
internal sgid | Exception was thrown! |
meta table | Exception was thrown! |
stewardship | |
- Description | :+1: |
- Data Source | :+1: |
- Website URL | :+1: |
- Data Type | :+1: |
- Endpoint | :+1: |
kelli bacon and i are meeting Feb 3rd to iron out the final details for the wording of the metadata and the agrc transportation page's lrs section
check | status |
---|---|
@gregbunce has completed 11 out of 13 tasks | :no_entry: |
@steveoh has completed 4 out of 5 tasks | :no_entry: |
stdavis has completed 2 out of 2 tasks | :+1: |
@jacobdadams has completed 0 out of 1 tasks | :no_entry: |
check | status |
---|---|
internal sgid | :+1: |
meta table | |
- item id | :+1: |
- item name | :+1: |
- geometry type | :+1: |
open sgid | :+1: |
open data | :+1: |
arcgis online | :no_entry: |
stewardship | |
- Description | :+1: |
- Data Source | :+1: |
- Website URL | :+1: |
- Data Type | :+1: |
- Endpoint | :+1: |
Summary
This new hosted feature layer will replace the existing SGID.Transportation.UDOTRoutes_LRS layer, as described in porter issue 104. This new layer represents UDOT's new Advanced LRS system. UDOT will maintain the feature service and AGRC will point SGID Open Data users to their service. Additionally, AGRC will host this layer in Internal and Open SGID. Note: This is one of three existing SGID layers that we will be replacing using this method (LRS, mile point measures, freeway exit locations).
Triage
We are introducing data
The data should be added at our earliest convince (after @gregbunce runs sweeper) to the following areas
The data is high quality
The data should propagate automatically to
SGID.META.ChangeDetection
(@steveoh)References to the data need to be manually added to
SGID.META.AGOLItems
(@stdavis) ~- [ ]AGOLItems_shelved
metatable (AGOL version of the metatable for anystatic
orshelved
items)~We have verified the data is live
01/05/2021
)01/05/2021
)01/05/2021
) ~- [ ]SGID.META.AGOLItems
(``)~SGID.META.ChangeDetection
(@steveoh on ``) ~- [ ] agol-validator items (@jacobdadams on )~Notification