Skip to main content
Solved

Dissolver error - INDEX FAILURE - requested predicate not implemented

oscard
Influencer
Forum|alt.badge.img+21

Good morning.

I have a very simple workspace that reads some polygons from a SHAPE file, aggregates them depending on an attribute and dissolves them with a "Group By" using the same attribute.

0684Q00000ArBgHQAV.png

This is working fine with FME Desktop 2017.1 (32-bits)

Today I wanted to update this workspace to FME Desktop 2018. I have tested it with FME Desktop 2018.0 (32-btis) and FME Desktop 2018.1 (32-bits). It always fails with this error:

"Dissolver(PolygonDissolveFactory_base_factory): INDEX FAILURE - requested predicate not implemented"

2018-10-17 11:47:04|   0.9|  0.0|STATS |Dissolver(PolygonDissolveFactory_base_factory): Dissolving 1523 input polygon(s) across 26 group(s)
2018-10-17 11:47:04|   0.9|  0.0|INFORM|Dissolver(PolygonDissolveFactory_base_factory): If the input dataset is large or complex, the dissolver could run for extended periods of time without logging
2018-10-17 11:47:04|   0.9|  0.0|STATS |Storing feature(s) to FME feature store file `C:\Users\OSCAR~1.DIA\AppData\Local\Temp\SHP_a_DGN_2018_114703\inspector.ffs'
2018-10-17 11:47:04|   1.3|  0.3|ERROR |Dissolver(PolygonDissolveFactory_base_factory): INDEX FAILURE - requested predicate not implemented
2018-10-17 11:47:04|   1.3|  0.0|STATS |Stored 253 feature(s) to FME feature store file `C:\Users\OSCAR~1.DIA\AppData\Local\Temp\SHP_a_DGN_2018_114703\inspector.ffs'
2018-10-17 11:47:04|   1.3|  0.0|INFORM|Saving spatial index into file 'C:\Users\OSCAR~1.DIA\AppData\Local\Temp\SHP_a_DGN_2018_114703\inspector.fsi'
2018-10-17 11:47:04|   1.3|  0.0|INFORM|Finished saving spatial index into file 'C:\Users\OSCAR~1.DIA\AppData\Local\Temp\SHP_a_DGN_2018_114703\inspector.fsi'
2018-10-17 11:47:04|   1.3|  0.0|ERROR |INDEX FAILURE - requested predicate not implemented
2018-10-17 11:47:04|   1.3|  0.0|INFORM|Translation FAILED with 2 error(s) and 0 warning(s) (0 feature(s) output)

I have two different shape files. With one of them, it only works with FME 2017.1. With the other one, the three versions work fine.

I do not undertsand what the error means, so I don't know which differences I should be looking for among the SHAPE files.

0684Q00000ArBg3QAF.png

Does anyone have a clue about it?

Thanks for any help provided!

Best answer by fmelizard

Hi @oscard I haven't seen this error before. Please file a case via https://www.safe.com/support/report-a-problem/ Thanks!

View original
Did this help you find an answer to your question?

9 replies

fmelizard
Contributor
Forum|alt.badge.img+17
  • fmelizardContributor
  • Contributor
  • Best Answer
  • October 17, 2018

Hi @oscard I haven't seen this error before. Please file a case via https://www.safe.com/support/report-a-problem/ Thanks!

gio
Contributor
Forum|alt.badge.img+15
  • gioContributor
  • Contributor
  • October 17, 2018

@oscard

..why would you aggregate them first and then dissolve on same group by key?

You even have the dissolver deaggregate them.

Is there a reason for the aggregation? Do you maybe concatenate or sum some attributes?

Seems like you can skip the aggregation(?)

oscard
Influencer
Forum|alt.badge.img+21
  • oscardInfluencer
  • Author
  • Influencer
  • October 17, 2018
gio wrote:

@oscard

..why would you aggregate them first and then dissolve on same group by key?

You even have the dissolver deaggregate them.

Is there a reason for the aggregation? Do you maybe concatenate or sum some attributes?

Seems like you can skip the aggregation(?)

The risks of copy/paste from a a much larger workspace without thinking!!

 

Yes, the Aggregator is kind of useless in this case. In any case, without it the error is still the same.

 

 

oscard
Influencer
Forum|alt.badge.img+21
  • oscardInfluencer
  • Author
  • Influencer
  • October 17, 2018
fmelizard wrote:

Hi @oscard I haven't seen this error before. Please file a case via https://www.safe.com/support/report-a-problem/ Thanks!

I will file a case. Thanks!

 

 

olivier
Contributor
Forum|alt.badge.img+7
  • olivierContributor
  • Contributor
  • February 24, 2019

Hi @oscard,

I encounter the exact same error. Have you been able to identify the root cause and/or a workaround?

Thanks!

Olivier

oscard
Influencer
Forum|alt.badge.img+21
  • oscardInfluencer
  • Author
  • Influencer
  • February 25, 2019
olivier wrote:

Hi @oscard,

I encounter the exact same error. Have you been able to identify the root cause and/or a workaround?

Thanks!

Olivier

I forgot about this!

 

 

My solution was using FME 2017.1
fmelizard
Contributor
Forum|alt.badge.img+17
  • fmelizardContributor
  • Contributor
  • February 25, 2019
oscard wrote:

I forgot about this!

 

 

My solution was using FME 2017.1

Hi @oscard and @olivier The Dissolver in FME 2019 betas is the fastest and most robust ever. If you can reproduce the problem with the latest beta - www.safe.com/beta then please file a case via https://www.safe.com/support/report-a-problem/

gio
Contributor
Forum|alt.badge.img+15
  • gioContributor
  • Contributor
  • February 25, 2019
olivier wrote:

Hi @oscard,

I encounter the exact same error. Have you been able to identify the root cause and/or a workaround?

Thanks!

Olivier

@oscard

 

I have encountered this annoying problem a lot in the current 2018 version.

 

After removing all things unwanted, small parts, areas posing as lines etc.. I was still getting this error.

I found a object causing it. It was a donut with the hole object where this same hole contained a object which was identical to the hole-object but was not created as a hole-object. (...)

This object was created by a areonarea overlay to extract data for some expression.

Little piece of script now finds and removes or sidetracks them (if they occur) and the workbenches have not crashed on this issue since.

olivier
Contributor
Forum|alt.badge.img+7
  • olivierContributor
  • Contributor
  • February 25, 2019
gio wrote:

@oscard

 

I have encountered this annoying problem a lot in the current 2018 version.

 

After removing all things unwanted, small parts, areas posing as lines etc.. I was still getting this error.

I found a object causing it. It was a donut with the hole object where this same hole contained a object which was identical to the hole-object but was not created as a hole-object. (...)

This object was created by a areonarea overlay to extract data for some expression.

Little piece of script now finds and removes or sidetracks them (if they occur) and the workbenches have not crashed on this issue since.

Thank you @gio! My process flow is quite complex and reads voluminous data. Indeed it involves Dissolver transformers after AreaOnArea operations. I have not yet been able to isolate the feature(s) responsible but there is a good chance that they involve polygons matching with donut holes. I suspect that the issue arises when the tolerance of the Dissolver is set on 'Automatic' instead of 'None'. The error did not occur at that specific Dissolver step during a rerun after changing the tolerance to 'None'. I will add more info in this thread when my test with the FME 2019 beta is done.

Reply


Helpful Members This Week

Community Stats

30,915
Posts
117,136
Replies
38,719
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie 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.