Johannes Drönner

rust-geo doesn't need to handle transformations internally :) Maybe we could create a trait for SRS/CRS with a method to get the corresponding proj4 string or the projection ID (e.g....

I would really like to see some progress on this issue 😄 In my experience data sets with non WGS84 CRS are still very common. My original idea was to...

I really like the idea of having traits for accessing geometries :) Is it really necessary to have `opt_m` and `opt_z` ? And will they always be `f64`? As Point...

Hi @pka i understand that it is not easy to find a generic trait which fits all needs. Maybe we could split the `Point` into multiple traits? Something like this:...

I guess you are right. If we treat Point2D and Point3D as different types than some things have to be handled separate. Accessing the z values of 3D line points...

We can use the associated type `ItemType` of the `LineString` trait to define the type of the points: ``` pub trait LineString Self::Iter; } pub fn do_something f64 where L:...

Maybe we can create a "basic-geometries" crate at some point which a format library can use if it doesn't need a special implementation... Just to be clear: i really like...

@pka maybe we can find a solution for `to_ewkb` that doesn't require to much code. Would it be possible to combine the de/encoding with `rust-wkt` and then reuse common parts?...

I'm also still interested in this. One open point is the design of **factory traits**. What are the minimal requirements for such a trait? I guess we need: * a...

I like the idea of the trait approach. Will rust-geo provide baseline implementations for all geometries which are currently covered by the enum? Will this be similar to `num` and...