What am I doing wrong?
Log:
2013-07-29 15:24:42| 454.5| 0.0|INFORM|Tagging...
2013-07-29 15:25:05| 477.1| 22.7|INFORM|Tagging done (23 s).
2013-07-29 15:25:05| 477.1| 0.0|INFORM|Repairing...
2013-07-29 15:25:05| 477.5| 0.3|INFORM|Repair successful (0 s). All polygons are now valid.
2013-07-29 15:25:05| 477.5| 0.0|INFORM|Reconstructing polygons (geometry)...
Quote from the help of the SliverRemover:
This transformer requires clean, valid data. For example, self-intersecting, or degenerate polygons will not be properly repaired. So, when input polygons are not clean, the SliverRemover may not generate results. If you don't use FAILED ports of the GeometryValidators, does the SliverRemover work?
Takashi
Unfortunately, even after disconnecting the FAILED port of GeometryValidators, there is nothing different, no output.
Worst, I tryed connecting the Input directly in the transformer and no more result. Even with another dataset, I dont get output.
I am fearing the problem could be in my FME system settings. I am using FME 2013 SP2 32bit on a windows 7 64bit computer.
Looking more carefully in the log I have found something anormal just before the translation stop:
2013-07-30 08:23:19| 0.3| 0.0|INFORM|Loaded module 'SliverRemovingFactory' from file 'C:\\apps\\FME\\plugins/SliverRemovingFactory.dll'
2013-07-30 08:23:19| 0.3| 0.0|INFORM|FME API version of module 'SliverRemovingFactory' matches current internal version (3.7 20121025)
2013-07-30 08:23:19| 0.3| 0.0|INFORM|FME Configuration: Source coordinate system for reader MAPINFO_1 MAPINFO] set to `LL-WGS84' as read from input data
2013-07-30 08:23:19| 0.3| 0.0|INFORM|Coordinate System `LL-WGS84' parameters: CS_NAME=`LL-WGS84' DESC_NM=`WGS84 Lat/Longs' DT_NAME=`WGS84' GROUP=`LL' MAP_SCL=`1' PROJ=`LL' QUAD=`1' SCL_RED=`1' UNIT=`DEGREE'
2013-07-30 08:30:16| 434.3|434.0|INFORM|Emptying factory pipeline
2013-07-30 08:30:16| 434.3| 0.0|STATS |Unexpected Input Remover(TestFactory): Tested 1289 input feature(s) -- 1289 feature(s) passed and 0 feature(s) failed
2013-07-30 08:30:16| 434.3| 0.0|STATS |Unexpected Input Remover Nuker(TeeFactory): Cloned 0 input feature(s) into 0 output feature(s)
2013-07-30 08:30:16| 434.3| 0.0|STATS |Source -> Generic(TeeFactory): Cloned 1289 input feature(s) into 1289 output feature(s)
2013-07-30 08:30:16| 434.3| 0.0|STATS |Mun Feature Counter -1 18(TeeFactory): Cloned 1289 input feature(s) into 1289 output feature(s)
2013-07-30 08:30:16| 434.3| 0.0|STATS |Secteurs_Franco (MAPINFO_1) Splitter(TeeFactory): Cloned 0 input feature(s) into 0 output feature(s)
2013-07-30 08:30:16| 434.3| 0.0|INFORM|Tagging...
2013-07-30 08:30:50| 468.2| 33.9|INFORM|Tagging done (34 s).
2013-07-30 08:30:50| 468.2| 0.0|INFORM|Repairing...
2013-07-30 08:30:50| 468.2| 0.0|INFORM|Repair successful (0 s). All polygons are now valid.
2013-07-30 08:30:50| 468.2| 0.0|INFORM|Reconstructing polygons (geometry)...
If the SliverRemover works with a test data like this, there may be problems in the actual data. You should validate the data more carefully.Otherwise, I recommend you to contact Safe support. Takashi
I have contact Safe support and Im waiting for a feed back.
Thank you for your support Takashi
It seems that many transformers cannot procceed when data are aggregate or contain donut holes.