Merge up Planet removal, getting params from SSM (UV changes already in, GH is confused)#256
Merged
dmannarino merged 20 commits intoproductionfrom Jan 7, 2026
Merged
Merge up Planet removal, getting params from SSM (UV changes already in, GH is confused)#256dmannarino merged 20 commits intoproductionfrom
dmannarino merged 20 commits intoproductionfrom
Conversation
* Docker compose changes to work better with local Data API * Re-lock deps. I think it's the titiler upgrade that fixes colormaps.
Integrated disturbance alerts are generated within the
gfw_integrated_alerts Data API dataset, but we have a distinct route
name to access them in titiler. Within a particular
gfw_integrated_alerts version, the COGs are named intdist.tif and
intdistintensity.tif (distinguishing them from the integrated alerts
COGs called default.tif and intensity.tif).
I am not generating the integrated disturbance COGs automatically yet,
but version v20251001 has the COGs generated, so a url like:
http://localhost:8088/gfw_integrated_dist_alerts/v20251001/dynamic/{z}/{x}/{y}.png?start_date=2025-08-13&alert_confidence=high&render_type=true_color"
works
Creating titiler route/handler for integrated disturbance alerts.
Was previously testing with rasters/COGs created under gfw_integrated_alerts.
…oint. (#234) I moved most of the forest filter code down to the Alerts class, so it can be shared between DistAlerts and gfw_integrated_dist_alerts.py (which uses IntegratedAlerts). It could also be used by other Alerts subclasses. Dist alerts no longer needs a create_mask method, since it is fully handled by the Alerts create_mask method. Dockerfile change is just to add ssh-client to test docker, which makes it easier for me to test dev changes on Linux with production DB.
* Merge to production: Bump deps, gfw_integrated_dist_alerts endpoint (#232) * (Bump deps to) allow colormaps to work (#228) * Create titiler route/handler for integrated disturbance alerts. * Switch to using actual gfw_integrated_dist_alerts dataset * GTC-3357 Add forest filter to gfw_integrated_dist_alerts titiler endpoint. * add ssh-client to test docker, which makes it easier for me to test dev changes on Linux with production DB.
* Convert Dockerfile to multistage * Switch to uv * Bump Python version to 3.11 * Bump PostgreSQL version to match deployed * Update setup script for uv * Export values via SSM (#235)
…245) * Add tests that will break upon upgrading to Python 3.11 without code changes * Make code compatible with Python 3.11
* Move tile_x/y/zoom assignment out of with statement, since needed below. * Make sure to apply tree cover filter for encoded int-dist alerts * Fix doc comments on create_mask(), based on Solomon's comments.
* Convert to uv from pipenv * Switch to ubuntu based image * Bump PostgreSQL version to match deployed * Bump Python to 3.11
This reverts commit 07632e7.
solomon-negusse
approved these changes
Jan 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull request checklist
Please check if your PR fulfills the following requirements:
Pull request type
Please check the type of change your PR introduces:
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this introduce a breaking change?
Other information