Merge pull request #1123 from georust/mkirk/configurable-spade

FIX: SpadeTriangulation was not actually configurable
georust · Dec 7, 2023 · fd7e7b1 · fd7e7b1
2 parents 76ad2a3 + b81b5a9
commit fd7e7b1
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 1 deletion.
diff --git a/geo/CHANGES.md b/geo/CHANGES.md
@@ -7,6 +7,8 @@
   * <https://github.com/georust/geo/pull/1119>
 * Add `LineStringSegmentizeHaversine` trait as a an alternative to `LineStringSegmentize` for geographic coordinates.
   * <https://github.com/georust/geo/pull/1107>
+* Make `SpadeTriangulationConfig` actually configurable
+  * <https://github.com/georust/geo/pull/1123>
 
 ## 0.27.0
 

diff --git a/geo/src/algorithm/triangulate_spade.rs b/geo/src/algorithm/triangulate_spade.rs
@@ -19,7 +19,7 @@ use crate::{Centroid, Contains};
 pub struct SpadeTriangulationConfig<T: SpadeTriangulationFloat> {
     /// Coordinates within this radius are snapped to the same position. For any two `Coords` there's
     /// no real way to influence the decision when choosing the snapper and the snappee
-    snap_radius: T,
+    pub snap_radius: T,
 }
 
 impl<T> Default for SpadeTriangulationConfig<T>