Skip to main content
Hi folks,

 

 

 

I’m trying to store in a geodatabase all points from a layer that shares the exact same location. These points are before aggregate in order to have only 1 point to represent the share location.

 

 

 

My workspace works well, but when I execute it, even if the FME log tells me that only 7598 points has been inserted in the database, when I look in it there are 42903 points added.

 

 

Here is my log file:

 

https://docs.google.com/file/d/0B6AQWwPegRg6ZXFvTEE5bmlmTms/edit?usp=sharing

 

 

Here is the select count in the database:

 

https://docs.google.com/file/d/0B6AQWwPegRg6a2pnaWVuY0Y1MDA/edit?usp=sharing

 

 

Now here is an extract of my workspace:

 

https://docs.google.com/file/d/0B6AQWwPegRg6TDE1T3gtbXdyMUk/edit?usp=sharing

 

 

As you can see the number of elements before the Aggregator is the same as the one in the database.

 

 

Finally here is the inspection done with ArcMap:

 

https://docs.google.com/file/d/0B6AQWwPegRg6ZnJVOHV1elV5dEk/edit?usp=sharing

 

 

So I would like to understand what I missing? Can you help me please?

 

 

 

Thanks

 

 

 

Hi

 

It looks to me like the geodatabase doesn't like aggregate features and is splitting them back up into their component parts. That seems strange to me, because the Readers and Writers manual states that Geodatabase does support aggregates. But, this would explain things. Technically FME is only sending 7598 features to the database, but once deaggregated there are now 42,903.

 

 

If you don't want the extra features, then can I suggest you use the Matcher transformer to remove any duplicates. Then there is no chance they will get written to the geodatabase.

 

 

Hope this helps

 

 

Mark

 

 

Mark Ireland

 

Product Evangelist

 

Safe Software Inc.
Ah, I see you do have a Matcher. Is it checking for duplicates? Maybe the other two output ports are what you need - SINGLE_MATCHED and NOT_MATCHED

Reply