Skip to main content
Solved

FeatureMerger, data from different readers: geometry not written

  • April 28, 2014
  • 1 reply
  • 7 views
vki
Contributor
Forum|alt.badge.img+7
  • vkiContributor
  • Contributor
I want to merge two features with FeatureMerger (Attributes only). The requestor is an Oracle spatial featuretype, the supplier an Oracle non-spatial featuretype. Although the geometry passes through a GeometryValidator, it is not written (Oracle Spatial writer). I get: Bad geometry detected in the following feature; Geometry could not be encoded for Oracle. If the requestor and the supplier-feature are both Oracle-spatial, it works just fine.

 

As a workaround I tried to use a GeometryExtractor before and a GeometryReplacer after the FeatureMerger (http://fmepedia.safe.com/AnswersQuestionDetail?id=906a0000000cu9WAAQ) but I get the same error.  (I'm using FME Desktop 2013)

 

Any suggestions? Thanks in advance.

 

 

Vera

 

Best answer by kathyross

You may need to send your workspace to a support email.

 

 

My suggestion would be to:
  • Try writing to another format temporarily. e.g. ESRI / MapInfo. Is the geometry still lost?
  • Use a GeometryRemover before the FeatureMerger on the Oracle Non-Spatial input connection
  • Ensure that the Oracle Spatial data is going into the Requester input port of the FeatureMerger
It may simply be a logic mismatch or it may be something "interesting" with the Oracle writer itself.

 

View original
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

K
Forum|alt.badge.img+4
  • kathyross
  • Best Answer
  • June 4, 2014
You may need to send your workspace to a support email.

 

 

My suggestion would be to:
  • Try writing to another format temporarily. e.g. ESRI / MapInfo. Is the geometry still lost?
  • Use a GeometryRemover before the FeatureMerger on the Oracle Non-Spatial input connection
  • Ensure that the Oracle Spatial data is going into the Requester input port of the FeatureMerger
It may simply be a logic mismatch or it may be something "interesting" with the Oracle writer itself.

 

Helpful Members This Week

Community Stats

30,910
Posts
117,117
Replies
38,714
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

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