--- In [email protected], "mark2atsafe" <[EMAIL PROTECTED]> wrote:
>
> Hi Stefaan,
> This is actually the default behaviour - although it must be
confusing
> at times. I guess in this sense the FFS output is more of a dump of
> features than a proper writer.
>
> One option is that you rename (or remove) the old attributes and
just
> have the new ones on the features - that way they won't get
written.
>
> However, looking through the FME Readers and Writers Manual I see
that
> there are various options for turning off this behaviour.
> STRICT_SCHEMA is the setting to use.
>
> Because this isn't exposed by default, you can add it in Workbench
> using Tools > Edit Header. When the editor opens add the lines...
>
> # Set the strict schema
> FFS_1_STRICT_SCHEMA Yes
>
> They have to go within the FFS writer section - I added them just
> before the comment "Set the compression level"
>
> If you wish to be able to turn the option on and off within the
> workspace, then use...
>
> # Set the strict schema
> DEFAULT_MACRO _STRICT_FFS_1 Yes
> GUI CHOICE _STRICT_FFS_1 yes%no Apply strict schema:
> FFS_1_STRICT_SCHEMA $(_STRICT_FFS_1)
>
> ...which will add it as a GUI option to the navigation pane.
>
> NB: This does depend on the FFS writer being the only one (or at
least
> the first one) within the workspace. If there is more than one FFS
> writer be sure to change the "FFS_1" part to "FFS_x" where x is the
> writer number.
>
> Hope this helps,
>
> Regards,
>
> Mark
>
> Mark Ireland, Senior Product Specialist
> Safe Software Inc. Surrey, BC, CANADA
> [EMAIL PROTECTED] http://www.safe.com
> Solutions for Spatial Data Translation, Distribution and Access
>
> --- In [email protected], "sttav2003" <stefaan.tavernier@> wrote:
> >
> > With one translation I made ffs-files, but I abbreviated the
> > attributenames in these files. When I load these files in
another
> > workbench, I can see the abbreviated attributes and the old full
> > names, which shouldn't be in there. And when I load the files,
> > attributes from a couple of features are automattically copied
onto
> > other features in the files. Has anyone had the same problem,
or
> > possible solutions?
> >
> >
> > sincerely,
> > Stefaan
> >
>
thanks.
The problem of the overwriting was caused by the group-by option in
the bufferer, apparently, all features got the attributes of one
group-element. It seems this is a change since 2006 GB?
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/
