Karel Maesen

This is an example of a [robustness problem](https://en.wikipedia.org/wiki/Robust_geometric_computation). There is little we can do about this, I'm afraid. The problem should go away when we implement support for curves and...

I hope to have support for all the SQL/MM curve types in [Postgis](https://postgis.net/docs/manual-3.2/using_postgis_dbmanagement.html#SQL_MM_Part3) by end-of-year. That should also translate in better support for Oracle.

Mabe there is something we can do. If the points are so close to colinear, we can simply treat them as linear. Could you provide me the Polygon as an...

Hi I implemented the solution so that (nearly) co-linear coordinates are treated as linear and will be used as-is. Could you maybe test this? It's in 1.9-snapshot

I'll make a release then

This is not merely a matter of format. The Version 2 geometries/geographies supports feature types such as CircularString, CompoundCurve, etc. which are (currently) not supported by Geolatte-geom. So I would...

When there is a need for it. We don't try to track JTS closely. We need to be mindful that updating JTS doesn't break our API.

First inspection of the [Javadoc](https://javadoc.io/doc/com.microsoft.sqlserver/mssql-jdbc/7.1.0.jre10-preview) is not hopeful... The Geometry/Geography classes provide very few methods to inspect the structure. Interop functions are limited to WKT/WKB conversions (in several flavors).

That is not really a bug. The current MSSqlServer Encoders/Decoders are designed to work with Geometries, not Geographies. Now that geolatte-geom Geometries contain coordinate system information, we are ready to...

The transformation you need is not yet supported. You should have received some sort of error, rather than an incorrect answer. And I really should have documented what works. Sorry,...