- XML (Extensible Markup Language) Reader/Writer
- XML Quick Facts
- Workbench XML Reader Parameters
- Workbench XML Writer Parameters
- Feature Representation
- Mapping File Reference
- xfMap
- Reading the Input XML Document
- Mapping Rules
- Types of Mapping Rules
- Match and Except Expression
- Specifying Several Match Expressions for One Mapping Rule
- Limiting Mapping Rule Activation with Except Expressions
- Mapping Rule States (activation, execution, suspension, and de-activation)
- Using Force Elements During Mapping Rule Activation and Deactivation
- Search-sets
- Expression Elements (Extract and Literal)
- Expression Sequence
- Feature Mapping Rules
- FME Feature Construction
- Feature Type Element
- Attributes Element
- FME Feature Construction (defining mapping rules under the <feature-content-map> element)
- Attribute Element (handling multiple values)
- Attribute Element (handling optional attributes)
- Attribute Element (sequenced attributes)
- Attribute Element (Nillable Attributes)
- Geometry Element
- Geometry Builder States (activation, execution, suspension, and de-activation)
- Geometry Construction
- Composite Geometry Builders
- Built-in Geometry Builders
- Mapping Segmented Geometric Information
- Geometry Traits (trait element)
- FME Feature Construction (constructing multiple features at a time)
- Structure Element
- References Element
- Apply References Element
- Group Mapping Rules
- Reference Mapping Rules
- Mapping Rules (Optional Elements)
- More Expression Elements
- FME Schema Features
- Reading the Input XML Document
Composite Geometry Builders
Geometry builders that can integrate another geometry into their own are called composite geometry builders, those that do not are called non-composite. Note that the composite, non-composite qualifiers do not refer to the type of geometry that the builder constructs, instead, they refer to whether or not the builder is capable of integrating another geometry into its own.
Usually, the builders that construct aggregate geometries are composite geometry builders. One can envisage a custom non-composite geometry builder that builds an aggregate geometry. For example, if a multi-point feature in the input XML document is defined to be something like:
<multi-point dimension="2"> 2.3,34.9 445.4,34.34 23.35,345.453 </multi-point>
A custom geometry builder used solely to build an aggregate of point features out of the <multi-point> element does not need to be a composite geometry builder, since it does not need to accept a point geometry from other builders because the information for all of the point components are embedded in the <multi-point> element’s text content.