2026-05-18

2026-05-18

Catalog Endpoint Planning, BEST Endpoint(question), Field Issues

  • Catalog (#/issues/1717)
  • Ensure proper doc coverage
  • CONCERN: Changes to client source to ensure it matches new catalog. Do we break existing endpoints? Covering data types that do not have catalog but be sure to plan backwards compat for TS and Locations
  • /catalog/locations and /catalog/timeseries can stay as-is or could be updated as well.
  • /authoritative vs /catalog/authoritative : Part of Composite TS work?
  • BEST is in the Standard Naming convention from 2017

  • [Upward Reporting] : A2W portion of the schema defines an elevation for the project (CMA is the website, It is what A2W uses as a point of reference). Be sure to define/ack

  • POSSIBLE: Endpoint exists in CDA now that lets you get the CMA defined timeseries for a location (Work being done in CWMSVue for this now to replace CMA website)
  • ENDPOINT COULD EXIST!
  • https://github.com/USACE/cwms-data-api/pull/1030
  • Feedback welcome, how should this return? Existing response can be seen in "files changed"
  • What shape should data be returned as/data structure
  • Work for CWMSVue
  • Brought attention to https://github.com/USACE/cwms-data-api/issues/1731