I see this: https://pkg.go.dev/github.com/spatial-go/geoos#section-readme <https://pkg.go.dev/github.com/spatial-go/geoos#section-readme> But haven’t tried it.
—Josh > On Mar 30, 2022, at 9:46 AM, George Percivall <[email protected]> wrote: > > Thanks to Josh and Martin for your responses. > > Anyone know of an open library in Go? > > > George Percivall > GeoRoundtable <https://www.linkedin.com/company/geo-roundtable/> > >> On Mar 29, 2022, at 3:22 PM, Martin Desruisseaux >> <[email protected]> wrote: >> >> Hello Georges and all >> >> The following article, "How Good Are Modern Spatial Libraries?" (published >> November 2020) does a comparison between JTS, GEOS and other libraries: >> >> https://doi.org/10.1007/s41019-020-00147-9 >> >> Note: I do not know why the language restriction, but if it is for >> performance, the reality can be counter-intuitive. GEOS is a port of JTS >> library from Java to C. So it should be the same algorithms, only in a >> different language. But according benchmarks in above-cited articles, GEOS >> is actually… slightly slower than JTS. >> >> Martin >> >> P.S.: On GEOS benchmark results: the authors attribute that to excessive >> memory allocations. The malloc and free functions in C/C++ are slower than >> memory allocation in Java. With a garbage collector, only surviving objects >> have a cost. In a program where e.g. 90% of objects die young, garbage >> collector can be more performant than explicit memory allocation (I also saw >> a benchmark from IBM a long time ago doing similar demonstration with the >> grep program). >> > > >> On Mar 29, 2022, at 12:46 PM, Joshua Lieberman >> <[email protected]> wrote: >> >> https://libgeos.org <https://libgeos.org/>.
