HydraIssues

Problem

HydraTAM production is configured to read hydradistrict, but its coverage check reports districts_total: 6 and districts_with_coordinates: 0. Therefore every city-to-district distance is null and the coverage layer cannot be used.

GET https://hydratam.experiencenet.com/api/v1/health is otherwise healthy (15 markets, 32 regions, 47 cities) and reports: none of the 6 districts in hydradistrict carry coordinates.

Requested change

Backfill valid WGS84 decimal-degree latitude and longitude for each existing hydradistrict district through its normal authenticated update API. Preserve all current district fields when updating; PUT replaces the resource.

Acceptance criteria

• All six existing districts have valid latitude and longitude.
• GET /api/v1/nearest in hydradistrict returns a meaningful result for a nearby test coordinate.
• HydraTAM GET /api/v1/coverage reports districts_with_coordinates > 0 with no missing-coordinate warning.
• HydraTAM coverage for Flanders returns plausible distances (for example Antwerp to bxl1 is roughly 41 km, Bruges roughly 89 km).

Scope

This is source-data remediation in hydradistrict. HydraTAM intentionally treats the integration as optional and needs no code change.