jusiheap wrote:
> 1. Surely this has been discussed before, but is it the case that
> there is no facility to resize (i.e. widen) the boxes on the
> workbench canvas for features/attributes/transformers? I tend to use
> quite verbose names (and indeed plenty of the transformers have long
> names), so I'm constantly having to hover the cursor over on object
> and wait for the tool tip before I can identify it absolutely.
This is not possible, however, in Tools -> Options you can specify how
FME abbreviates the transformer names. Maybe that's of some help to you.
Alternatively, you can attach summary annotations to the transformers
(right click, show summary annotation), which shows the full name.
> 3. I've noticed that the AttributeRemover does not appear to support
> the removal of list attributes - such attributes are not included in
> the "Attributes to Remove" pick list. Why is this? The documentation
> for the @RemoveAttributes function suggests that list attributes
> should be supported.
Lists can be removed with the ListRemover.
> 4. Looking at the documentation, there are plenty of functions (e.g.
> @Coordinate) with different 'modes' of invocation, depending upon
> the type/value of the supplied parameters. Each transformer supports
> one any only one mode of invocation (e.g. CoordinateFetcher calls
> @Coordinate((x|y|z),(<index>|END),[FLATTEN_AGGREGATE])) - does this
> mean that there will always be other transformers that use the other
> invocations, or do you have to get your hands dirty to use them?
It depends on the actual function. Rest assured though, there's hardly
ever a need to get your hands dirty in a mapping file. I haven't come
across one ever since Workbench first appeared in a beta.
> 5. ... which leads to the question: if you do decide to get your
> hands dirty in the mapping file, does this mean that you have to
> ditch workbench because it won't necessarily be able to visualise
> your script?
Workbench is not capable at all to visualise a mapping file. However,
you can edit the workbench file (.fmw) just like a mapping file (.fme)
because it basically is a mapping file with some visualisation
information attached. However, depending on what you do exactly,
Workbench may not be able to properly read it anymore.
> Please let me know if I'm doing the right thing in piling such
> questions (and there will be more) into this forum, and feel free to
> recommend how I might find the answers elsewhere without bothering
> everyone ...
Well, don't worry about bothering everybody, that's what this list is
for. Alternatively, check out the FMEPedia (www.fmepedia.com), where
we've collected a load of information on FME.
Hope this helps.
--
Hans van der Maarel
Red Geographics
www.redgeographics.com / [EMAIL PROTECTED]
Join us at the FME Worldwide User Conference Sept. 21-22, 2006 Vancouver BC
Canada. For more information, visit www.safe.com/2006uc.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/fme/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
