You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Snowflake, carto.PLACEKEY_TOH3 occasionally returns incorrect and invalid H3s for valid placekeys.
As an example the placekey "@8f3-tw4-evz" maps to the H3 index "8a44516b382ffff" (this can be confirmed with the placekey api) which is a valid index, however carto.PLACEKEY_TOH3 returns the H3 "8a44516b2fc3fff" which is an invalid index.
This issue appears to be quite rare (appearing roughly on the order of 1 every 100k - 1M placekeys)
The text was updated successfully, but these errors were encountered:
On Snowflake, carto.PLACEKEY_TOH3 occasionally returns incorrect and invalid H3s for valid placekeys.
As an example the placekey "@8f3-tw4-evz" maps to the H3 index "8a44516b382ffff" (this can be confirmed with the placekey api) which is a valid index, however carto.PLACEKEY_TOH3 returns the H3 "8a44516b2fc3fff" which is an invalid index.
This issue appears to be quite rare (appearing roughly on the order of 1 every 100k - 1M placekeys)
The text was updated successfully, but these errors were encountered: