I am trying to simply export results with a Writer into a .shp. If I do not use a GeometryValidator most of the features are present in the final attribute table, but not shown in a ArcGIS map. If I use the GeometryValidator and then use both the good and the repaired features as inputs for the Writer, some results are missing from the final attribute table, but all the result in said table are also displayed in an ArcGIS map. The log gives following warning "Dropping heterogeneous aggregate feature for the SHAPEFILE Writer, due to feature type allowed geometries restriction". How do I solve this? Thank you!
Solved
FME Writer not exporting all results after GeometryValidator
Best answer by rivam
Found the answer! For some reason the very GeometryValidator was creating some repaired hidden non-polygon features. These are not shown in any result table, but putting the GeometryFilter right after the GeomertyValidator did the trick for me. Putting it at a later stage was not useful, only right after the "repaired" feature coming out of the GeometryValidator. Thank you all for your help!
Try inserting a GeometryFilter before the writer to only include geometry types compatible with the output feature type definition.
In FME versions prior to 2022 you'll need to activate the option "homogenize collections" in the settings.
+48- Celebrity
One of the restrictions of shapefiles is that they can only support one type of geometry per file. This also goes for aggregate features. So if you have one aggregate containing of a point and a line FME will split that into two seperate features, going to separate shapefiles, in the writer (so really the GeometryValidator does not come in to play here).
If you want to avoid this a quick solution would be to use a Deaggregator before the GeometryValidator, although depending on what you want to do you may need to rethink your overall approach.
Found the answer! For some reason the very GeometryValidator was creating some repaired hidden non-polygon features. These are not shown in any result table, but putting the GeometryFilter right after the GeomertyValidator did the trick for me. Putting it at a later stage was not useful, only right after the "repaired" feature coming out of the GeometryValidator. Thank you all for your help!
Reply
Rich Text Editor, editor1
Editor toolbars
Press ALT 0 for help
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.