Skip to content

To Do List #1

Description

@needham-michael
  • Write detailed instructions for each application stage
  • Management of large local files
    • Allow the user to specify (via the config.yml file) whether raw satellite granules should be retained or deleted after the specified fields have been downloaded, extracted, and reprojected to the updated coordinate system. The default should be to delete the granule files
    • Also could specify an alternate location (e.g., E:/ vs C:/ drives) to store raw satellite granules.
  • Day-by-day area exclusion
    • Allow the user to drop a pin on the map to exclude pixels within the specified county from being included in the final burn mask for the given day. This can be implemented easily using rioxarray and the .rio.clip(geom) method.
    • Evaluate how difficult it would be to allow the user to draw a polygon on the map to exclude specific areas
  • Automatic year-to-date burn mask calculation
  • Rename both Point Draw Tool instances to Burned Pixel and Unburned Pixel or similar
    • Rely on hv.render(hv_obj) to access the underlying object (e.g., as fig), and update the tool.description within fig.toolbar.tools for the tools
  • Revisit landcover mask
    • Expand water cover masks to address lake edge issues

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions