+5In FME 2021.1, is anyone else having an issue where the feature class that FME writes is a data table, instead of a polyline?
I'm using a dynamic workflow with a FeatureWriter and the open file geodb writer on a Mac.
This was working perfectly before upgrading to test in 2021.1.
+2Hi @dannymatranga ,
Any chance you'd be able to share the log file for the successful translation in a previous version and the failed version in 2021.1?
+5Hi @dannymatranga ,
Any chance you'd be able to share the log file for the successful translation in a previous version and the failed version in 2021.1?
@chrisatsafe I see this line in the translation log:
FileGDB Writer: Failed to write Geometry to feature class 'GPS_PATHS' with geometry type 'esriGeometryPolyline'. Dropping containing feature
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++and then here's another chunk of the log that looks suspect:
Attribute(string: UTF-8) : `filegdb_type' has value `geodb_polyline'
Attribute(string: UTF-8) : `fme_feature_type' has value `record'
Attribute(string: UTF-8) : `fme_geometry' has value `fme_aggregate'
Attribute(string: UTF-8) : `fme_geometry{0}' has value `fme_line'
Attribute(string: UTF-8) : `fme_template_feature_type' has value `d_y_n'
Attribute(entangled: string: UTF-8): `fme_type' has value `fme_line'
entangled to filegdb_type
Attribute(32 bit unsigned integer) : `multi_writer_id' has value `0'
Coordinate System: `SPHERICAL_MERCATOR'
Geometry Type: IFMEAggregate
Front Appearance Reference: `<inherited_or_default_appearance>'
Back Appearance Reference: `<inherited_or_default_appearance>'
Number of Geometries: 1
--------------------------------------What I'm actually trying to write to a file geodb is an aggregate group of GPS paths (polylines). Wondering what I might be able to do to fix this, any ideas?
+5@chrisatsafe I see this line in the translation log:
FileGDB Writer: Failed to write Geometry to feature class 'GPS_PATHS' with geometry type 'esriGeometryPolyline'. Dropping containing feature
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++and then here's another chunk of the log that looks suspect:
Attribute(string: UTF-8) : `filegdb_type' has value `geodb_polyline'
Attribute(string: UTF-8) : `fme_feature_type' has value `record'
Attribute(string: UTF-8) : `fme_geometry' has value `fme_aggregate'
Attribute(string: UTF-8) : `fme_geometry{0}' has value `fme_line'
Attribute(string: UTF-8) : `fme_template_feature_type' has value `d_y_n'
Attribute(entangled: string: UTF-8): `fme_type' has value `fme_line'
entangled to filegdb_type
Attribute(32 bit unsigned integer) : `multi_writer_id' has value `0'
Coordinate System: `SPHERICAL_MERCATOR'
Geometry Type: IFMEAggregate
Front Appearance Reference: `<inherited_or_default_appearance>'
Back Appearance Reference: `<inherited_or_default_appearance>'
Number of Geometries: 1
--------------------------------------What I'm actually trying to write to a file geodb is an aggregate group of GPS paths (polylines). Wondering what I might be able to do to fix this, any ideas?
By sampling groups of points using a Sampler (I did first 100 points = write success, next 200 = write success, then 300 = write fails), so I knew the problem is somewhere with the points in there. Looks like I'm getting these self intersections in 2D, but I'm not real sure what to do about that.
With GPS data, if you jog a path, and then run back the other way and cross over your previous path, why can't I just draw that line?
+5@chrisatsafe I see this line in the translation log:
FileGDB Writer: Failed to write Geometry to feature class 'GPS_PATHS' with geometry type 'esriGeometryPolyline'. Dropping containing feature
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++and then here's another chunk of the log that looks suspect:
Attribute(string: UTF-8) : `filegdb_type' has value `geodb_polyline'
Attribute(string: UTF-8) : `fme_feature_type' has value `record'
Attribute(string: UTF-8) : `fme_geometry' has value `fme_aggregate'
Attribute(string: UTF-8) : `fme_geometry{0}' has value `fme_line'
Attribute(string: UTF-8) : `fme_template_feature_type' has value `d_y_n'
Attribute(entangled: string: UTF-8): `fme_type' has value `fme_line'
entangled to filegdb_type
Attribute(32 bit unsigned integer) : `multi_writer_id' has value `0'
Coordinate System: `SPHERICAL_MERCATOR'
Geometry Type: IFMEAggregate
Front Appearance Reference: `<inherited_or_default_appearance>'
Back Appearance Reference: `<inherited_or_default_appearance>'
Number of Geometries: 1
--------------------------------------What I'm actually trying to write to a file geodb is an aggregate group of GPS paths (polylines). Wondering what I might be able to do to fix this, any ideas?
Ok I'm gonna talk to myself again here. I managed to fix the issue by using a Chopper to break up the aggregated line, and then used an Aggregator. Before, I just had the Aggregator, but for whatever reason, using that Chopper to break up the line segments, and then build them back into an aggregated line feature worked.
+2@chrisatsafe I see this line in the translation log:
FileGDB Writer: Failed to write Geometry to feature class 'GPS_PATHS' with geometry type 'esriGeometryPolyline'. Dropping containing feature
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++and then here's another chunk of the log that looks suspect:
Attribute(string: UTF-8) : `filegdb_type' has value `geodb_polyline'
Attribute(string: UTF-8) : `fme_feature_type' has value `record'
Attribute(string: UTF-8) : `fme_geometry' has value `fme_aggregate'
Attribute(string: UTF-8) : `fme_geometry{0}' has value `fme_line'
Attribute(string: UTF-8) : `fme_template_feature_type' has value `d_y_n'
Attribute(entangled: string: UTF-8): `fme_type' has value `fme_line'
entangled to filegdb_type
Attribute(32 bit unsigned integer) : `multi_writer_id' has value `0'
Coordinate System: `SPHERICAL_MERCATOR'
Geometry Type: IFMEAggregate
Front Appearance Reference: `<inherited_or_default_appearance>'
Back Appearance Reference: `<inherited_or_default_appearance>'
Number of Geometries: 1
--------------------------------------What I'm actually trying to write to a file geodb is an aggregate group of GPS paths (polylines). Wondering what I might be able to do to fix this, any ideas?
You're too fast ;P
Glad you were able to get it all sorted. Generally with self intersects, the GeometryValidator transformer can help to identify and repair these geometry issues. But happy to hear you got it all cleaned up with the Chopper and Aggregator!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
