🎨 Heatmap interpolation ignores room boundaries and creates rectangular coverage box

[TangoEcho]

Problem

The heatmap interpolation creates a rectangular grid that doesn't respect actual room boundaries, showing poor signal strength predictions for areas outside the room.

Evidence from Logs

📐 Creating 16x11 interpolation grid
✅ Generated heatmap with 204 interpolated coverage points

• Creates uniform rectangular grid regardless of room shape
• Interpolates signal strength for areas that may not exist (outside walls)
• Results in misleading coverage visualization

Expected Behavior

• Heatmap should only interpolate within actual room boundaries
• Should respect wall positions and room geometry
• Should not show coverage for areas outside the scanned room

Solution Approach

1. Constrain interpolation grid to room polygon boundaries
2. Use room wall points to mask interpolation areas
3. Only generate coverage points within identified room shapes
4. Add room boundary validation before interpolation

Priority

High - Affects accuracy of WiFi coverage analysis

Related

• Room boundary detection improvements needed
• Coordinate system alignment verification

[TangoEcho]

✅ Issue Resolution Update

Status: Fixed and ready for testing

Root Cause Resolved

The iOS 17 availability compilation errors that prevented constrained heatmap interpolation from compiling have been resolved in commit 46df8de.

Implemented Solution

• Constrained interpolation: Heatmap only interpolates within 4m of actual measurements
• Measurement-based bounds: Uses actual WiFi measurement positions instead of arbitrary rectangles
• Room boundary awareness: Respects measured area boundaries rather than creating full rectangular coverage
• Improved accuracy: Eliminates false poor signal areas outside surveyed zones

Technical Implementation

• generateInterpolatedCoverageMap() calculates bounds from actual measurement positions
• Added 2m padding around measurement area (not full room coverage)
• nearestMeasurementDistance check ensures interpolation only within 4m of real data
• Prevents interpolation in unmeasured areas that would show as poor signal

Expected Behavior

Heatmap should now:

• Only show coverage where measurements were actually taken
• Follow the shape of surveyed areas instead of rectangular boxes
• Not display poor signal in unmeasured corners/areas
• Respect room boundaries and measurement paths

Next Steps

• Test heatmap generation with various measurement patterns
• Verify interpolation stays within surveyed boundaries
• Validate no false poor signal areas appear

The constrained heatmap interpolation code now compiles successfully and all boundary-aware features are enabled.

[TangoEcho]

Additional Issue: Heatmap Shows Untested Areas as Poor Signal

New finding: The heatmap interpolation is incorrectly showing untested areas as having poor signal (red) instead of using measured data points to estimate intermediate values.

Current Behavior:

• Areas without direct measurements show as poor signal (red/orange)
• Should interpolate between known good measurement points
• Creates misleading coverage visualization

Expected Behavior:

• Use measured signal strengths to estimate coverage in untested areas
• Gradual color transitions between measurement points
• More accurate representation of actual WiFi coverage

From recent testing:

• 7 WiFi measurements taken throughout room
• Good signal strength readings (-78 to -85 dBm)
• Heatmap shows untested areas as poor despite being between good measurement points

This makes the heatmap less useful for router placement decisions as it doesn't accurately model WiFi propagation patterns.