Good news for us Elastic users:

Several geospatial systems use Well Known Text (WKT) as their preferred/only format for geospatial objects.  What if you wanted to use Elasticsearch for your geospatial data though?  Until 6.2, Elasticsearch has only provided the option of providing shapes in GeoJSON format.   To get your WKT data into Elasticsearch, you may have to go through a complicated export + conversion process.  No longer!  You can now index a shape in a WKT string directly to Elasticsearch.

I’ve been using WKT quite a bit because it supports curves and now I can load WKT natively into Elasticsearch without converting it beforehand.  There is much here to think about for sure!