Hi @joy​,

The LogMessageStreamer transformer can route the log messages into the workspace to allow you to extract the Global Origin parameters:

Use a Tester to isolate the global origin message, then a StringSearcher to extract the Global Origin values.

hi @daveatsafe​ 

Thanks for this suggestion. My colleague is partly in the right direction based on your script. However my colleague's script is fairly big and

the LogMessageStreamer runs at the end when all other transformers/reader have ran. Is it possible to trigger the LogMessageStreamer midway in the script? Midway in the script my colleague has several dgn files that are going to be read in and my colleague wants to have the global origin x, y and z from the dgn files midway and can use the output from the LogMessageStreamer in the rest of the script. Another question of my colleague is how to derive from which model the global origin x, y and z has been derived. So instead of only finding different x,y and z values, you can also see to which model the xyx values belong.

Hi @joy​,

It may be necessary to add the LogMessageStreamer first in the workspace. Please try creating a new empty workspace, adding the LogMessageStreamer, then copying and pasting all the transformers from the existing workspace.

The DGN file name is also logged, so with a few alterations, we can use the previous feature attribute option in FME to merge the file name and global origin messages. I am attaching an updated workspace illustrating how to do this.