While testing the implementation of the support for the new LRTS interval identifiers within cwms-data-access, (appending Local to the interval instead of prepending ~) it was discovered that endpoints that handle data associated with these new intervals are still using the previous format.

The methods currently known to have this behavior are:

• Binary TimeSeries: storage: The storage method is failing to associate binary data with the timeseries ID. Data is not being stored into the AT_TSV_BINARY table. There could be an underlying issue with the association between the new and old interval id: calls into CWMS_TEXT.RETRIEVE_TS_BINARY(). Recent testing suggests this issue occurs for all irregular timeseries, further investigation is underway. See TS Binary storage of irregular time series does not work #28 for details on this issue, as it applies to all irregular time series data.
• ForecastSpec: retrieval: uses custom query against the AV_FCST_SPEC, AV_FCST_LOCATION, and AV_FCST_TIME_SERIES views. Tests show that this issue persists when using the CWMS_FCST_PACKAGE.call_RETRIEVE_FCST_SPEC procedure in CDA.

ForecastSpec has been verified to return the legacy format (e.g. ~1Hour instead of 1HourLocal) when the USE_NEW_LRTS_ID_FORMAT session variable is set to level 6 - which should require the new format input and provide it on output.