Skip to main content
Question

How can I avoid creating "wrong"handed curves with the GeometryReplacer?

  • May 25, 2018
  • 2 replies
  • 9 views
G

I am using the GeometryReplacer with the "OGC Well Known Text" Geometry Encoding. The Geometry Source is "CIRCULARSTRING(@Value(StartX) @Value(StartY),@Value(MidX) @Value(MidY),@Value(EndX) @Value(EndY))". It nicely creates curves from the StartXY, MidXY and EndXY coordinates. But 5% of the curves show the remainder of the curve, not the curve as it is defined by the input coordinates. What is the reason?

 

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, 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.

2 replies

takashi
Celebrity
  • takashiCelebrity
  • 7843 replies
  • May 26, 2018

Could you please post some OGC WKT examples that have been replaced with wrong curves by the GeometryReplacer?

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
G
  • gidolangen
  • Author
  • 14 replies
  • May 28, 2018

I investigated the issue further and discovered that the input data had an minute almost invisible error. I appreciate your interest. But everything is fine with the CIRCULARSTRING command. Thanks so much,

Gido

Community Stats

32,086
Posts
121,845
Replies
39,727
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.