Question
Setting a format attribute dynamically in file based datasets
+46- Influencer
When writing to a file based dataset, i.e. each feature type is a layer within a dataset does it matter in which layer you set and expose a format attribute, e.g. map extents / viewport within a geosptial pdf, does it need to be repeated for each layer?
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+10What format are your writing to?
Feature Type in FME has to be understood in the context of the Reader/Writer you are using.
For a database FeatureType could be a table name, for a file like dgn it could be a level name and so on.
Cheers
Happy FME :-) ing
SRG
+10Looking at the Writer documentation for Geospatial PDF you will find that:
Adobe Geospatial PDF Writer Parameters The following are Writer parameters which will apply to all features in the Writer dataset:
Page Size Map Parameters Text Parameters Attribution Compression Compatibility
Map Parameters Specifies a rectangular region of space, in world coordinates, that will be mapped to the page viewport. Geometry outside the world viewport will be clipped when drawn on the page. The format for this option is four floating point numbers separated by spaces describing the lower left corner and the upper right corner of the rectangle. If a value is not specified, then the world viewport rectangle will be the bounding box of the entire dataset. Values: <lowerLeftX> <lowerLeftY> <upperRightX> <upperRightY>
Every component of a translation - workspace, reader, writer, feature type - has a set of parameters to control how it operates.
In the hierarchy of different translation components, each different level of the hierarchy has a set of parameters that belong to it. So there are: Workspace Parameters Reader Parameters Writer Parameters Feature Type Parameters Format Attributes (Feature Parameters)
Having parameters right down to the feature level provides a huge degree of control over every aspect of a translation.
In some formats there are some parameters which can be set both at Writer level and at Feature Type level (especially Database types).
Top-Down Effect: The basic rule is that any higher-level parameter affects every component below it. For example, a Workspace Parameter affects all Readers and Writers, all Feature Types that belong to those Readers/Writers, and all features that belong to the Feature Types. A Reader Parameter affects all Feature Types that belong to that particular reader, but not Feature Types belonging to another Reader.
Hope this clarification helps.
Happy FME-ing :-)
Cheers
SRG