# Form Basics - Exercise 1

<table><thead><tr><th width="176">Exercise Details</th><th>Opening and Running a Workspace</th></tr></thead><tbody><tr><td><strong>Locality</strong></td><td>Melbourne, Australia</td></tr><tr><td><strong>Data</strong></td><td>Bicycle Network (GeoJSON)<br>Property Boundaries (Esri Shapefile)</td></tr><tr><td><strong>Overall Goal</strong></td><td>To open and run an FME workspace to explore what it can do with data</td></tr><tr><td><strong>Demonstrates</strong></td><td>Opening and running a workspace</td></tr><tr><td><strong>Start Workspace</strong></td><td>C:\FMETraining\Workspaces\FormBasics-Ex1-Begin.fmw</td></tr><tr><td><strong>End Workspace</strong></td><td><em>None</em></td></tr></tbody></table>

Rather than trying to explain what FME is and does, let us try it for ourselves! In this exercise, you will explore a workflow to integrate and transform data to create a Google KML file that provides a bicycle route that can be taken to visit the main parks in Melbourne, Australia. This workflow works with spatial and attribute data.

***

{% stepper %}
{% step %}

## Locate Workspace File

When translations and transformations are defined in FME, they can be saved in a .fmw file.

Using a file explorer, browse to: **C:\FMETraining\Workspaces\FormBasics-Ex1-Begin.fmw**

<figure><img src="/files/b6FYbuddLqOZkVv1v7K5" alt=""><figcaption></figcaption></figure>

Double-click on the file. It will open an application called FME Workbench.
{% endstep %}

{% step %}

## Explore FME Workspace

When FME Workbench opens you will see the option of viewing the Workbench Essentials tutorial. You can complete this now if you wish, or view it later under Help > Workbench Essentials. For now, click the X to close the window.

The main part of the application will look like this (click to expand):

<figure><img src="/files/wlCs39pKrsa8IrzW7OkX" alt=""><figcaption></figcaption></figure>

This part we call the canvas. It is where the translation and transformation of data is defined graphically. Although it might look complicated, it does not take much practice with FME to create workflows of this type.

Examine the left-hand side of the canvas:

<div align="left"><figure><img src="/files/m55lGABIkpXhxFRMTayC" alt=""><figcaption></figcaption></figure></div>

This area is where we read data, in this case, Property Boundaries from a Shapefile and Bicycle Path data from GeoJSON files (the bicycle network and the property centroids).

Now, look at the right hand side:

<div align="left"><figure><img src="/files/ZO3RYhLTuSZiDWZnw0yC" alt=""><figcaption></figcaption></figure></div>

This area is where we write data, in this case, a KML file showing a bicycle path between certain properties.

In between the reader and writer are objects that transform data.\
Labels and other annotations show us what the workspace does. It:

* Reads both Property Boundaries (Shapefile) and the Bicycle Paths (GeoJSON).
* Joins a list of parks to filter the property boundaries to known parks.
* Calculates the shortest bicycle path taking in all parks
* Creates KML Styling for the park areas and the calculated path
* Writes the data to a KML file to be used with Google Earth

{% hint style="info" %}
**NOTE**

*Let's make sure we are clear on terminology. The application itself is called FME "Workbench," but the process defined in the canvas window is called a "Workspace." The terms are easily confused.*
{% endhint %}
{% endstep %}

{% step %}

## Ask AI Assist (Optional)

Another way to learn about the workspace is to utilise the AI Assist utility.

Open the utility by locating the **AI Assist** button on the toolbar:

<figure><img src="/files/VmAXrBUHeEVg68dlr3pz" alt=""><figcaption></figcaption></figure>

Any questions that you may have about the workspace can be posed to the AI Assistant here, such as "What does this workspace do?":

<figure><img src="/files/MgKsDTkIpeDyVgnTP6nz" alt=""><figcaption></figcaption></figure>

The AI Assistant should provide a response that helps understand the workspace and its functionality in response:

<figure><img src="/files/vpLyKcukmgzkAHjufirJ" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**NOTE**

*As is the nature of AI, the assistant may be subject to varying answers for individuals and hallucinations. Whilst extremely helpful, a healthy scepticism should always be applied to responses, where possible.*
{% endhint %}
{% endstep %}

{% step %}

## Run FME Workspace

Let’s run this workspace.

Click on the green Run button on the Workbench toolbar:

<figure><img src="/files/uTFFYuVJJ5l3m4NthXXF" alt=""><figcaption></figcaption></figure>

The workspace will now run. As it does, you will see messages pass by in a log window. You may also see numbers appear on the canvas connections and green annotated icons on each object. We'll get to what these are for later!

{% hint style="info" %}
**NOTE**

*You may be prompted by a pop-up dialog box after running the workspace. By default, a feature called **Prompt for User Parameters** is turned on. We don't need this on for this course, so if prompted, turn it off by clicking the dropdown arrow next to the Run button the toolbar, and clicking Prompt for User Parameters*

<img src="/files/Dlkqrf7RLfp14F9WbU2A" alt="" data-size="original">
{% endhint %}
{% endstep %}

{% step %}

## Locate and Examine Output

Once the translation is complete, click on the KML writer object on the canvas. It is located on the right side of the workspace and is labelled **ParksBikeRoute**. Choose the option to Open Containing Folder:

<figure><img src="/files/j2kpTcDjHwNuKLl11mHq" alt=""><figcaption></figcaption></figure>

In the Explorer dialog that opens you will find the KML output:

<figure><img src="/files/mEtFBiq8UR4skOzD93tG" alt=""><figcaption></figcaption></figure>

Open the output file created by FME with "Data Inspector" (right click and open with). You will see the parks that are visited highlighted as green areas and the bike path taken to visit all of them as a red line:

<figure><img src="/files/4EBjRwN6KTwUOIAk5rkk" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**NOTE**

*This small demonstration illustrates the power of FME. This workspace read data from multiple spatial datasets and wrote it out to a KML file.... to be used in Google Earth. In between it carried out a series of transformations and spatial analyses, joining and reprojecting the data and creating added value and information.*
{% endhint %}
{% endstep %}
{% endstepper %}

***

{% hint style="success" %}
**CONGRATULATIONS**

*By completing this exercise, you have learned how to:*

* *Open an FME Workspace*
* *Run an FME Workspace*
* *Locate the output from an FME Workspace*
  {% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://1spatial.gitbook.io/fme-form-beginner/form-basics/data-translation/form-basics-exercise-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.