FME - Can I write back into my original file geodatabase

Question

I have a gas pipeline network which I have stored in an File Geodatabase as polylines. I've created an FME workspace to split the pipelines at fittings (valves, reducers, tees, etc) which are stored as point features. This effectively creates smaller line segments when a fitting overlaps a pipe.

My question is: can I have FME remove my original pipes and replace them with my split lines? Or do I have to write to another geodatabase and then cut/paste back into the original file? Please note, I am using a tester to query out only a certain area, so I don't want to replace all of the pipes, just the area I'm working on.

I'm relatively new to FME and appreciate any input.

Thanks,

Rob

Answer 1

Yes, you can write back to the same source file geodatabase and you can even write back to the same featureclass. In the workspace below, I read in the featureclass EsriCitiesDetailed as the Clipee, then write out the clipped features right back to a featureclass with the same name in the same geodatabase.

The key is to drop the target table before you write back out to it. Truncating it won't work, as the extent will still be that of the original featureclass.

EDIT:

Based on your comments, it sounds like you need to update only the certain features you have edited. I know updating/inserting based on criteria is possible with ArcSDE, but not sure about file geodatabases. The workspace below (for ArcSDE) exposes and sets the fme_db_operation attribute to either INSERT or UPDATE based on criteria. You then expose fme_db_operation and set it in the target. Worth a shot with a file geodatabase. It won't look exactly like the workspace below, but the concept is similar, if the record exists, then update it. You won't have any inserts as you are just editing existing data. So essentially you are just testing to see if the record exists (finding it), if so, then update it.