# GeoPolars
<p align="center">
<img src="static/logo.svg" height="300px" alt="geopolars"></a>
</p>
<p align="center">
<em>
Geospatial DataFrames for Rust and Python
</em>
</p>
<p align="center">
<a href="https://github.com/geopolars/geopolars/actions?query=workflow%3ARust" target="_blank">
<img src="https://github.com/geopolars/geopolars/workflows/Rust/badge.svg" alt="Test">
</a>
<a href="https://pypi.org/project/geopolars" target="_blank">
<img src="https://img.shields.io/pypi/v/geopolars?color=%2334D058&label=PyPI%20version" alt="PyPI Package version">
</a>
<a href="https://github.com/geopolars/geopolars/blob/master/LICENSE" target="_blank">
<img src="https://img.shields.io/github/license/geopolars/geopolars.svg" alt="Downloads">
</a>
</p>
## Summary
GeoPolars extends the [Polars][polars] DataFrame library for use with geospatial data.
- Uses [GeoArrow][geo-arrow-spec] as the internal memory model.
- Written in Rust
- Bindings to Python (and WebAssembly in the future)
- Multithreading capable
At this point, GeoPolars is a **prototype** and should not be considered production-ready.
## Use from..
### Rust
GeoPolars is [published to crates.io](https://crates.io/crates/geopolars) under the name `geopolars`.
Documentation is available at [docs.rs/geopolars](https://docs.rs/geopolars).
### Python
An early alpha (`v0.1.0-alpha.3`) is published to PyPI:
```
pip install --pre geopolars
```
The publishing processs includes binary wheels for many platforms, so it should be easy to install, without needing to compile the underlying Rust code from source.
A documentation website has been started but is not yet hosted online.
### WebAssembly
Polars itself does not yet exist in WebAssembly, though there has been discussion about adding bindings for it. The long-term goal of GeoPolars is to have a WebAssembly API as well.
## Comparison with GeoPandas
Imitation is the sincerest form of flattery! GeoPandas — and its underlying libraries of `shapely` and `GEOS` — is an incredible production-ready tool.
GeoPolars is nowhere near the functionality or stability of GeoPandas, but competition is good and, due to its pure-Rust core, GeoPolars will be much easier to use in WebAssembly.
## Future work
The biggest pieces of future work are:
- Store geometries in the efficient Arrow-native format, rather than as WKB buffers (as the prototype currently does). This is blocked on Polars, which doesn't currently support Arrow `FixedSizeList` data types, but they've recently [expressed openness](https://github.com/pola-rs/polars/issues/4014#issuecomment-1212376538) to adding minimal `FixedSizeList` support.
- Enable `georust/geo` algorithms to access Arrow data with zero copy. The prototype currently copies WKB geometries into `geo` structs on each geometry operation, which is expensive.
This is blocked on adding support to the `geo` library for geometry access traits, which is a large undertaking. See [georust/geo/discussions/838](https://github.com/georust/geo/discussions/838). I've started exploration on this
- Implement GeoArrow extension types for seamless handling of CRS metadata in Rust, rather than in the Python wrapper.
[polars]: https://github.com/pola-rs/polars
[geo-arrow-spec]: https://github.com/geopandas/geo-arrow-spec