Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIX: SpadeTriangulation was not actually configurable #1123

Merged
merged 1 commit into from
Dec 7, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions geo/CHANGES.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,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

Expand Down
2 changes: 1 addition & 1 deletion geo/src/algorithm/triangulate_spade.rs
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand Down