chore(tiles): stop exporting the frozen incident bundles - #76
Merged
Conversation
report.incident has been frozen since 2026-03-03 (2,756 rows, 157 days), so every nightly GPKG export of incident and its three aggregations has been a byte-identical copy. The aggregations are pure derivations of report.incident anyway, and ~700 daily snapshots already cover the whole period incidents were being filed. enabled=false makes processOne take the both-flags-off early return from #53: no ogr2ogr dump, no queue job, no log line. The map layers are unaffected — Martin serves them from maplayer.incident*(z,x,y), verified still returning 200 after the flip. facade_scan deliberately stays enabled: it is live data (new samples in Aug 2026), none of its attributes exist in analysis_full, and the planned delete-and-reimport of all 5,200+ QuickScan records would otherwise wipe every trace of the pre-reimport state. analysis_full stays enabled as the static-model history itself. Applied to prod 2026-08-07. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Follows #75, which turned tile generation off but deliberately left
enabled/upload_dataseton so the GPKG exports kept feeding the static-model history. For the incident layers that history has nothing left to record.Why these four
report.incidentis frozen: 2,756 rows, newestcreate_date2026-03-03 — 157 days ago. Intake stopped when the KCAF loket and municipal portals moved off our infra, so every nightly export since March has been a byte-identical copy.report.incidentjoined to the geocoder areas — reconstructable from the incident export, and from the table itself.enabled=falsemakesprocessOnetake the both-flags-off early return from #53 — no ogr2ogr dump, no queue job, no log line. Verified after applying that Martin still serves all four layers (200 onincident,incident_district,incident_municipality,incident_neighborhood).Why
facade_scanis NOT includedanalysis_full— I checked the column list: 33 columns of risk model, none ofskewed_parallel_facade,skewed_perpendicular_facade,facade_type,settlement_speed,facade_scan_risk,risk,priority. The export is the only archived record of them.Costs 1.2 MB and ~17s a night.
analysis_fullstays enabled as the static-model history itself.Result
Nightly
process_mapsetis nowanalysis_full(~9.5 min) +facade_scan(~17s), and nothing else.Applied to prod 2026-08-07.
🤖 Generated with Claude Code