geo
geo copied to clipboard
georust
Geospatial primitives and algorithms for Rust
point types
how do we want to handle the difference between x,y, x,y,z, x,y,z,w (someone could conceivably want a 4th digit for something like time). Possibilities - WKT style: use templates or...
# Overview The ability to buffer geometries is fundamental to a high-quality geometry library. Thus far, we lack that ability. This is a kind of tracking issue for the implementation...
I'd like to use geo in a `no_std` build. Any chance this will be supported soon? If not on you roadmap, would you accept a PR?
This would allow us to make more geo algorithms generic over `CoordsIter` like `Simplify` ```rust pub trait CoordsIter
rust-geo still has the `ToGeo ` trait in traits.rs. Is this trait still required? I guess the conversion traits are the way to go.
This is a issue to gather discussion (started from #660) around eventually releasing a `geo-types` 1.0. To streamline the discussions, we could list topics categorized as: 1. Blocker for 1.0...
I've been thinking about this for years...
Should we deprecate Point::new(1, 1) constructor in favor of point!(x: 1, y: 1) macro constructor?
https://github.com/georust/geo/issues/528