FME Desktop Tutorial
FME Desktop Tutorial
Desktop
Data Sources
City of Vancouver
Unless otherwise stated, the data used here originates from open data made available by the City of Vancouver, British
Columbia (data.vancouver.ca). It contains information licensed under the Open Government License - Vancouver.
Others
Forward Sortation Areas: Statistics Canada, 2011 Census Digital Boundary Files, 2013. Reproduced and distributed on an "as
is" basis with the permission of Statistics Canada. This data includes information copied with permission from Canada Post
Corporation.
Digital Elevation Model: GeoBase
Fire Hall Data: Some attribute data adapted from content 2013 by Wikipedia
(http://en.wikipedia.org/wiki/Vancouver_Fire_and_Rescue_Services), used under a Creative Commons Attribution-ShareAlike
license
Stanley Park GPS Trail: Used with kind permission of VancouverTrails.com. See
http://www.vancouvertrails.com/trails/stanley-park/.
Copyright
20052015 Safe Software Inc. All rights are reserved.
Revisions
Every effort has been made to ensure the accuracy of this document. Safe Software Inc. regrets any errors and omissions that
may occur and would appreciate being informed of any errors found. Safe Software Inc. will correct any such errors and
omissions in a subsequent version, as feasible. Please contact us at:
Safe Software Inc.
Phone: 604-501-9985
Fax: 604-501-9965
Email: [email protected]
Web: www.safe.com
Safe Software Inc. assumes no responsibility for any errors in this document or their consequences, and reserves the right to
make improvements and changes to this document without notice.
Trademarks
FME is a registered trademarks of Safe Software Inc. All brand or product names are trademarks or registered trademarks of
their respective companies or organizations.
Document Information
<ReleaseYear>.<MajorVersion>.<MinorVersion>.<BuildNumber>
Contents
Introduction
Training Pathway
FME Version
Contents
What is FME?
10
In this chapter
10
11
12
16
Getting Help
20
Conclusion
21
22
In this chapter
22
22
23
FMEWorkbench
27
31
Conclusion
38
39
40
Transformers
49
51
Conclusion
59
60
Content Transformation
60
61
Conclusion
72
73
In this chapter
73
Coordinate Systems
73
Data Reprojection
73
75
Dynamic Workspaces
81
82
Conclusion
84
Introduction
This tutorial is a recommended part of all the FME Training
Pathways
Training Pathway
This tutorial is a basic introduction to using FME and is part of the FME Training Pathway
system.
No prior knowledge of FME Desktop is required to follow its instructions.
FME Version
This tutorial specifically covers the use of FME Desktop 2015 edition. Older versions of FME
may not have some of the functionality described in this tutorial.
Contents
This tutorial consists of five individual chapters. Each chapter has its own topic and exercises.
The FME Desktop installation DVD includes a set of movies which cover each chapter of this
tutorial. They can be accessed on the disk by browsing to the folder Tutorial.
Data Inspection
This chapter explains what sample data is required for this tutorial, and where to download it
from. It also covers viewing the sample data in the FMEData Inspector.
Format Translation
The first task for most new FME users is translation of spatial data from one format to another.
This chapter shows how to quickly translate data between different formats, using both the FME
Quick Translator and FME Workbench.
Data Restructuring
Format translations are much more effective when they can be customized to produce output
data in a particular structure. This chapter explains how to use FME Workbench to go beyond
quick translation, and produce data in a structure that can be used seamlessly by the end user.
Introduction
Content Transformation
Data Transformation in FME can go further than simple restructuring, and include manipulating
the actual content of data during a format translation. This chapter covers using FME
Workbench to transform spatial and attribute components, demonstrating FMEs ability to add
significant value to translated data. It also covers how to translate more than one format of
data simultaneously.
Data Reprojection
In order to be able to share spatial data, it is often necessary to reproject that data into a more
suitable coordinate system. This chapter shows how to reproject data within FME Workbench,
and also demonstrates how to handle multiple source files using a Dynamic schema.
Introduction
Introduction to FME
FME is a spatial data transformation platform that helps
organizations more easily overcome a range of spatial data
interoperability challenges. It is available in both desktop and
server solutions.
What is FME?
FME enables both Translation and Transformation of spatial data to overcome the twin barriers
to interoperability:
l
Data Format
FME is classified as a Spatial ETL (Extract-Transform-Load) tool, designed to help users master
more spatial data transformation challenges than any other technology.
l
Introduction
With Data Transformation, the output from an FME process can be tailored to match a required
structure, and can even be greater than the sum of the inputs.
The key FME Desktop application is FME Workbench, an intuitive point and click interface for
graphically defining translations and transformations as a flow of data.
FME Quick Translator is an application for carrying out basic, non-customized translations.
FME Data Inspector is an application for visually inspecting spatial data.
Introduction
Further information on all training options is available on the Safe Software web site at
www.safe.com/training.
Many other resources for FME Desktop technical information can be located through the
FMEpedia knowledgebase at http://fmepedia.safe.com.
Introduction
In this chapter
l
Getting Help
Carrying out the exercises in this tutorial requires a set of sample data available from either the Safe
Software web site or the installation DVD.
Follow these steps to download and install the FME sample dataset from the Safe Software web site.
1) Open a web browser and visit: http://www.safe.com/fmedata.
2) There are two datasets available. One is a full dataset with nearly 500mb of example data. The
other is a 100mb subset specifically for the FME Desktop and Server tutorials.
The Tutorials dataset is all you need to complete the exercises in this document; however the Full
dataset has a wider range of formats and data types that you may find useful to experiment with.
Click the correct link to download your chosen set of FME sample data.
3) Download the file and extract its contents. Where possible, choose the root folder of the C:\ drive
to extract the data.
Document v
10
Choosing a different location than C:\ will not prevent you from using this tutorial, but
predefined translations within the FMEData folder will require editing to locate the data.
Document v
11
Data
Overall Goal
View city parks and parcel data overlaid onto a raster image and inspect the data
Demonstrates
3) To specify the source data format, click in the Format field and start typing "mapi."
A filtered list of formats appears.
When MapInfo TAB (MITAB) appears in the list, press Enter or click to select it.
Alternatively, the source format can be defined by clicking on the Browse button at the right of the
Format field, and using the Reader Gallery dialog box.
4) To select the TAB data to view, click the Browse tool (the [] icon for the Dataset field).
Document v
12
In the file browser, navigate to, navigate to C:\FMEData2015\Data\Parks and select the Parks.tab
file.
5) Click OK to open the TAB file in the FME Data Inspectors display window.
The MapInfo TAB dataset is now open in the FME Data Inspector.
Inspecting Attributes
Follow these steps to inspect a spatial feature, and to view attribute and other information.
1) You can verify that this tool is activated in one of the following ways:
l
The
Place your cursor on the View window. When the letter i appears to the right of the cursor,
the tool is active.
Document v
13
Details about the feature are displayed in the Information window, on the right hand side of the Data
Inspector.
Notice that the Feature Information window displays: user attributes and FME format attributes, as
well as details about the features coordinate system, plus other information:
Document v
14
Also notice that the TableView window is a layout of the user attributes for all features in the Parks
layer, with the selected Park feature highlighted:
Document v
15
1) To add a dataset, on the Inspector toolbar click the Add (not Open) Dataset icon (
).
The equivalent menubar tool is found under File > Add Dataset.
The Select Dataset to Add dialog box appears.
2) Select the Autodesk AutoCAD DWG/DXF format.
3) In the Dataset field, click the dataset Browse button and navigate to
C:\FMEData2015\Data\Parcels.
4) Select the DWG file Parcels.dwg and click OK to accept the selection.
By selecting the format before the dataset, you can browse only those datasets that
correspond to the requested format. This narrows your search and makes it quicker to find
what you need.
The newly-added data appears above the original MapInfo Parks dataset.
Document v
16
6) In the Display Control Window (left side of Inspector), dragging the dataset icon
beside the
MITAB (city_parks) dataset can be used to move it above or below the properties datasets in the
display window.
Notice that the park features now appear above - and therefore obscure - the AutoCAD parcel data.
Document v
17
The FMEData Inspector can also add background maps to the display. Follow these steps to add a
background map.
7) Click Tools >FMEOptions on the menubar.
8) In the field for Background Format notice all of the different online mapping services that can be
used to provide background information. To use local data - as we will in this example - select Other
FMEFormats.
9) Set Format to GeoTIFF (Geo-referenced Tagged Image File Format). Browse to the folder
C:\FMEData2015\Data\Orthophotos and select all of the TIF files in there.
Background data - in this case raster - will be displayed. (It may take some time to render.)
Document v
18
Queried a feature
Document v
19
Getting Help
FME Workbench includes extensive, context-sensitive help. For assistance with a tool or format, click
the item and then press F1 to open the help system.
Further Resources
Below is a list of other technical resources to help you make the most of FME and FME Server.
Sales
To obtain an evaluation copy or for sales enquiries, please contact your Safe Software Account
Manager or [email protected].
Training
Safe Software offers a number of training courses in FME Workbench and FME Server. For more
information, see our website at http://www.safe.com/training.
Documentation
The FME Server Administrators Guide is available with every FME Server installation and online at
our website: FME Server Administrator's Guide (HTML).
Technical Resources
Many other resources for FME Desktop and Server can be located at http://fmepedia.safe.com.
Support
If you need assistance with the tutorial or have any other technical questions about FME Server,
please feel free to contact the FME support team through the contact form on their web site at:
www.safe.com/support.
Document v
20
Conclusion
Next Step
Now that you have completed this chapter, your next step in the FME learning program is to continue
to the next chapter: Format Translation.
Further information on all training options is available on the Safe Software web site at
www.safe.com/training.
Many other resources for FME Desktop technical information can be located through the FMEpedia
knowledgebase at http://fmepedia.safe.com.
Document v
21
In this chapter
l
FME Workbench
22
Data
Overall Goal
23
3) In the Reader Format field set the reader format as GML (Geography Markup Language).
4) Click the Browse button next to to the Reader Dataset field, and navigate to
C:\FMEData2015\Data\Boundaries.
5) Select the file CityGrid.gml. Click on Open to accept the file.
6) In the Writer Format field, select Esri Shape from the Writer Gallery.
7) Click the Browse button adjacent to the Writer Dataset field, and navigate to
C:\FMEData2015\Output\Tutorial.
24
9) Why not open the newly created Shape dataset in the FMEDataInspector to prove that the
translation has worked as expected and contains a grid of rectangular polygons?
25
Translated data from one format to another using the Quick Translator
26
FMEWorkbench
FME Workbench has two immediate advantages over the Quick Translator:
l
Before attempting to use Workbench, it will be useful to read this introductory information
about the application.
Workbench Interface
The FME Workbench user interface looks like this:
27
Be aware that windows can be moved and docked in different locations; therefore not
every installation of FME will have exactly the same layout.
28
File tools also let you run a translation (in one of three different modes), pause it, and
stop it.
Edit tools let you cut, copy, and paste objects, as well as undo and redo changes.
View tools let you explore the Workbench canvas. They include select, pan, zoom in,
zoom out, zoom to extents, and full screen.
The Launch Inspection Application tool launches the FME Data Inspector.
29
Align tools let you arrange a set of selected objects into horizontal or vertical groups.
Publish tools let you publish to and download workspaces from FME Server.
Many objects in Workbench have a context-sensitive menu with shortcuts to toolbar tools, and
can be opened by right-clicking the object.
30
Data
Overall Goal
31
To name the output, click the Browse button and navigate to C:\FMEData2015\Output\Tutorial.
In the File Name field of the Select File dialog, type the file name as Parks.gml and then click
Save.
Ensure that the Static Schema default option is selected, and then click OK.
The new workspace is now created. Workspace is the FME term for a translation created and
edited in FME Workbench.
32
The object on the left-hand side represents a layer to be read by the Reader (in this case a
MapInfo data table).
The object on the right-hand side represents a layer to be written by the Writer (in this case to
a GML layer).
As part of FME terminology, these objects are called Feature Types.
Multiple layers in the input or output would be represented by multiple feature type objects in
the workspace.
By default FME sets up the translation to replicate the source. As a result, the writer
feature type and its attributes have identical names to that of the Reader.
The lines between the reader and writer feature types are called Connections. They represent
the flow of data within the workspace.
l
The green arrows at the end of each connection are called Ports.
Ports on the right of an object are called Output Ports; on the left side, Input Ports.
5) To save the translation, click the Save button on the Workbench menu bar.
33
34
7) To inspect the translation output, right-click the writer feature type (GML:city_parks) and
choose the option Inspect.
35
The FME Data Inspector starts up and the Select Dataset to View dialog opens. Click OK.
36
This will open up the data for viewing within the FME Data Inspector.
37
Conclusion
Next Step
Now that you have completed this chapter, your next step in the FME learning program is to
continue to the next chapter: Data Restructuring.
Further information on all training options is available on the Safe Software web site at
www.safe.com/training.
Many other resources for FME Desktop technical information can be located through the
FMEpedia knowledgebase at http://fmepedia.safe.com.
38
In this chapter
l
Structural Transformation
Transformers
Structural Transformation
Transformation of data structure in FME is vital to produce data in a form that can be used
seamlessly by the end user, a key requirement for transparent data interoperability.
Examples of structural transformation are:
l
39
Data
Overall Goal
Demonstrates
Follow these steps to carry out a simple Data Transformation exercise using FME Workbench.
This exercise continues on from the exercise "Quick Translations in FME Workbench" from the
previous chapter. You may skip the first two steps if you have that workspace already open.
1) Select Start > All Programs > FME Desktop 2015 > FME Workbench from the
Windows start menu.
FME Workbench will launch, and the FME Workbench start tab appears.
CityParks.fmw will appear in the Recent Workspaces part of the Start tab.
2) Click on the link to open the workspace.
40
3) Click on the expand icons on both the reader and writer feature types to expand the list of
user attributes on these types.
The first task is to rename the destination attributes. Right-click on the writer attribute called
ParkName and choose the Rename option.
4) Enter Name as the new attribute name, and then press Enter.
41
Because FME is case sensitive, be sure to enter attribute and feature type names
exactly as they appear throughout this tutorial.
5) Repeat the process to rename a second attribute from ParkId to simply ID.
This overall process is called Schema Editing.
6) Another schema editing task is to add new attributes to a writer schema.
Click on the Settings button on the right-hand side of the writer feature type (GML:Parks).
42
Set the data type of ParkSize to xml_real32, by clicking on the Type field down arrow and
selecting that data type.
43
7) Repeat this process to create an attribute called "BikePaths", also of type xml_real32.
Then click OK.
44
45
9) Drag the created duplicate of the first feature type underneath the original feature type.
When the workspace is run there will now be two layers in the output GML dataset; although, no
action has yet been taken to actually separate the data.
10) To differentiate the output layers, rename the feature types as follows:
Click on the duplicate writer feature type (GML:Parks00). Then press the F2 key and change the
name to DogParks.
46
11) Click on the green arrow emerging from the MITAB:Parks Reader feature type, and then
drag a connection to the red arrow on the GML:DogParks Writer feature type.
12) Repeat the previous step, this time connecting the attributes ParkName to Name and
ParkId to ID.
47
48
Transformers
Besides schema editing and schema mapping, transformation can also be carried out using
blue-colored objects in FME Workbench called Transformers.
Transformation occurs as the data is passed from reader to writer through a series of these
transformers.
There are approximately 500 different transformers available within Workbench and the
FMEStore.
You may already have seen a transformer in a prior workspace, since FME
sometimes inserts a GeometryFilter transformer automatically in a new workspace.
This allows FME to perform the restructuring necessary for translation to a specific
format.
Transformer Info
A parameters button is located on the top right of a transformer. This button appears as a cog
wheel whose color defines its status.
49
Many transformers have mandatory parameters that must be set. Luckily the majority contain
default values that will be acceptable. A yellow parameters button indicates the transformer is
using default values for any mandatory fields.
The workspace will run, but it is recommended that you confirm the default values are correct
for your needs before starting the translation.
When the parameters button is red it means that one or more mandatory fields do not have
defaults. In this case, a value must be set before the translation can be run.
A parameters button whose color matches the transformer (usually light blue) indicates that all
parameter values have already been checked and accepted.
Some transformers (like this Joiner) have extra decoration. This is to indicate transformers
that are fetching data into the workspace or sending data out of it.
50
Data
Overall Goal
51
At the moment, the workspace is duplicating data due to the connections from the Reader to
two different Writer feature types.
Therefore, the first task involves filtering out data into one feature type or another. This can be
done using a Tester transformer.
52
1) Click in a blank space on the Workbench canvas. Start typing the characters "test." A list of
matching transformers will appear.
2) Select the transformer named Tester. The transformer is dropped onto the Workbench
canvas window.
3) Now the transformer must be set into the correct position. Click on the transformer and
start to drag it. A pink marker will appear in the top-left corner of the transformer.
4) Drag the transformer so the pink marker is on top of the connection between the
MAPINFO:Parks Reader feature type and GML:DogParks Writer feature type as shown (here
with the attribute list collapsed).
53
The connection will become highlighted to confirm that the transformer is in the correct
position.
5) Drag a new connection between the Tester:Failed port and the GML:Parks Writer feature
type.
6) Click on the existing connection between MITAB:Parks and GML:Parks.Then press the Delete
key to remove it.
54
Because overlapping connections are frowned upon in a workspace, re-arrange the workspace
objects to avoid this (as shown). In effect, the two Writer feature types swap positions.
Notice that the attribute ports belonging to the FAILED features are yellow. This is
because FME cannot identify an automatic connection. When arrows are yellow like
this, the values will be dropped when the workspace is run.
55
The next task consists in setting up the test to be carried out by the Tester. The test will check
if the DogPark field is set to "Y" (meaning "Yes").
7) Click on the parameters button for the Tester (it should be red). A Tester Parameters dialog
box will open.
8) In the Test Clauses section, double-click the Left Value field, click the drop-down arrow,
choose "Attribute Value" and select the attribute DogPark.
56
10) Save the workspace, so it can be reused later on, but don't run it yet.
Output from a workspace can be inspected, without actually writing a new dataset, by using a
redirect option.
11) Click the menu bar option Writers > Redirect to FMEData Inspector.
12) Run the workspace. The data will be divided into two output layers and sent to the FME
Data Inspector as a preview.
If the Tester is set up correctly, then the feature counts in the completed workspace will show
that 80 features were read from the Parks dataset, of which only seven (7) had off-leash dog
areas and the remaining 73 did not.
57
The feature count display shows how many features passed through each link. The
display continuously updates as features pass through the workspace. This function
helps analyze the results of a workspace, and provides a reference for debugging if
the destination results or performance are not what you expected. Feature counts
are also written to the Log file but you can find the references more quickly on the
links in a workspace.
To enable feature count display, click the Display Feature Counts tool
on the
toolbar or click Tools > FME Options > Workbench and check Display feature
counts. Click the tool again to turn off feature counts (although you will have to run
the workspace again to refresh the display).
13) Select the same menu bar tool again to turn off the redirect option. Run the workspace
again to create the correct output.
58
Conclusion
Next Step
Now that you have completed this chapter, your next step in the FME learning program is to
continue to the next chapter: Content Transformation.
Further information on all training options is available on the Safe Software web site at
www.safe.com/training.
Many other resources for FME Desktop technical information can be located through the
FMEpedia knowledgebase at http://fmepedia.safe.com.
59
In this chapter
l
Content Transformation
Content Transformation
Transformation of data content occurs when the spatial or attribute components of a dataset
are manipulated.
Examples of content transformation are:
l
60
Data
Overall Goal
Measure the area of each city park, and the total length of bike path that runs
through each one.
This is the final step in a project to create data suitable for analysis by a
Grounds Maintenance team.
61
To measure the area of each park feature, an AreaCalculator transformer must be used.
Calculator is the term used for transformers that compute new attribute values.
3) In the Workbench canvas, click on the connection between MITAB:Parks and the Tester.
5) Select the AreaCalculator transformer. The transformer is dropped automatically into place.
Re-arrange the workplace objects to avoid overlapping connections:
Notice that even though the area of each park is being calculated, the ParkSize attribute is not
receiving that information.
62
Thats because the AreaCalculator records its information in a default attribute called _area.
The new attribute (_area) can be manually mapped to ParkSize, but there is a better way.
6) Click the yellow-colored parameters button on the AreaCalculator transformer to open up
the parameters dialog box.
The Area Attribute parameter defines the attribute to receive the calculated area.
Click in the Area Attribute field, and rename the attribute as ParkSize to match the name of the
writer feature type definition. Then click OK.
Now FME can automatically map the measured area to the correct schema attribute.
63
The next transformation requires bike path information to calculate the length of bike path per
park. Because this information is held in a separate dataset, it is necessary to add a new
Reader to the workspace.
7) Select Readers > Add Reader from the menu bar.
8) When the Add Reader dialog box opens, fill in the format field as follows and then select the
three specified Shape files:
Format
Datasets
Esri Shape
C:\FMEData2015\Data\Transportation\Cycling\BikePaths_L.shp
C:\FMEData2015\Data\Transportation\Cycling\BikePaths_M.shp
C:\FMEData2015\Data\Transportation\Cycling\BikePaths_S.shp
64
Calculating the length of bike path that runs through each park requires that the bike path
features are clipped to the park extents. This can be done with a Clipper transformer.
9) Click on a blank area of the Workbench canvas and start typing letters to match the Clipper
transformer name (e.g. "clip")
The Quick Add list of matching transformers appears beneath.
Select the Clipper transformer.
10) Drag connections between the SHAPE:BikePaths Reader feature types and the
Clipper:Clippee port.
11) Drag a second connection from the MITAB:Parks Reader feature type, onto the
Clipper:Clipper port.
The first section of workspace will now resemble this layout:
65
12) Click on the Clipper transformer parameters button to open the Clipper Parameters dialog
box.
Set the Clipper Type parameter to Multiple Clippers (or ensure it is already set) and click OK.
The next task involves measuring the length of the remaining streams.
13) Click on the yellow arrow of the Cllippee:Inside output port. It will be highlighted in orange
to confirm its selection.
14) Start typing a match for the LengthCalculator transformer. "Length" or "thcal" would both
work. The Quick Add list of matching transformers appears beneath.
15) Select the LengthCalculator transformer. The transformer will be added to the workspace
and connected to the correct Clipper port. The parameters for this transformer can be checked,
but the defaults shouldnt need changing.
66
Now that the length of each path is being calculated, it needs to be added to the park features
using an "overlayer" transformer. An overlayer transformer carries out a form of spatial join
upon the data.
Since bike path features are lines, and park features, areas, the LineOnAreaOverlayer is the
transformer to use.
16) Click on a blank area of the Workbench canvas and start typing the letters "overlay." The
Quick Add list of matching transformers appears beneath.
Select the LineOnAreaOverlayer transformer.
67
68
The path lengths in the list need to be summed up, to use as a single result. This can be done
with a ListSummer transformer.
21) Click on the LineOnAreaOverlayer:Area output port. It will be highlighted in orange to
confirm its selection.
Start typing the letters "sum." The Quick Add list of matching transformers will appear
beneath.
Select the ListSummer transformer. The transformer will be added to the workspace and
connected to the LineOnAreaOverlayer:Area port.
69
22) Open the ListSummer Parameters dialog box. Select the MyList{}._length as source list
attribute. To match the destination feature type schema, rename the Sum Attribute name to
BikePaths.
Click OK.
23) Drag a connection from the ListSummer:Output port to the Tester:Input port.
Notice that the BikePaths attributes on the Writer feature types now have a green input arrow,
indicating they are properly connected and receiving data.
24) Delete the existing connection between the AreaCalculator and the Tester transformer and
rearrange the transfomers to straighten out connections and ensure as few connections overlap
as possible.
25) Check and reconnect any attributes whose schema mapping has been lost (there shouldn't
be any, but you should check). Then save the workspace, run it, and inspect the output dataset.
70
All features will now have a value for ParkSize and BikePaths, and will be divided into Parks
and Dog Parks.
This information will let the planning department calculate grounds maintenance costs for the
coming year.
71
Conclusion
Next Step
Now that you have completed this chapter, your next step in the FME learning program is to
continue to the next chapter: Data Reprojection.
Further information on all training options is available on the Safe Software web site at
www.safe.com/training.
Many other resources for FME Desktop technical information can be located through the
FMEpedia knowledgebase at http://fmepedia.safe.com.
72
In this chapter
l
Coordinate Systems
Data Reprojection
Dynamic Workspaces
Coordinate Systems
Usually coordinate systems are associated with the term map projection; however, they also
involve:
l
Datum
Units
Spheroid
Ellipsoid
Scale Factor
Data Reprojection
Reprojection can be considered a form of Data Transformation, but one which is unique enough
to deserve its own section.
Reprojection occurs naturally in FME whenever a destination coordinate system is specified
that is different to the source coordinate system.
Coordinate systems are specified in the Workbench Navigator window. The destination
coordinate system is specified by the user, whereas the source coordinate system can be
specified either by the user or within the dataset itself.
73
74
Data
Overall Goal
Demonstrates
Follow these steps to carry out a simple reprojection exercise using FME Workbench.
1) Select Start > All Programs > FME Desktop 2015 > FME Workbench from the
Windows start menu.
FME Workbench will launch, and the start screen appears.
2) Open the Generate Workspace dialog box, either through the Generate Workspace link on
the Start tab, or by using the shortcut ctrl-G.
3) In the Generate Workspace dialog box, fill in the Reader format field as EsriShape
Click the dataset browse button and browse to C:\FMEData2015\Data\Transportation\Cycling.
In the file browser select all three of the files with a .shp extension.
75
Then click the Open button to accept these files as the workspace input.
4) Back in the Generate Workspace dialog box, fill in the Writer fields as:
Format
Dataset
Esri Shape
C:\FMEData2015\Output\Tutorial
Notice that the workspace is reading and writing using the same format, which
implies that this is solely a data transformation process, with no format translation.
This is a very common use for FME.
5) In the Workflow Options section, ensure the Dynamic Schema option is checked.
76
The new workspace is created and can be set up to reproject the data.
7) Click on the connection between the source (Reader)Feature Type and the destination
(Writer) Feature Type. Start typing the word "Csmap." When the CsmapReprojector (not
CsmapAttributeReprojector) appears, click on it to insert an instance of this transformer into
the canvas.
77
8) Click on the parameters button for the CsmapReprojector (it should be red). A parameters
dialog box will open. In the Destination Coordinate System parameter, enter "LL83." Leave the
Source Coordinate System as "<Read from Feature>."
This will cause the data to be reprojected from its original coordinate system to a LatitudeLongitude system with a datum of NAD83.
9) Save the workspace as BikePathReproject.fmw, and then run the translation.
Check the output folder to show that all of the files have been translated.
78
10) Inspect one of the output files. One way to do this is to drag and drop a Shapefile from a
file explorer directly into the FME DataInspector.
NB: You only have to select the SHP file (the parent) rather than all files in the dataset. This is
the same for any multi-file dataset.
11) In the FME Data Inspector, query a feature to verify that the data has been reprojected to
the new coordinate system. The coordinate system for a queried feature is displayed near the
top of the Information window.
79
12) Click on the coordinate system (it is a hyperlink) to open a dialog showing the coordinate
system properties:
80
Dynamic Workspaces
The prior example used the dynamic schema option.
It would have worked just as well with a static schema, but dynamic has two major
advantages.
l
Dynamic schemas are powerful and make possible a huge number of different data
interoperability scenarios; far more than will be covered in this tutorial.
Novice FME users are advised to use static workspaces when carrying out structural
transformations, as data restructuring techniques are different in dynamic mode.
Dynamic schemas are easier to implement when the workspace is intended for
format translation only, or transformation of spatial content such as reprojection or
clipping.
81
Data
Overall Goal
Demonstrates
Reusable workspaces
82
83
Conclusion
Next Steps
Now that you have completed this tutorial, your next step in the FME learning program offers a
number of different choices. You may either follow a specific path by studying a tutorial such as
FME for Raster Data, or go directly on to the FME Desktop Basic Training course.
84
You might also check out the FME Server tutorial, to find out the basic uses of that product.
Further information on all training options is available on the Safe Software web site at
www.safe.com/training.
Many other resources for FME Desktop technical information can be located through the
FMEpedia knowledgebase at http://fmepedia.safe.com.
85