Michael Kirk
Michael Kirk
> However, I'd rather write the "script" in Rust than as a shell script Provided it's a small number of lines of code, it should be easy to review, so...
This makes sense, though I haven't audited to see if there are places where the Math methods which take a GEODESIC_ORDER *always* take the GEODESIC_ORDER. All things being equal, it...
I'm not opposed. Is your thought that it will read more clearly?
This would be excellent!
We've misspelled `POINT Z`, `POINT M`, and `POINT ZM`. See https://github.com/georust/wkt/issues/114 Can you take a look @ariesdevil? Otherwise I think we should revert this.
One point of friction is `POINT EMPTY`. It's not clear how to handle that with geo-types.
Can you spell that out for me a bit more? What would this deserialize to? ``` let empty_point: geo_types::Geometry = Wkt::from_str("POINT EMPTY"); ```
Hmm... I'm not sure I understand your suggestion. To dig in a bit, I kind of get how `geo_types::Point` could maybe be thought of as a corollary to `POINT EMPTY`....
``` let g: Wkt = Wkt::from_str("GEOMETRYCOLLECTION(LINESTRING(10 20,20 30), LINESTRING EMPTY)") ``` What member of the `Wkt` enum would this be?