Kyle Barron

Note that here it would be ideal if we implemented our _own_ `BinaryArrayType` trait, because then we could implement it _both_ on upstream types like `BinaryArray` _and_ our own types...

This can be added to the `geoarrow-cast` module.

I updated this PR and wrote new documentation. @gadomski @paleolimbot if you'd be interested in giving a review I'd appreciate it!

This PR could additionally use tests with bounding box covering columns, but that data doesn't yet exist in geoarrow-data and the write side of the `geoparquet` crate doesn't yet support...

GeoJSON is probably the weakest reader we have (aside from PostGIS), and essentially the only reader left where we have a pure-geozero implementation. Ideally we'd be able to reuse [arrow-json](https://docs.rs/arrow-json/latest/arrow_json/),...

I would've ideally liked to provide a selection of a few geocoder providers that users could choose from, because the actual geocoding API calls should be able to integrate into...

Ideally I would choose the top N geocoding providers by usage (not sure what those are), including at least one free one, if possible. I don't currently have a way...

It compiles fine in 1.2.0; fails with 1.2.1.

``` RUSTFLAGS="-Zinline-mir=no" CFLAGS=-fno-PIC RUSTUP_TOOLCHAIN=nightly \ maturin build \ --release \ --no-default-features \ -o dist \ -m geoarrow-io/Cargo.toml \ --target wasm32-unknown-emscripten \ -i python3.11 ``` this still fails with 1.2.1. ```...

@felixpalmer was saying that a general solution here is to turn off depth testing ``` parameters: {depthCompare: 'never'} ``` https://luma.gl/docs/api-reference/core/parameters#depth-test-parameters