Skip to content

Merge up Planet removal, getting params from SSM (UV changes already in, GH is confused)#256

Merged
dmannarino merged 20 commits intoproductionfrom
staging
Jan 7, 2026
Merged

Merge up Planet removal, getting params from SSM (UV changes already in, GH is confused)#256
dmannarino merged 20 commits intoproductionfrom
staging

Conversation

@dmannarino
Copy link
Member

Pull request checklist

Please check if your PR fulfills the following requirements:

  • Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your master!
  • Make sure you are making a pull request against the develop branch (left side). Also you should start your branch off our develop.
  • Check the commit's or even all commits' message styles matches our requested structure.
  • Check your code additions will fail neither code linting checks nor unit test.

Pull request type

Please check the type of change your PR introduces:

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this introduce a breaking change?

  • Yes
  • No

Other information

dmannarino and others added 20 commits October 6, 2025 06:28
* 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
@dmannarino dmannarino changed the title Merge up Planet removal, getting params from SSM (UV changes already in, GH seems confused) Merge up Planet removal, getting params from SSM (UV changes already in, GH is confused) Jan 7, 2026
@solomon-negusse solomon-negusse self-requested a review January 7, 2026 15:52
@dmannarino dmannarino merged commit f620454 into production Jan 7, 2026
4 of 5 checks passed
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.

3 participants