+6An error occurred while attempting to add a shape to a feature buffer. The error number from ArcObjects is: '-2147210926'. The error message from ArcObjects is: {Closed polylines not allowed with network features [class name = wLateralLine, object id = 3688]}
I am having this error all the time. I checked the geometry and realized that there are some arcs.Then I used GeometryCoercer but it didnt fix the problem.
+7Try the ArcStroker. That converts arcs into lines.
+6Try the ArcStroker. That converts arcs into lines.
An error occurred while attempting to add a shape to a feature buffer. The error number from ArcObjects is: '-2147210926'. The error message from ArcObjects is: {Closed polylines not allowed with network features [class name = wLateralLine, object id = 3688]}
+7Well, then the problem probably relates to the error you are seeing. It's not an FME error, but an Esri error.
This feature class you are writing to (wLateralLine)... does that already exist by any chance? And does it participate in a network dataset (there should also be a junction feature class in that case)? Notice you can set the Geodatabase type on the writer feature class. Valid values are mentioned here.
Good luck..!
+7Well, then the problem probably relates to the error you are seeing. It's not an FME error, but an Esri error.
This feature class you are writing to (wLateralLine)... does that already exist by any chance? And does it participate in a network dataset (there should also be a junction feature class in that case)? Notice you can set the Geodatabase type on the writer feature class. Valid values are mentioned here.
Good luck..!
+6Hello @canerakin111,
If you want to find the closed polylines you could try the following:
1) Add a counter to the workspace to set a unique ID to each line.
2) Then send them to an Area Builder with the Group by setting set to the ID attribute.
3) Unclosed lines will be output through the Incomplete port, while any lines that closed on themselves will exit the Area port.
Alternatively, a GeometryFilter may also reveal the problem features.
Once found, a GeometryValidator may be able to correct the geometry errors.
+6Hello @canerakin111,
If you want to find the closed polylines you could try the following:
1) Add a counter to the workspace to set a unique ID to each line.
2) Then send them to an Area Builder with the Group by setting set to the ID attribute.
3) Unclosed lines will be output through the Incomplete port, while any lines that closed on themselves will exit the Area port.
Alternatively, a GeometryFilter may also reveal the problem features.
Once found, a GeometryValidator may be able to correct the geometry errors.
+6
this is the result.
+6
A colleague of mine suggested, with the fact you have the problem features identified. Use a GeometryCoercer on the Area features to convert them to lines, this should allow them to be written now.
+6 this is the result.
A colleague of mine suggested, with the fact you have the problem features identified. Use a GeometryCoercer on the Area features to convert them to lines, this should allow them to be written now.
+6
A colleague of mine suggested, with the fact you have the problem features identified. Use a GeometryCoercer on the Area features to convert them to lines, this should allow them to be written now.
+6
A colleague of mine suggested, with the fact you have the problem features identified. Use a GeometryCoercer on the Area features to convert them to lines, this should allow them to be written now.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
