-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add skyshade to raster.utah.gov from Jake's hard drive #324
Comments
Discover or AGOL are the places we have available to serve this sort of data. I assume it would be tiled? |
Sorry, I should have explained more. The skyshade is a pure raster product, like a hillshade but with a significantly longer processing time (it took about a week to run on my old office desktop). The output raster needs to be styled to a user's preference, so pre-rendering wouldn't work. The original output was something like 24gb, but I was able to get it down to about 4gb in the process of dividing it into the same sized chunks we currently serve the underlying 10m DEM in. At this size, a single download wouldn't be too much of a burden on users, so maybe adding it as a file-only AGOL item and linking to it from a datapage would be the better course of action. |
Yeah or GCS is a cheap option for downloads. So, what would be shown in raster.utah.gov? |
If we went the raster.utah.gov route, it'd look the same as when you go to download the USGS DEMs- a bunch of tiles that would link to zip files in GCS. I'm intrigued by the idea of hosting it as an item in AGOL. I'd have to check the storage costs, but then we could expose it through Open Data as well. |
Does that mean that raster would only have a tile index? I use the preview feature but that wouldn't be available would it? |
huh, I guess I've never used the preview feature and forgot it was there. Yeah, without a served version of it somewhere, it would be like the Lidar DEMs- just an extent/tile index. Rick can correct me if I'm wrong, but I don't think it'd take too much space/cost to make a layer on Discover, but I don't know that it's worth it just for the extent. It wouldn't be terribly useful as its own layer... maybe... I mean, I guess I could do a "default" style that I like and then we could have that as a pre-canned product in discover with the raw data available for download if desired. |
I like this idea |
conductor results for tasks - 324
|
conductor results for category.internaltablename
|
Rick and I chatted about this today and came up with the following plan to move forward:
I can start step one right away, and I'll need to work with @stdavis on step two. Step three can wait until later™. |
So the hillshade would become the preview service for this new layer in raster.utah.gov? |
correct, if/when we get there. |
conductor results for tasks - 324
|
conductor results for category.internaltablename
|
conductor results for tasks - 324
|
conductor results for category.internaltablename
|
conductor results for tasks - 324
|
conductor results for category.internaltablename
|
conductor results for tasks - 324
|
Is this a stretch goal or needing a waiting or blocked label? |
Added waiting label to pause Conductor notifications since this is in the FY25 Q1 I&P Sprint 6 |
conductor results for tasks - 324
|
Summary
Proposed Readable Name: Utah SkyshadeProposed Internal Dataset Name: skyshadeProposed External Dataset Name: SkyshadeSeveral audience members at the 2024 UGIC Iron Cartographer sessions wanted access to our skyshade. This is the same dataset used in Zach's basemaps but converted to 8-bit int and chunked into the same chunks as the source USGS DEMs.
I figured a porter issue is the best way to start the discussion of getting it onto
raster.utah.gov
.The data should be available in
1 Check [x] all the areas where you expect the data to show up.
The data is of high quality
[ ] Sweeper checks have run and passed (name on2024/00/00
)[ ] The minimum requirements for metadata are populated (name on2024/00/00
)[ ] The data complies with our domain rules (name on2024/00/00
)Where is the data source
Choose one.
Action items
name
with their github@name
.Strikeout all items that do not apply.[ ] Add data to the Internal SGID (name, completed:2024/00/00
)[ ] Configure forklift for Farm from AGOL (name, completed:2024/00/00
)2024/00/00
)raster.utah.gov
sources (@rkelson, completed2024/00/00
)raster.utah.gov
(?) (@stdavis, completed2024/00/00
)2024/00/00
)2024/00/00
)[ ] Complete aSGID.META.AGOLItems
record (name, completed:2024/00/00
)AGOL_ITEM_ID
will be populated by Forklift after it publishes the new AGOL item.[ ] Complete an AGOLItems_shelved record for anystatic
orshelved
item (name, completed:2024/00/00
)2024/00/00
)🤖 Automation validation
name
with their github@name
.2020/01/01
when the task is verified.Strikeout all items that do not apply.[ ] Open SGID via cloudb (@steveoh on2024/00/00
)[ ] ArcGIS Online via forklift (@stdavis on2024/00/00
)[ ] Auditor ran successfully (@jacobdadams on2024/00/00
)[ ] SGID on ArcGIS (name on2024/00/00
)2024/00/00
)2024/00/00
)Notification
Group Task Assignments
The text was updated successfully, but these errors were encountered: