Schema Mapping is the second key part towards data restructuring in FME.
In FME Workbench, one side of the workspace shows the source schema ("what we have") and the other side shows the destination schema ("what we want"). Initially the two schemas are automatically joined when the workspace is created, but when edits occur then these connections are usually lost.
Schema Mapping is the process of connecting the source schema to the destination schema in a way that ensures the correct reader features are sent to the correct writer feature types and the correct reader attributes are sent to the correct writer attributes.
In FME, it is permitted to do this mapping in any way that is desired.
|Ms. Analyst says...|
Hi. I'm Ms. Analyst, one of your colleagues at the city. I think of Schema Editing and Mapping as a means of reorganizing data.
A good analogy is a wardrobe full of clothes. When the wardrobe is reorganized you throw out what you no longer need, reserve space for new stuff that you’re planning to get, and move existing items into a more usable arrangement.
The same holds true for spatial data restructuring: it's the act of reorganizing data to make it more usable.
In Workbench’s intuitive interface, the most common way to make feature type and attribute connections is by dragging connecting lines between these parts of the schema.
Feature mapping is the process of connecting source feature types to destination feature types.
Feature Mapping is carried out by clicking the output port of a source feature type, dragging the arrowhead across to the input port of a destination feature type, and releasing the mouse button.
Here, a connecting line from source to destination feature type is created by dragging the arrowhead from the source to the destination.
Merging and splitting of data is permitted. Here, a user wishes to create a single layer called Transportation and so is merging two input feature types (Roads and Rail) into one output feature type (Transportation).
Attribute Mapping is the process of connecting reader attributes to writer attributes.
Attribute Mapping is performed by clicking the output port of a reader attribute, dragging the arrowhead to the input port of a writer attribute, and releasing the mouse button.
Here feature mapping has been carried out already and attribute connections are being made.
Notice the green, yellow, and red color-coding that indicates which attributes are connected.
Green ports indicate a connected attribute. Yellow ports indicate a reader attribute that’s unconnected to a writer. Red ports indicate a writer attribute that’s unconnected to by a reader.
Feature mapping connections (or links) are shown with a thick, black arrow.
Attribute mapping connections are shown with a thinner, gray arrow.
Attributes with the same name in reader and writer are connected automatically, even though a connecting line might not be visible; the port color is the key.
Names are case-sensitive, therefore ROADS is not the same as roads, Roads, or rOADS.
That's important to know if you are relying on automatic attribute connections!