Hi @ana.j
Can you confirm if you have set the writer to INSERT or UPDATE?
Can you confirm that the writer has split the feature or it is possible that duplicate features were added?
If you are writing to an existing geodatabase, it is recommended to use transformers such as ChangeDetector or FeatureMerger transformer to compare the original and Revised data see article Updating a File Geodatabase
@ana.j would you have a little sample dataset and your workspace that you can share with us? If you are using a template file or XML workspace document to define the target schema can you also include that. Also including the results you are seeing would help.
I have seen ArcPro insert points where lines cross, but not splitting the lines. This was for a feature class that was part of a topological network.
Hello! Thank you for your prompt replays. The Writer is set on INSERT and its an existing GDB with a line feature type, the table handling is set to Use existing.
In the screenshot you can see the comparison between the writer and the reader. In green thin line is the reader and in red thick line is the writer. In blue you can see selected the overlapping line on the right and the line of the reader is long, however the writer in red was split at the cross with the perpendicular another line. Which results in 2 polylines in the writer for the one polyline in reader.
I hope I explained better this time and thank you to help me understand this behavoir.
Hello! Thank you for your prompt replays. The Writer is set on INSERT and its an existing GDB with a line feature type, the table handling is set to Use existing.
In the screenshot you can see the comparison between the writer and the reader. In green thin line is the reader and in red thick line is the writer. In blue you can see selected the overlapping line on the right and the line of the reader is long, however the writer in red was split at the cross with the perpendicular another line. Which results in 2 polylines in the writer for the one polyline in reader.
I hope I explained better this time and thank you to help me understand this behavoir.
@ana.j Thanks for the clarification. To diagnose the problem we really need to understand the target schema. Can you export the destination schema to either a file geodatabase or as an Esri XML Workspace Document (schema only) and attach here or send it to me at mark @ safe.com. It would also help to include in a zip file a small sample of your source data and your workspace. Thanks
@ana.j It looks like it is the presence of a Geometric Network feature class that causes the lines to be split. Removing the geometric Network seems to solve the problem of lie splitting. I'm not sure if it is possible to change the geometric feature class properties to prevent line splitting - perhaps any Esri experts can chime in.