Issues

• CHARTER transform generated duplicate item_id.

  IFRCGo/pystac-monty#256 · Filter by author Rup-Narayan-Rajbanshi opened on Sep 25, 2026
  3

  

• USGS: shakemap/dyfi/losspager/etc. items only attach one asset, dropping most of the source's content files

  IFRCGo/pystac-monty#241 · Filter by author emmanuelmathot opened on Sep 15, 2026

• Duplicated collection self-href logic across common.py, cems.py, charter.py

  IFRCGo/pystac-monty#234 · Filter by author emmanuelmathot opened on Sep 10, 2026

• Stac-geoparquet export

  IFRCGo/pystac-monty#222 · Filter by author wrynearson opened on Sep 9, 2026
  

• Missing back-links on response/impact items in CEMS and Charter transformers

  IFRCGo/pystac-monty#209 · Filter by author Rup-Narayan-Rajbanshi opened on Aug 31, 2026
  1

  

• USGS PAGER alert-derived records: clarify why alerts become impacts and fix inconsistent metadata

  bugquestion
  Bug

  IFRCGo/pystac-monty#200 · Filter by author arunissun opened on Aug 13, 2026
  2

  

• USGS unit in impact details in impact item

  IFRCGo/pystac-monty#199 · Filter by author ranjan-stha opened on Aug 13, 2026
  3

• GDACS impact items deviate from the now-documented mapping

  IFRCGo/pystac-monty#188 · Filter by author emmanuelmathot opened on Aug 3, 2026
  2

  

• Close the implementation ↔ analysis feedback loop with monty-stac-extension (repo overhaul, mirrors monty-stac-extension#62)

  IFRCGo/pystac-monty#180 · Filter by author emmanuelmathot opened on Jul 28, 2026

• Standardize STAC link media types on application/geo+json for Item targets (follow-up to #156)

  IFRCGo/pystac-monty#165 · Filter by author emmanuelmathot opened on Jul 14, 2026