Michael Kirk
Michael Kirk
Another note, though this greatly speeds up (`change: [-71.144% -71.004% -70.873%]`) converting already parsed geojson to other formats, this doesn't seem to affect the actual *parsing* speeds all that much....
I believe this has been addressed - all geometries are backed by Coordinates now, not points.
Every year or so, I come back to this issue and stare into the void. For the record, I think it'd be nice to consolidate the Point and Coord structs....
Staring into this void again. I'm going to re-open this issue. > A more practical approach might be https://github.com/georust/geo/issues/901 One thing that a coordinate trait would not solve are algorithms...
Sheesh, how would we go about implementing this without blowing up the entire codebase. I think in any case it would be a *large* change. I don't think any of...
I'm going to move your issue to the geozero repository, since it seems to be about geozero.
I think we could do this fairly easily - it would be a lexical comparison of the points, probably in (x,y) ordering. ```diff - #[derive(Eq, PartialEq, Clone, Copy, Hash, Default)]...
Sorry that I didn't merge this a long time ago! I've made a couple minor changes but the thrust is the same. Can I get another review?
Yikes, sorry this got lost for so long! If you're still interested in seeing it through, I think it would be reasonable to add. > Performance testing There are some...
That seems plausible. Is this something you're interested in working on?