The format=timeseries option silently returns incomplete data when the response exceeds user limits.
Testing revealed that the gzip-compressed timeseries format response is only slightly smaller than the gzip-compressed json format response (200kb vs. 250kb for one month).
Grouping of substantial amounts of json-formatted data into timeseries format can be accomplished client-side with relatively minor performance impact -- <60ms on a powerful machine for one quarter of nwm30-medium-range forecasts.
Based on this information, the plan is to drop the format=timeseries option for the time being. If needed in the future it can be re-implemented with built-in pagination to match other formats.
The
format=timeseriesoption silently returns incomplete data when the response exceeds user limits.Testing revealed that the gzip-compressed timeseries format response is only slightly smaller than the gzip-compressed json format response (200kb vs. 250kb for one month).
Grouping of substantial amounts of json-formatted data into timeseries format can be accomplished client-side with relatively minor performance impact -- <60ms on a powerful machine for one quarter of nwm30-medium-range forecasts.
Based on this information, the plan is to drop the
format=timeseriesoption for the time being. If needed in the future it can be re-implemented with built-in pagination to match other formats.