bearatwrc wrote:
> I am trying to create a custom transform that initially tosses (via
> ATTRIBUTE FILTERs) everything except microstation shapes and lines.
> Kept in an intact workbench, the transformes work fine but copied to a
> custom transform the ATTRIBUTE FILTERs lose awareness of the kind of
> data they will be fed. Thus the 'attribute to filter by' is null in the
> custom transform and does not recover it when reconnected to source
> data.
>
> Is there any way to tell a custom transform the attributes it will be
> getting?
Unfortunately, not as far I know.
Given the nature of the AttributeFilter, and the fact that you have
little control over what a user actually connects to your custom
transformer, I'm wondering whether this is the right approach. Any
chance you can use a GeometryFilter to achieve the same result?
--
Hans van der Maarel
Red Geographics
www.redgeographics.com / [EMAIL PROTECTED]
Get the maximum benefit from your FME, FME Objects, or SpatialDirect via our
Professional Services team. Visit www.safe.com/services for details.
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/
