We update hundreds of shapefiles quarterly. The data we use comes from many sources, but we transform all the data of a single type into a standardized "Master" schema for that type (for example we get Parcel data from 70 counties, each having their own schema, and we translate and transfer that data into a standardized "MasterParcel" file). Using the above example we currently use 70 different workspaces containing 70 different instances of AttributeManager. To hopefully make this process much more efficient, we have developed is a database table containing rows like "ProviderSourceTable", "SourceAttribName", "SourceAttribType", "SourceAttribLength",...."TargetLayer", "TargetAttribName","TargetAttribType".... basically all the data AttributeManager needs to do the job for each data provider/data type combination. The only problem is we cannot figure out how to use this data to dynamically populate AttributeManager. If this is possible it would be HUGE for us, so any help would be greatly appreciated. P.S. We have scripting experience, but are relatively new to FME.
+31- Influencer
This sounds like a use-case for the SchemaMapper. It uses an external file as source for mapping the schema, instead of having to maintain those change rules in transformers. That would be the first place I start. But to answer your question, you can import attributes into the AttributeManager. But in my opinion, it's going to be much more cumbersome updating 70 AttributeManagers, opposed to updating an excel file that could potentially be used in a single SchemaMapper.
Reply
Rich Text Editor, editor1
Editor toolbars
Press ALT 0 for help
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.