Skip to main content
Archived

?CSV to Shape error trap enhancement

Related products:Transformers

davideagle
Contributor

From FME 2017 there's a neat error trap that means you don't trip over the 'rejected features' issue when writing to the Shape format quite so much. If you add a CSV reader and a Shape Writer to the canvas, the semantic capability of FME kicks in and drops a GeometryFilter on the canvas to route the null geometry records straight to a FeatureType with the shape_null geometry setting. You also get a FeatureType for points. Since the first thing you often do in this scenario is make points this means that you don't end up with lots of points being sent to a Feature Type with the wrong geometry type set. BUT, whilst this is 99% better than previously, the Null port of the GeometryFilter is auto connected to a FeatureType that gets named ' CSV_geom'. This confused a number of training delegates recently who argued that this should be called 'CSV_null' instead.

A very small change needed really.

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.

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