Yes, if you have a generic reader and expose the fme_basename, fme_format_short_name and fme_basename, then use a FeatureWriter, in the Writer Parameters set the Output Format to fme_format_short_name and the Base filename to fme_basename (unless you want a different output file name, in which case set it to an attribute containing that name)
In the feature type parameters set the Feature Type Name to fme_feature_type, Geometry from Schema Definition, Check off Dynamic Schema, and set the Schema Sources to your generic reader.
If you would like a different Feature Type Name, then set that to whatever attribute contains the name, but the Schema Definition Name must be set to the fme_feature_type.
is there a way to get the FORMAT from the generic reader and pass it to the generic writer automatically in newer versions of FME somehow?
This is not the problem though in the scripted parameter. The problem is it can't reach the parameter "$(SourceDataset_SHAPE)" : "ParamFuncinvoked from within" error
That is what Jonathan is trying to do. Set output filetype to same as inputfiletype.
( i think he has to either use a workspacerunner, or use extension to select one writer using a testfilter wich boils down to basicaly entering writers for all expected possibel filetypes.)
When fme2015 is rolled out here (next week or so; i accepted and tested the instalation) we will see if i can do away with the @Evaluate. But if u use nested tcl bits, u need to use @Evaluate(). At least in and up to fme 2014sp2. Nesting is common practice.
This does not apply however to using tcl in script in a tcl caller; no need for the @Eval there.
So in a start-up i would not need to use the @Evaluate. This is only needed when used in the transformers.
(i do hope i can still use tcl in transformers though...if not that would be a big drawback)
-----
return [lindex [split $FME_MacroValues(SourceDataset_GENERIC) {.}] end]
-----
FME Functions such as @Evaluate don't work in a Tcl script.
And also, in FME 2015, the @Evaluate function will not evaluate Tcl script and string expressions no longer. The function is now only for evaluating a math expression.
[string range $(SourceDataset_SHAPE) @Evaluate(@Evaluate([string length $(SourceDataset_SHAPE)])- 3) @Evaluate([string length $(SourceDataset_SHAPE)])]
to get the extention and then somehow pass it to set the "$(GENERIC_OUT_FORMAT_GENERIC)" parameter.
..but all attemtps ended in "ParamFuncinvoked from within" error.
Maybe a startUp script to set it?
I think a start-up script would do.
I tried creating a tcl to do that in a scripted parameter, but run into "ParamFuncinvoked from within" error.
Just an idea.
If the input format could be determined by the file extention of specified source dataset, it might be possible to define a scripted parameter that returns appropriate output format name based on the input format.
Takashi
David - Ok. It seems odd that it's not possible as it's a simple use-case.
Thanks
I not think it is possible to set the Generic writer format at run-time. Your closest bet is using a published or private parameter (those are evaluated just before run-time).
David
AttributeCreator becomes:
outformat =
$(DestDataset_GENERIC)$(FileOut).$(GENERIC_OUT_FORMAT_GENERIC)
This works.
Any help?
Greetzz.