Skip to content

Commit e51f026

Browse files
tweaks to readme
1 parent 47b27cb commit e51f026

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -47,15 +47,15 @@ result = sf.lazy().filter(pl.col("population") > 100_000).range_query(-10.0, 35.
4747

4848
During my undergrad research, I saw firsthand how spatial dataframe tooling could use performance improvements.
4949

50-
The driving motivator behind creating this library was to provide the optimizations of relational DBs (query planning, indexing, etc) in a fast spatial dataframe interface that abstracts away these complexities for users.
50+
The driving motivator behind creating this library was to provide the optimizations of relational DBs (query planning, indexing, etc) in a fast, Polars-like interface meant for in-memory spatial work.
5151

52-
Edit [June 19 2026]: Apache Sedona released a cool Python DataFrame API. There are similarities between their API and this tool but some key differences are (1) this query planner interacts with Polars rather than just being an input source and (2) this uses a cost-model approch to dynamic indexing.
52+
Edit [June 19 2026]: Apache SedonaDB released a cool Python DataFrame API. There are similarities between their API and this tool but some key differences are that this library uses (1) a Polars-native query engine and (2) a cost model that decides whether and how to index.
5353

5454

5555
| | PyCanopy | GeoPandas | DuckDB | SedonaDB | Spatial Polars |
5656
|:--|:--------:|:---------:|:------:|:--------:|:--------------:|
5757
| Polars-native API ||||||
58-
| Spatial query planner (reorder, fuse, pushdown) ||||||
58+
| Spatial query planner (reorder, pushdown, etc) ||||||
5959
| Index vs scan decided by cost model ||||||
6060
| Dynamic index selection ||||||
6161

0 commit comments

Comments
 (0)