Hi!
I'm using the CARTO H3_POLYFILL function in BigQuery. I'm noticing that for some input geometries, I'm not getting all the hex returned that I would expect when comparing to the Python H3 implementation.
In these examples, the geometry is valid and I'm trying to polyfill it at resolution 10. In the Python H3 binding these hex are returned, but in the CARTO BigQuery binding they are not. This is using the standard H3_POLYFILL function which I believe uses the hex centroid to determine containment.
Does anyone have any ideas on why this might be please?
Hi!
I'm using the CARTO H3_POLYFILL function in BigQuery. I'm noticing that for some input geometries, I'm not getting all the hex returned that I would expect when comparing to the Python H3 implementation.
In these examples, the geometry is valid and I'm trying to polyfill it at resolution 10. In the Python H3 binding these hex are returned, but in the CARTO BigQuery binding they are not. This is using the standard H3_POLYFILL function which I believe uses the hex centroid to determine containment.
Does anyone have any ideas on why this might be please?