Bump rust library to 0.2 (#99)

Author: kylebarron

CHANGELOG.md

@@ -0,0 +1,51 @@
+# Changelog
+
+**This is the changelog for the core Rust library**. There's a [separate changelog](./python/CHANGELOG.md) for the Python bindings.
+
+## [0.2.0] - 2025-01-06
+
+### Breaking
+
+- Use u32 and u16 in public API for num_items and node_size by @kylebarron in https://github.com/kylebarron/geo-index/pull/69
+- Rename `OwnedRTree` to `RTree` and `OwnedKDTree` to `KDTree` by @kylebarron in https://github.com/kylebarron/geo-index/pull/81
+
+### Bug fixes
+
+- Fix `intersection_candidates_with_other_tree` by @kylebarron in https://github.com/kylebarron/geo-index/pull/51
+- Improve precision in f64 to f32 box cast by @kylebarron in https://github.com/kylebarron/geo-index/pull/76
+- Avoid panic for rtree with one item by @kylebarron in https://github.com/kylebarron/geo-index/pull/91
+
+### New Features
+
+- Implement nearest neighbor searches on RTree by @kylebarron in https://github.com/kylebarron/geo-index/pull/79
+- Add geo-traits integration by @kylebarron in https://github.com/kylebarron/geo-index/pull/71
+  - Implement RectTrait for Node by @kylebarron in https://github.com/kylebarron/geo-index/pull/75
+- KDTree traversal by @kylebarron in https://github.com/kylebarron/geo-index/pull/96
+- Expose RTreeMetadata & KDTreeMetadata (allowing you to infer the memory usage a tree would incur) by @kylebarron in https://github.com/kylebarron/geo-index/pull/77
+
+### Performance
+
+- Remove unnecessary `Cow` in kdtree trait by @kylebarron in https://github.com/kylebarron/geo-index/pull/72
+
+### Documentation
+
+- Use "immutable" over "static" wording in docs by @kylebarron in https://github.com/kylebarron/geo-index/pull/70
+- improved rtree & kdtree docs by @kylebarron in https://github.com/kylebarron/geo-index/pull/93
+
+### What's Changed
+
+- Don't panic for accessing level out of bounds by @kylebarron in https://github.com/kylebarron/geo-index/pull/49
+
+### New Contributors
+
+- @H-Plus-Time made their first contribution in https://github.com/kylebarron/geo-index/pull/55
+
+**Full Changelog**: https://github.com/kylebarron/geo-index/compare/v0.1.1...v0.2.0
+
+## [0.1.1] - 2024-01-14
+
+- Updated benchmarks in documentation by @kylebarron in #27
+
+## [0.1.0] - 2024-01-14
+
+- Initial public release.

Cargo.lock

@@ -1,6 +1,6 @@
 [package]
 name = "geo-index"
-version = "0.1.1"
+version = "0.2.0"
 authors = ["Kyle Barron <kylebarron2@gmail.com>"]
 edition = "2021"
 rust-version = "1.75"

Cargo.toml

@@ -32,7 +32,7 @@ A Rust crate for packed, immutable, zero-copy spatial indexes.
 - Queries return insertion indexes into the input set, so you must manage your own collections.
 - Only the set of coordinate types that exist in JavaScript are allowed, to maintain FFI compatibility with the reference JavaScript implementations. Hence this does not support other types like `u64`.
 
-## Alternatives
+## Alternative crates
 
 - [`rstar`](https://github.com/georust/rstar): a dynamic RTree implementation.
 - [`kdtree`](https://github.com/mrhooray/kdtree-rs): a dynamic KDTree implementation.

README.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## Unreleased
+
+- Raise runtime warning for debug builds by @kylebarron in https://github.com/kylebarron/geo-index/pull/63
+- RTree Buffer protocol, python binding tests by @H-Plus-Time in https://github.com/kylebarron/geo-index/pull/55
+- Python: Return boxes as arrow from RTree by @kylebarron in https://github.com/kylebarron/geo-index/pull/89
+- Update Python API & implement RTree partitions, nearest neighbor search by @kylebarron in https://github.com/kylebarron/geo-index/pull/87
+- Update python bindings by @kylebarron in https://github.com/kylebarron/geo-index/pull/78
+- Add `__repr__` to Python classes by @kylebarron in https://github.com/kylebarron/geo-index/pull/84
+- Python docs website & improved rtree & kdtree docs by @kylebarron in https://github.com/kylebarron/geo-index/pull/93
+
 ## [0.1.0] - 2024-03-26
 
 - Initial public release.

python/CHANGELOG.md

@@ -1,4 +1,5 @@
-//! Data structures to hold indices that may be either `u16` or `u32` to save space.
+//! Data structures to hold insertion and internal tree indices that may be either `u16` or `u32`
+//! to save space.
 
 use bytemuck::{cast_slice, cast_slice_mut};