+11Can I read multiple geometry using sqlexecutor. In my case , i dont have two geometry in one table. i am extracting/constructing multiple (2) geometry from different tables and the sql gives resultset with two geometries in one row.
two geometry from sql resultset not from one table
and later i will deaggregate this and use these geometries for different purposes.
how can i achieve this using fme?
Which database are you using and how are the geometries stored?
One solution could be to cast both geometries to e.g. WKB and then use two separate GeometryReplacers to extract the geometries. Something like (pseudo-code):
select
as_binary(t1.geom) as geom1,
as_binary(t2.geom) as geom2
from
mytable1 t1 join mytable2 t2 on t1.id=t2.idThen expose "geom1" and "geom2" and send them to the GeometryReplacer as OGC Well-Known Binary.
+11Which database are you using and how are the geometries stored?
One solution could be to cast both geometries to e.g. WKB and then use two separate GeometryReplacers to extract the geometries. Something like (pseudo-code):
select
as_binary(t1.geom) as geom1,
as_binary(t2.geom) as geom2
from
mytable1 t1 join mytable2 t2 on t1.id=t2.idThen expose "geom1" and "geom2" and send them to the GeometryReplacer as OGC Well-Known Binary.
as_binary
+22Why do you need to use the SQLExecutor transformer and not an Oracle Spatial reader or the FeatureReader.
In your case the SQLExecutor seems to complicate matters only.
For Oracle Spatial, use:
SDO_UTIL.TO_WKBGEOMETRY(geom)Doc: https://docs.oracle.com/cd/B28359_01/appdev.111/b28400/sdo_util.htm#SPATL1250
For ArcSDE with an Oracle backend, use:
sde.st_asbinary(geom)Doc: http://desktop.arcgis.com/en/arcmap/10.3/manage-data/using-sql-with-gdbs/st-asbinary.htm
Why do you need to use the SQLExecutor transformer and not an Oracle Spatial reader or the FeatureReader.
In your case the SQLExecutor seems to complicate matters only.
as_binary
+11Why do you need to use the SQLExecutor transformer and not an Oracle Spatial reader or the FeatureReader.
In your case the SQLExecutor seems to complicate matters only.
+22Why do you need to use the SQLExecutor transformer and not an Oracle Spatial reader or the FeatureReader.
In your case the SQLExecutor seems to complicate matters only.
But in this example I would use two SQLCreators (not SQLExecutors), each with a query containing 1 geometry.
No need to de-aggregate afterwards.
But in this example I would use two SQLCreators (not SQLExecutors), each with a query containing 1 geometry.
No need to de-aggregate afterwards.
+22