@@ -283,19 +283,14 @@ export default defineNuxtConfig({
283283 // remaining externalData adapters (market/hazard) are a cheap no-op
284284 // until configured.
285285 '15 3 * * *' : [ 'external-enrichment' ] ,
286- // Daily: rebuild geo_features from osm_local_elements (GIS WP-4) — picks
287- // up whatever OSM data changed since yesterday, whether from an admin-
288- // requested reimport (see osm-import.get.ts) or a newly enabled
289- // country's first auto-load. Also manually triggerable from /settings
290- // (geo-metrics.post.ts) to unblock the same day instead of waiting for
291- // this tick.
292- '0 2 * * *' : [ 'build-geo-features' ] ,
293- // Daily, offset 3h from build-geo-features so a full rebuild (tens of
294- // millions of osm_local_elements rows across all countries) has time to
295- // publish a new epoch first; otherwise this just reports itself skipped
296- // (see build-auction-geo-metrics.ts's latestCompleteEpoch check) and
297- // picks it up on the next tick. Precomputes the auction_geo_metrics
298- // columns the search's Umgebungsfilter (GIS WP-5) reads.
286+ // Daily: update only missing or re-geocoded auction_geo_metrics rows
287+ // against the current, complete geo_features epoch. The task's
288+ // candidate query is incremental; keeping the epoch stable means a
289+ // normal run touches only newly changed auctions, never every listing.
290+ // A full geo_features rebuild is deliberately *not* scheduled: it scans
291+ // tens of millions of OSM rows and invalidates every metrics row. Run
292+ // the explicit /settings geo-metrics rebuild chain only after an OSM
293+ // import has actually changed the source data.
299294 '0 5 * * *' : [ 'build-auction-geo-metrics' ] ,
300295 // Monthly: refresh the local EU Flood Risk Areas polygon cache (see
301296 // server/tasks/import-eu-flood-risk-cache.ts) from the EEA's published
0 commit comments