geos
geos copied to clipboard
georust
Rust bindings for GEOS
Hi, It seems that prepared geometry contains is not thread safe before run at least once. Easiest to provoke on large geometries. Not able to provoke on example in docs....
I must be doing something dumb. Rust 2018 edition, Geos v8.0.1 Code: ``` use geo::{MultiPolygon}; use std::convert::TryInto; use geos::{Geometry as GGeometry}; #[derive(Clone, Debug)] pub struct GeomAndId { pub geom: MultiPolygon,...
That would allow to prevent unnecessary runtime checks on some methods. The `GGeom` trait would contain all the common methods.
There is no point into making a conversion inside `geos`, it should be done alongside or outside but not inside the `compute_voronoi` function.
The self-generated [documentation for geos crate](https://docs.rs/geos/4.0.0/geos/) is rather empty. Perhaps we should try to document the main structs (`CoordSeq`, `GGeom`) and put some examples to feed a bit the documentation.
It would be very helpful if new tags were created for each new crate version. https://github.com/georust/geos/tags atm only has [2.0.2](https://github.com/georust/geos/releases/tag/2.0.2)
This has been occurring for quite a long time, so raising an issue to ensure it is either fixed, or the test runner enhanced to ignore the known problems. https://github.com/georust/geos/actions/runs/7817187602/job/21324473886...
```rust error: failed to run custom build command for `geos-src v0.2.1 (/home/jayvdb/rust/geos/sys/geos-src)` Caused by: process didn't exit successfully: `/home/jayvdb/rust/geos/target/debug/build/geos-src-2ae16c31e7b1411f/build-script-build` (exit status: 101) --- stdout cargo:rerun-if-changed=build.rs CMAKE_TOOLCHAIN_FILE_x86_64-unknown-linux-gnu = None CMAKE_TOOLCHAIN_FILE_x86_64_unknown_linux_gnu =...
I can use dynamic compilation to implement functions after installing libgeos on Ubuntu, but after the program is sent to other environments, if other machines do not have lib Geo,...
