ElasticSearch coordinates are always stored in LL-WGS84. If spatial data in a different coordinate system enters the ElasticSearch writer, then FME will try and reproject the data to LL84. In this case, it looks like the SQL Server reader is not returning a recognized coordinate system for the dbo.Parcels_View table. Use FME Data Inspector to view the dbo.Parcels_View table and confirm the source coordinate system. You might have to explicitly set the coordinate system on the SQL Server reader.
@boubcher It looks like Kibana does not support geo_shape. I found this request for them to add support. There seems to be several requests for this here and here . You could add your thoughts to one of these discussions.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.