Overview

Fixes #7874.

Prevent a zero-area MultiPolygon feature from aborting choropleth rendering. When centroid selection cannot find a positive-area sub-polygon, the feature now receives the existing [NaN, NaN] centroid sentinel. Its geometry remains available for rendering, while valid sibling features continue through extraction.

Root cause and user impact

The MultiPolygon centroid path initialized maxArea to zero and only selected sub-polygons whose area was strictly greater. If every sub-polygon had zero area, the selected polygon remained undefined and was passed to Turf's centroid helper, causing an uncaught TypeError that stopped the entire plot.

The guard is limited to that no-positive-area case. Centroid calculation for valid Polygon and MultiPolygon features is unchanged.

Validation

• Added a regression test using the issue's two-distinct-vertex degenerate ring alongside a valid polygon.
• Verified the regression test failed before the source change with Cannot read properties of undefined (reading 'type').
• npm run test-jasmine -- lib_geo_location_utils choropleth --nowatch --report-spec — 37/37 passed (Chromium-based Edge via CHROME_BIN).
• npm run test-syntax
• npm run lint
• git diff --check