Skip to main content
  • EN

we have a simple workspace MSsql spatial reader and elastic search writer, but we are having this error, attached text file

Any idea

What's the error? I only see two workspace files attached.

 

Sorry,

elastic-search-error.txt

Thanks

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.

@Mark

Thanks we fix the problem of the coordinate as you recomanded , but we are still unable to display the polygone on Kibana Dashborad

take a look at the print screens

https://qsnapnet.com/snaps/jb0alvm930kep14

https://qsnapnet.com/snaps/9nwed91dp7ujtt9

All snaps: https://qsnapnet.com/folders/v2r8vs0btwhr529

@MarkAtSafe

Any idea ?

 

@Mark

Thanks we fix the problem of the coordinate as you recomanded , but we are still unable to display the polygone on Kibana Dashborad

take a look at the print screens

https://qsnapnet.com/snaps/jb0alvm930kep14

https://qsnapnet.com/snaps/9nwed91dp7ujtt9

All snaps: https://qsnapnet.com/folders/v2r8vs0btwhr529

@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.

 

Reply


Community Stats

30,099
Posts
114,259
Replies
37,731
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.