Skip to main content
  • EN

I have a very simple workspace. A DTED reader which is set to read a few thousand .dt0 files. This feeds into a Sorter transformer, which sorts alphabetically on fme_dataset, and finally outputs to an Inspector 

When exactly 506 features have entered the Sorter, all subseqent features gives the error

ERROR |DTED Plugin: Failed to open file Z:\raw\Elevation\Global\DTED0\dted\e016\s05.dt0.
WARN  |MULTI_READER(DTED_1): Skipping to next Reader

and only the first 506 features are output from the Sorter. This happens regardless of which .dt0 files are read, the limit is always 506 features.

This seems like a bug in the DTED reader to me, because a DEM reader does not give the same error.

I'm using FME 2018.1.0.0

Hi @mbu, sorry to hear about this error you're getting. Would you be able to tell me which OS you're using (i.e. Windows, Mac)? If Windows, are you using the 32-bit or 64 bit version of FME Desktop?

 

Hi @Nampreet , I'm using 64 bit Windows 10.

I was able to reproduce this issue and have filed a ticket with our development team (reference: FMEENGINE-56260). We will post an update here once the issue is resolved.

Thanks @mbu for bringing this to our attention!

Hi @mbu: We found a potential workaround for you while we are looking into your issue. I got the workspace to process all my DTED files by adding a RasterCheckpointer before the Sorter. This will essentially process/read-in each DTED file, save it to a temporary space, and close the original file. Let me know if this works for you in the meantime.

See also https://knowledge.safe.com/articles/449/error-reading-large-number-of-raster-files.html

Hi @mbu: We found a potential workaround for you while we are looking into your issue. I got the workspace to process all my DTED files by adding a RasterCheckpointer before the Sorter. This will essentially process/read-in each DTED file, save it to a temporary space, and close the original file. Let me know if this works for you in the meantime.

I can also advise that this is fixed in FME 2019. We can't backport it to 2018.x, but the workaround above should get you through we hope.

 

 

@mbu: I'm glad to inform you that the fix for this issue is now available in the FME 2019 Beta release (build 19150+).

Reply


Community Stats

31,801
Posts
120,805
Replies
39,419
Members

Latest FME

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.