This is a follow up to this question:

I am trying to find the a workflow that will define dynamic schema readers from a blank workspace - that is to say, without using the "Generate work space" option.

The "Generate Workspace" option seems to only allow for the definition of one type of type (i.e. format) of reader (such as raster). I am trying to figure out how to load many sorts of dynamic readers (raster, shape file, point cloud) into one workspace. As far as I can tell the "add reader" button on the toolbar will only add a static reader.

2 Answers 2


This help page should get you going.

The key is to change the Workflow Options to Single Merged Feature Type. Also look at the section on Adding Multiple Readers. There are some options there that might assist you.

  • it seems that "Single Merged Feature Type" still requires the files to be the same format (mine are different formats), unless Ive misunderstood something. I read the section about "Adding Multiple Readers", which states: "To add readers of differing format and schema, or readers of the same format and schema but for which other dataset settings need to be different, select Readers > Add Reader from the menu bar." - which leads me to the same problem - I dont see how I can define a dynamic reader from that menu option.
    – whatIS
    Commented Apr 22, 2014 at 20:05
  • 1
    It's not unusual to have multiple readers in one workspace. However, if you have multiple files that are the same format, you can use the dynamic reader for that format. You can also try looking into the "Generic" format reader.
    – Fezter
    Commented Apr 23, 2014 at 0:22
  • Fezter is correct the Generic Reader is what you require docs.safe.com/fme/html/FME_ReadersWriters/Default.htm#generic/…
    – Mapperz
    Commented Apr 23, 2014 at 13:35

I am not clear on what you are trying to accomplish, but you might take a look at the FeatureReader transformer, which lets you specify many reader aspects dynamically (e.g. by attributes rather than by parameters, or worse, hard-coded), and only actually attempt to read features using that transformer if and when a feature enters it (allowing for more dynamic choices as to what readers are actually activated).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.