Zacharias Knudsen

Thanks for the PR, I'll try looking into it. Could it be related to the way h3 is built? ``` cmake \ -DCMAKE_C_FLAGS=-fPIC \ -DBUILD_TESTING=OFF \ -DENABLE_COVERAGE=OFF \ -DENABLE_DOCS=OFF \...

Release `v3.6.3` includes `-DCMAKE_BUILD_TYPE=Release` which should improve performance. Still `objdump -D h3.so | grep _square` shows three callsites, so I'll keep this issue open until we figure out how to...

We should also keep an eye on https://github.com/uber/h3/pull/360.

Solved by #75

Would you prefer only considering input as omitted on `undefined` then? If so I can quickly update the PR accordingly.

Hi stefano! Have you tried increasing the resolution parameter for polygon_to_cells to something higher than 8? What does polygon `way` look like?

As a temporary workaround you can use `network-only` fetchPolicy for queries that are affected by this issue.

According to [apollo-client#5659](https://github.com/apollographql/apollo-client/issues/5659) this was fixed in `3.0.0-beta.24`

For inspiration there exists https://github.com/sikanhe/gqtx which is a thin layer over `graphql-js` which provides type-safety. Also @ephemer appears to have a similar wrapping in the works here: https://github.com/graphql/graphql-js/issues/2104#issuecomment-707779154

It is not a problem with GiST generally, but a problem with my initial implementation. Specifically I need to come up with good algorithms for `penalty` and `picksplit` (see https://www.postgresql.org/docs/current/gist-extensibility.html)....