Skip to main content
  • EN

We are using FME 2017.1 to transfer facilities from one company to another going from a SW 5.2.3 database to a SW 5.1.2 database.  I can connect to the SW 5.1.2 Gas_transmission dataset from the SW 5.2.3 session. When setting up my Workspace, I have multiple geometries being exported like gt_line_loop (beg_location, end,location, route_satellite and route_aerial). Iff I have 11 records that I am exporting from SW 5.2.3, I will have 4 sets in the reader (11 per geometry). If I just run a straight tranlastion, I end up 44 gt_line_loop records being inserted into the SW 5.1.2 database. I only want 11 records to be imported/inserted. I did an AttributeCreator and created sworld_geometry{0}.sworld_name for beg_location. I set up another AttributeCreator sworld_geometry{1}.sworld_name for end_location. I crete and Aggregator and do it on ID and Merge Attributes. I run translation and it appears to work fine. I get 11 records with beg_location and end_location populated. If I do AttributeCreators on route_satellite and route_aerial, let's say sworld_geometry{2}.sworld_name and sworld_geometry{3}.sworld_name, I get an error or it does not populate the route_satellite and route_aerial. I want to set this up so all four geometries get populated for just the 11 records. Need some help on this.

Thaks,

R. Mark Smith

DOminion Energy

Hi @robe543​ 

 

I think this may have to do with how you are reading in the SW data. On the GE Smallworld Reader there are 2 settings, one preserves the multiple geomtries, the other splits the feature into each geometry type(point, line, annotation etc.)

 

Try changing the following parameter -

Service: from FME to FMENOFACTORY

 

The FME setting splits the incoming features, while the FMENOFACTORY will preserve the original feature(so they should only have 11). Let me know if that works!

Hi @robe543​ 

 

I think this may have to do with how you are reading in the SW data. On the GE Smallworld Reader there are 2 settings, one preserves the multiple geomtries, the other splits the feature into each geometry type(point, line, annotation etc.)

 

Try changing the following parameter -

Service: from FME to FMENOFACTORY

 

The FME setting splits the incoming features, while the FMENOFACTORY will preserve the original feature(so they should only have 11). Let me know if that works!

Hi trentatsafe, I was working on gt_casing and I decided to try setting the Service to FMENOFACTORY for the Reader. Yes, it made one Feature and I got one for one records being written to the other Smallworld DB. The only thing is, it did not bring the geometries across. I did not use FMENOFACTORY for the Writer. On the gt_casing object, you can have route, extent and Annotation. Maybe, I am doing something wrong. Any other suggetions?

bcid:image001.png@01D6884F.65EAF820]

Hi @robe543​ 

 

I think this may have to do with how you are reading in the SW data. On the GE Smallworld Reader there are 2 settings, one preserves the multiple geomtries, the other splits the feature into each geometry type(point, line, annotation etc.)

 

Try changing the following parameter -

Service: from FME to FMENOFACTORY

 

The FME setting splits the incoming features, while the FMENOFACTORY will preserve the original feature(so they should only have 11). Let me know if that works!

Hi trentatsafe, disregard my last reply. I found that I still had an Aggregator in the Workbench. I took it out and Geometries came across and were inserted with records.

Reply


Community Stats

30,189
Posts
114,582
Replies
37,853
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.