Corey Farwell comments

Results 416 comments of


                                            Corey Farwell

Introduce trait for accessing geometries

WIP PR: https://github.com/georust/rust-geo/pull/85

Figure out if it's possible to make the algorithm traits generically commutative

nice, good find! for posterity, here's the tracking issue for specialization: https://github.com/rust-lang/rust/issues/31844

remove all deprecated features from `geo-types`

@michaelkirk Gotcha, thanks for explaining. In that case, do you (or anyone) have any hesitations about a 0.7.4 release for geo-types?

Write custom, more succinct, debug output for all geometries in geo-types

This all sounds good to me! 👍🏻

For algorithms that return meters, document that self and the input is expected to be latitude/longitude degrees

Somewhat related to https://github.com/georust/geo/issues/194#issuecomment-621776960

Line Slice

are you thinking something like this? ```rust let ls = line_string![coord1, coord2, coord3, coord4, coord5]; assert_eq!( line_string![coord2, coord3, coord4], ls.slice(coord2, coord4) // or ls[coord2..=coord4] ); ```

point types

I think initially just having two coordinates (x, y) should be be an okay starting point, and if we want to expand we can do that in the future. Though,...

geo structs

Maybe we should open separate GitHub issues to discuss each of these points individually to facilitate better, more organized discussion. In terms of XYZM, does the M coordinate value ever...

geo structs

Unless I'm looking at this incorrectly, [it looks like JTS's distance operation only works on XY](https://github.com/simplegeo/jts/blob/master/src/com/vividsolutions/jts/operation/distance/DistanceOp.java) even though they offer XYZ (and M).

Design a better UX with lengths/distances/area

Relevant issue: https://github.com/georust/rust-geo/issues/194 Library that may help here: https://github.com/paholg/dimensioned/