geo
geo copied to clipboard
georust
Geospatial primitives and algorithms for Rust
Remove `geo-types` patches in `Cargo.toml` files, so that `geo-types` is now completelly separated from the rest of the code. This should be reverted once geo-types 0.8+ is released. This PR...
- [ ] I agree to follow the project's [code of conduct](https://github.com/georust/geo/blob/main/CODE_OF_CONDUCT.md). - [ ] I added an entry to `CHANGES.md` if knowledge of this change could be valuable to...
At the moment, our simplification algorithms work like this: If we want retained indices: 1. We create a vec of [wrapper structs](https://github.com/georust/geo/blob/main/geo/src/algorithm/simplify.rs#L8-L15) of indices and coordinates by [iterating over the...
UPDATE: most of this pr has been moved to #797 (all of `geo-types` changes). 797 should be merged and published first. This PR will need to be updated once 797...
This PR includes #798, which should be merged before this one --- * BREAKING: Remove deprecated functions on the `Geometry`: * `into_point` - Switch to `std::convert::TryInto` * `into_line_string` - Switch...
Is this possible with docs.rs? For example, we can't currently see the `Transform` algorithm on docs.rs/geo
- https://github.com/georust/geo/issues/527 - [Video](https://www.youtube.com/watch?v=N00_yt4_kNQ) TODO: - [ ] Check validity of outputted geometries - [ ] Include NaN values - [ ] Fuzz against the geos and gdal crates
Currently geo implements rotation and translations, but misses others like `scale` (see static methods on [JTS AffineTransformation](https://locationtech.github.io/jts/javadoc/org/locationtech/jts/geom/util/AffineTransformation.html#method.summary)). Does it make sense to port the entire AffineTransformation as a single matrix-based...
As noted in #541, there is an interest in making the concave hull algorithm converge with the implementation in concaveman. Since, the current implementation diverges by avoiding the use of...
Related: #706 #708 None of the other geo-types have equivalent methods. There are alternatives in `geo::algorithms` that are more uniformly implemented: * `LineString::coords`: Alternative is `CoordsIter::coords_iter` (although that returns an...
