Unsupported polygon targeting

Some platforms accept only circles or native geo IDs, not arbitrary polygons; a custom trade-area polygon submitted directly is rejected or silently approximated by the platform's own simplification.

Class

Case to account for

Affects

2 conversions

Detection

platform.polygonSupport=false while the target list contains raw polygon geometry.

Mitigation

Pre-convert polygons to the platform's supported primitive (circle set or native ID crosswalk) rather than submit raw rings

Verify the platform's rendered target against the intended polygon post-submission

Affected conversions

H3exact polygon

OPEN

H3platform-native IDs

OPEN