Skip to content
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

Update USFS_GTAC_TreeMap_v2016.js #994

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

abhinavshrestha-41
Copy link

Added code in the example to let users clip TreeMap bands to an area of interest (AOI). AOI can be from TIGER data set (shown as example) or can be a user-defined GEE asset. Clipped raster will be exported to user-defined Google Cloud Storage bucket.

Added code snippet to let users clip TreeMap bands to an area of interest (AOI). AOI can be from TIGER data set (shown as example) or can be a user-defined GEE asset. Clipped raster will be exported to user-defined Google Cloud Storage bucket.
Copy link
Collaborator

@simonff simonff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Abhinav - thank you for the suggestion! We generally try to keep these examples simple, without running exports.

What's the motivation behind this change?

@abhinavshrestha-41
Copy link
Author

Hello!

I'm a federal contractor with RCR, working with the USFS and the TreeMap team. We're publishing this dataset for a cooperator. We wanted to provide an example of how to export data for her users, since currently, GEE is the easiest place for users to clip, zip, and ship the dataset. We can comment out the export example if you'd prefer it didn't auto-run.

Or let us know if we should find an alternate place to share this code snippet. The example just seemed like an easily accessible place to share this possibility with users-- many of whom are desktop GIS folks with minimal scripting skills

@simonff
Copy link
Collaborator

simonff commented Jun 1, 2024

Hi Abhinav - I think putting a fairly specific usage pattern into the already-long example script might be too confusing, as we generally don't do this - the dataset example is intended to show what the dataset is, not to replace the whole workflow.

But I appreciate your concern about trying to simplify user experience - EE can indeed be difficult to get used to. If you have an alternate place for publishing this script (a github repo?), we can link to it from the example code or the dataset description.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants