search

stuckyb / gcdl

6 stars 2 forks source link

vector datasets #12

Open HeatherSavoy-USDA opened 2 years ago

HeatherSavoy-USDA commented 2 years ago

Some datasets will be vector instead of raster, e.g. county-level data. Temporal characteristics will be the same as raster data, but not all spatial characteristics, e.g. grid size. So the catalog should be flexible enough to support that.

We will need to handle processing both directions for users if they want to merge the two types: rasterizing polygons or summarizing raster cells to polygons.

stuckyb commented 2 years ago

See also #7.

melaniekamm commented 2 years ago

I think we should be cautious that this software is not trying to replicate all basic GIS functionality. As far as I understand, the primary goal is to reduce replication of datasets on the HPC moreso than being a one-stop-shop for pre-processing spatial data. Or is offering harmonization functionality also a top priority?

At minimum, I vote we prioritize giving users access to additional datasets before building out all the harmonization tools. It would be helpful to ask potential users which harmonization tools they want and would use most frequently. This wasn't included in the survey results we have.

Melanie

On Fri, Dec 17, 2021, 8:46 PM stuckyb @.***> wrote:

See also #7 https://github.com/stuckyb/gcdl/issues/7.

— Reply to this email directly, view it on GitHub https://github.com/stuckyb/gcdl/issues/12#issuecomment-997121329, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD2YM5FV5IS66SE7RE7WYMDURPRX5ANCNFSM5KJ6CYCA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you are subscribed to this thread.Message ID: @.***>

stuckyb commented 2 years ago

That is a great point, @melaniekamm. I agree this is a project that could easily get stuck in "feature creep" mode. Identifying the core set of high-priority features will be critical to ensure we can actually get something into production.

BrianStucky-USDA commented 12 months ago

Revisiting this issue now, I think @HeatherSavoy-USDA was correct. There are important datasets we need to support that are vector, which means we will need to expand our dataset class to support that, as well as processing in both directions (raster -> vector, vector -> raster). Not being able to support vector datasets is currently a significant limitation of the GeoCDL.