It looks like you need to flatten the oData (it's json) first and then expose the GeoInstance.Geography.WellKnownText. That holds the WKT and that can be used by the GeometryReplacer, like this:
I did have to add a } at the end of that oData string to make it valid though. Can you doublecheck your data to see whether or not it's just a matter of missing one character when copying it into your original post.
As an added suggestion: if you expose the GeoInstance.Geometry.CoordinateSystemId and then use an AttributeManager to turn that into an EPSG coordinate system identifyer you can put that in to a CoordinateSystemSetter:
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.
It looks like you need to flatten the oData (it's json) first and then expose the GeoInstance.Geography.WellKnownText. That holds the WKT and that can be used by the GeometryReplacer, like this:
I did have to add a } at the end of that oData string to make it valid though. Can you doublecheck your data to see whether or not it's just a matter of missing one character when copying it into your original post.
As an added suggestion: if you expose the GeoInstance.Geometry.CoordinateSystemId and then use an AttributeManager to turn that into an EPSG coordinate system identifyer you can put that in to a CoordinateSystemSetter: