Skip to main content
  • EN

Hi all

 

 

I'm about to make a spatial query from two tables. One is a SQL-Creater with a MSSQL Spatial driver. The other is a WFS with polygons. (I have to read from MSSQL by SQLCreater because of a complex nested query that won't fit into the MSSQLSpatial Reader. I've tested the query in MSSQL Server Management Studio and it works just fine with geometry attached).

 

 

I've loaded the PointOnAreaOverlayer, however it doesn't seem to fetch the GEOMETRI-column in which the geographic data is.

 

Is it a setting in the SQLCreater or in the POAO that has to be made for it in order to make a spatial join?

 

 

Hi @chemichael,

When you view the data in de Data Inspector, do both inputs have the same coordinate system and are aligned (e.i you see them both on top of each other)?

If not you probably have data in different coordinate systems and there fore the overlay will fail.

Hope this helps.

In the screenshot above there are no features exiting the SQLCreator...?

I'm not familiar with how geometry is stored in MSSQL. Have you tried using a GeometryReplacer with Geometry Encoding set to Microsoft SQL Server Binary?

In the screenshot above there are no features exiting the SQLCreator...?

I'm assuming the 30,641 features exiting the Rejected port came from the SQL query originally...

One way to get the geometry out of SQL Server Spatial and into FME using the SQLExecutor, is to cast the geometry column to binary using the STAsBinary method, e.g.

select my_column1, my_geometry_column.STAsBinary() as geom_wkb
from my_table

You should then expose "geom_wkb" in the SQLExecutor, then follow with a GeometryReplacer set to OGC Well-Known Binary to extract the geometry before proceeding as usual.

Reply


Community Stats

30,177
Posts
114,555
Replies
37,843
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.