NASA-IMPACT / NASA-IMPACT/veda-odd

ODD PI 25.4 Objective 1: 🎬 TiTiler-CMR is production ready

Open
#197 3 comments 0 reactions 2 assignees View on GitHub

@hrodmn is already working on this.

Since Jun 24, 2025.

pi-25.4-objective
Dominant language
No language data
Stars
5
Forks
0
Avg merge
4d 19h
Merged PRs (30d)
3

Description

Motivation

TiTiler-CMR has the potential to be a powerful tool to visualize data catalogued in CMR, enabling visualization as soon as data is delivered to CMR with zero data preprocessing. However, given TiTiler-CMR tiles the raw data, performance could be improved.

Description

The VEDA ODD will do a performance assessment to understand bottlenecks and then come up with a plan improving performance.

Acceptance Criteria
  • Performance assessment
  • 1 performance improvement implemented
  • Production instance of titiler-cmr (dependency on data services team)
Sub-tasks
  • Establish mailing list for titiler-cmr users (Worldview, GIBS, VEDA instances) and document / share a process for announcing new deployments + features
  • Integrate titiler-cmr timeseries into the VEDA UI (dependency on UI team)
  • Complete performance assessment and implement improvements:
    • Edge caching via Cloudfront
    • Share findings with other VEDA teams
  • Coordinate a production deployment: Staging and production deployment of titiler-cmr for phased deployment of new features (MCP deployment would require data services)
  • Work with data services on a monitoring solution (we should be alerted when something like access breaks)
  • Support datasets (HLS in Worldview, MiCASA (GHG), TROPESS (AQ), and GPM IMERG (Earthdata VEDA))
  • As needed, document how to integrate a dataset into VEDA UI using titiler-cmr. Include details of how to report issues.
  • Stretch - Interactive tool to help troubleshoot datasets

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.