H3 polygons work at resolution 8 but become empty at resolution 9+
Environment
- ArcGIS Pro 3.6
- ArcGIS API for Python 2.4.2
- DuckDB 1.5.4
- DuckDB Spatial Extension
- DuckDB H3 Extension
- Python Notebook in ArcGIS Pro
Description
I found what appears to be a bug in GeoAccessor.set_geometry() when converting H3 cell boundary WKT geometries.
Using the same workflow, H3 polygons at resolutions 0–8 are converted correctly and displayed on the map. However, polygons at resolutions 9–15 are converted to empty geometries.
The feature class is created successfully, but no geometry is displayed on the map.
Output
Resolution 8 (Works)
{'rings': [[[31.134037, 29.98722], [31.139995, 29.98765], [31.143417, 29.983361], [31.140882, 29.978643], [31.134924, 29.978213], [31.131502, 29.982502], [31.134037, 29.98722]]], 'spatialReference': {'wkid': 4326, 'latestWkid': 4326}}
<class 'arcgis.geometry._types.Polygon'>Resolution 10 (Fails)
{'rings': [], 'spatialReference': {'wkid': 4326, 'latestWkid': 4326}}
<class 'arcgis.geometry._types.Polygon'>The same geometries are successfully parsed using arcpy.FromWKT() and are reported as valid by DuckDB ST_IsValid(), suggesting the issue occurs during the GeoAccessor.set_geometry() conversion process.
I've attached two minimal reproducible examples. The only change is the H3 resolution (8 vs 10), yet one works and the other returns an empty polygon geometry.
