Skip to main content
  • EN

I have multiple shape files from different owners classified in sub-directories.

All Owners have shape reader entries in my workbench.

Every once and a while some readers don't read the file and so I loop input. Testing the input in the workbench with the inspector option works well so the data is there. I need to recreate the reader.

How can I test non read input from these readers and terminate the workbench before going any further. When I put a counter after the reader it isn't triggered so that doesn't work.

I'd much prefer to find out why those files are not being read.

  1. Are you sure they are there and have the exact same filename as the feature type? Do you get the Unexpected Input dialog when the files are not being read (if you've disabled that, go to Tools -> FME Options -> Workbench and press the "Reset Warning Dialogs" button)
  2. Could it be that the files are opened in another application while FME is trying to read them?
  3. Could it be that the structure (schema) of the files has been changed?

To test for no features I use something similar to the following

Creator to a feature merger supplier port with the features to test to the requestor port, merge on a constant, e.g. one then a terminator on the unreferenced port

I'd much prefer to find out why those files are not being read.

  1. Are you sure they are there and have the exact same filename as the feature type? Do you get the Unexpected Input dialog when the files are not being read (if you've disabled that, go to Tools -> FME Options -> Workbench and press the "Reset Warning Dialogs" button)
  2. Could it be that the files are opened in another application while FME is trying to read them?
  3. Could it be that the structure (schema) of the files has been changed?

Hi,

 

 

1. they are there and are the same. I will reset the warning dialogs.

 

2. They aren't open by another application. As you see in screenshot I can open them with right button > Inspect.

 

3. hasn't changed...

 

 

 

To test for no features I use something similar to the following

Creator to a feature merger supplier port with the features to test to the requestor port, merge on a constant, e.g. one then a terminator on the unreferenced port

Will test this out thanks.

 

 

Hi,

 

 

1. they are there and are the same. I will reset the warning dialogs.

 

2. They aren't open by another application. As you see in screenshot I can open them with right button > Inspect.

 

3. hasn't changed...

 

 

 

Right, judging by that blue line in the log window I expect the Unexpected Input will show at least some data (shapefiles) being read that can't be matched to feature types in your workspace. That may be by design, but it may give you a clue as to what's going on.

 

 

But then again, if you inspect the features by right clicking on the feature type and choosing the inspect option that proves the data is there and can be read by FME.

 

 

I agree with @redgeographics the better solution is to determine why certain feature types are not being read. That said there is a handy-dandy NoFeatureTester custom transformer that Aaron Koning created many years ago.

To test for no features I use something similar to the following

Creator to a feature merger supplier port with the features to test to the requestor port, merge on a constant, e.g. one then a terminator on the unreferenced port

Works fine Tnx

 

 

I had the same problem. I added a Filter Type and it worked...

Reply


Community Stats

30,387
Posts
115,451
Replies
38,103
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.