From b81b5a94a7f06f940afb7e66b87519e92b8271ae Mon Sep 17 00:00:00 2001 From: Michael Kirk Date: Wed, 6 Dec 2023 08:15:24 -0800 Subject: [PATCH] FIX: SpadeTriangulation was not actually configurable --- geo/CHANGES.md | 2 ++ geo/src/algorithm/triangulate_spade.rs | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/geo/CHANGES.md b/geo/CHANGES.md index 99469f57d..98a7cd421 100644 --- a/geo/CHANGES.md +++ b/geo/CHANGES.md @@ -5,6 +5,8 @@ * * Add `LineStringSegmentizeHaversine` trait as a an alternative to `LineStringSegmentize` for geographic coordinates. * +* Make `SpadeTriangulationConfig` actually configurable + * ## 0.27.0 diff --git a/geo/src/algorithm/triangulate_spade.rs b/geo/src/algorithm/triangulate_spade.rs index fb38ff4f1..544c53963 100644 --- 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 { /// 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 Default for SpadeTriangulationConfig