So it doesn’t need to be re-computed. In the ClickHouse example, 3 zoom levels are added in 70 seconds. They can now be aggregated in SELECT statements that should last for milliseconds.
H3 is new and few datasets will include it, let alone at the Zoom levels your application might be interested in.
Why
materializethe zoom level constant ingeoToH3?So it doesn’t need to be re-computed. In the ClickHouse example, 3 zoom levels are added in 70 seconds. They can now be aggregated in SELECT statements that should last for milliseconds.
H3 is new and few datasets will include it, let alone at the Zoom levels your application might be interested in.
Sorry, I meant why call
materialize(7)insidegeoToH3to prevent ClickHouse evaluating 7 as a constant for that expression?When I first started working with H3s in ClickHouse there was an issue that was worked around by using the materialize call https://github.com/ClickHouse/ClickHouse/issues/35670