Tom Payne

Hopefully the situation is improving. https://github.com/microsoft/winget-cli/issues/182 just got closed, we're waiting for documentation on how to use it now.

I would suggest: "If removing the parentheses does not change the evaluation order of the expression, then they are superfluous."

I personally don't use shapefiles, but I would be very happy to accept a PR that adds this functionality to `go-geom`.

It might be necessary to use `*ewkb.GeometryCollection` (i.e. pointer to struct) not `ewkb.GeometryCollection`. This allows the handling of `nil` values (which are represented as `NULL` in SQL). go-geom currently does...

> It seems like in order to correctly implement the interface and keep things clean with nulls, one would have to add types like `ewkb.NullGeometryCollection`. Yes, that makes sense. To...

My thoughts: 1. GeometryCollections are under-specified by the OGC and rarely used in practice (to my knowledge). It is fantastic that we're considering all the edge cases here, but I'm...

Thank you very much for reporting this. I'd missed this in the GeoJSON spec. I think that the only way to fix this without breaking backwards compatibility is to create...

Creating a buffer around a single point is relatively straightforward: the resulting geometry is a circle (likely simplified to a polygon with an appropriate number of points). [`ST_Buffer`](https://postgis.net/docs/ST_Buffer.html) is significantly...

Thank you @atombender for opening this issue :) This library effectively contains three parts: a Go-friendly representation for geometry types, a set of packages to serialize and deserialize those types,...

Linear referencing is indeed useful. A high-quality PR implementing such functionality would be welcome.