> For the complete documentation index, see [llms.txt](https://1spatial.gitbook.io/fme-form-beginner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://1spatial.gitbook.io/fme-form-beginner/form-basics/fme-form/creating-a-translation.md).

# Creating a Translation

Workbench’s intuitive interface makes it easy to set up and run a simple format-to-format ('quick') translation.

## The Start Tab

The Start Tab in FME Workbench includes several options to get started, such as starting a new workspace, opening an existing one and looking at official and community examples.

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

Additionally, it comes with quick options to get connected to FME Flow and use the AI Assistant (we will discuss this soon).

However, there is another great option (especially as a beginner) to be aware of: **Generate Workspace**

## Generate Workspace

The **Generate Workspace** option provides the options for reading in and writing out your data, all in one handy dialog. It has fields for the defining the format and location of both the input and output.

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

Red colouring in an FME dialog indicates mandatory fields. Users must enter data in these fields to continue. In most dialogs, the OK button is deactivated until the mandatory fields are complete.

### Format and Dataset Selection

A key requirement is the format of the source data. All format selection fields in FME are both a pull-down menu and a text entry field.

The text entry field allows you to type a format name directly. It has an 'intelli-complete' function that selects close matches as you type.

The drop-down list shows some of the most commonly used formats, so many favourite formats are instantly available:

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

Click 'More Formats' and a table opens showing all of the formats supported by FME in the Reader and Writer Gallery.

The source dataset is another key requirement. Dataset selection fields are a text entry field, but with a browse button to open an explorer-like dialog for file selection.

Similarly, the Writer format and dataset are defined in this dialog:

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

Clicking OK on the Generate Workspace dialog causes FME to generate the defined workspace. However, whenever a source dataset contains multiple **feature types**, the user is first prompted to select which are to be translated.

This is achieved through the Select Feature Types dialog. Feature type is the FME term that describes a subset of records. Common alternatives for this term are layer, table, sheet, feature class, and object class. For example, each sheet in an Excel workbook, table in a database, or layer in a spatial data file is defined by a feature type in FME. Only feature types selected in the Select Feature Types dialog will be added to the workspace:

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

Here, for example, is a Select Feature Types dialog where the user has chosen to include all available layers in the workspace.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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/fme-form/creating-a-translation.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.