Repository navigation
Prepare for semi-distributed model gauge rename and update dependencies (v1.1.1) - #11
Merged
Merged
Conversation
…es (v1.1.1) - Refresh the gauge cache early when over 25% of current gauges have no cached model (at most hourly), so thresholds and forecasts return quickly after the hybas_ to subhybas_ gauge ID rename - Document the Flood Hub model change in the README - Update @tak-ps/etl, eslint and typescript-eslint; add a minimatch override and drop the stale fast-xml-parser override so npm audit reports 0 vulnerabilities
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Google Flood Hub is switching to a semi-distributed riverine model in late November 2026. Gauge IDs change from
hybas_<id>tosubhybas_<id>, some gauges move between low and high confidence, and data is only available for the new gauges from the launch date.The ETL treats gauge IDs as opaque and needs no configuration change. The one gap is the gauge cache: thresholds are cached per gauge ID, so after the rename the Thresholds and Forecast sections of the remarks would be empty for up to
GAUGE_REFRESH_HOURS(24 h by default).Changes
gaugeIdoutput schema description.@tak-ps/etlto 10.26.0,eslintto 10.14.0 andtypescript-eslintto 8.72.1, withpackage.jsonranges raised to match.fast-xml-parseroverride (the package is no longer in the tree) with aminimatch^11.0.1override for GHSA-g3hv-75wg-m249.npm auditwent from 17 vulnerabilities (3 high inundici, 14 moderate fromminimatch) to 0.Not included
@tak-ps/etl11.0.0: changes the published output schema format and targets CloudTAK v14.typescript7.0.2: not supported bytypescript-eslint(requires below 6.1.0).Verification
npm run lint,npm run buildandnpm testpass (5 tests).npm auditandnpm audit --omit=devreport 0 vulnerabilities.Notes
floodhub-<gaugeId>) change. Markers for the old gauges should expire at their stale time. This has not been confirmed in CloudTAK.minimatchoverride can be removed onceeslintandtypescript-eslintrequire a patched release.