forked from UN-SPIDER/burn-severity-mapping-EO
-
Notifications
You must be signed in to change notification settings - Fork 0
Issues: SchmidtDSE/burn-severity-mapping-poc
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Should probably define a class for batch analysis and fetch
#34
opened Mar 4, 2024 by
github-actions
bot
Think about best practice for reducing time dimension pre/post fire
#30
opened Feb 27, 2024 by
github-actions
bot
Move to sentry to environment variable if we keep sentry
#28
opened Feb 13, 2024 by
github-actions
bot
self-referential endpoint, will be solved by refactoring out titiler and/or making fully static
#24
opened Feb 2, 2024 by
github-actions
bot
This is the same logic as in upload_cogs. Refactor to avoid duplication
#23
opened Feb 2, 2024 by
github-actions
bot
Use Tofu Output to construct hardocded cog and geojson urls (in case we change s3 bucket name)
#21
opened Jan 29, 2024 by
github-actions
bot
Harcoded project string and others - now that tofu outputs are setup up, make more general
#20
opened Jan 29, 2024 by
github-actions
bot
v1 frontend prototype
enhancement
New feature or request
question
Further information is requested
#10
opened Jan 23, 2024 by
GondekNP
Generalize Sentinel2Client to accept any CRS
question
Further information is requested
smelly
Working but hacky, hardcoded, and/or confusing
#7
opened Jan 22, 2024 by
github-actions
bot
Decide on / implement cloud tasks or other async batch
enhancement
New feature or request
#5
opened Jan 22, 2024 by
github-actions
bot
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.