FME Translations Quiz

Which of the following statements is true about the Generate Workspace dialog?

You must define both the reader and writer format You must define the reader format, but writer format is optional The reader format is optional, but you must define the writer format Both the reader and writer formats are optional Generate Workspace requires both a reader and writer format. You can use leave the Format field blank (it will show <Guess from Dataset>) and FME will try to guess your format. However, you must still eventually supply a value to this field. In more advanced training courses, you can learn how to set a Generic reader or writer, which can use any format FME supports.

Visual Preview and FME Data Inspector are fully-functioned spatial data analysis and cartography tools.

True False Visual Preview and FME Data Inspector are not designed to replace GIS software, but rather to provide a quick and useful way to inspect the result of FME workspaces.

Which of the following scenarios would be well-suited to using feature caching? Check all that apply.

Reading from a large database Reading from a large web dataset Running a production workspace Running a simple workspace with a Creator and a single Emailer to send an email Using partial runs to incrementally develop a workspace with a complicated workflow

Workspaces that read large datasets or data that is slow to access, including databases or data on a network, can benefit from feature caching. Read the data once to cache it and then use Run From This or Run To This.

The initial process of feature caching takes longer than running the workspace without feature caching on, so it is not a good idea to keep feature caching on with a production workspace.

A very simple workspace with only one or two transformers, neither of which produce many features, will not benefit from feature caching.

Using partial runs with feature caching is a great way to quickly build and test sections of your workspace.

Which of the following is an example of schema editing or mapping? Check all that apply.

You create a workspace that removes observations from a CSV file if they are older than a target date. You create a workspace that joins customer data from a CRM to social media exposure data gathered by your Social Media Manager. You create a workspace that adds updated AutoCAD drawings to a centralized Esri ArcGIS geodatabase, removing three unwanted attributes and renaming two others in the process. You create a workspace that extracts a group of records from an Oracle database based on a spatial filter. Removing records (by an attribute value like observation date or spatial location) does not count as schema editing or mapping. Although the content of the written data is changed, its structure remains the same. In the CRM example, joining data adds new attributes. In the AutoCAD example, attributes are removed or renamed. These operations are schema editing, because you are changing the structure of the final dataset.

Why is the input port on the Date attribute of the writer feature type green?

The feature type's User Attributes tab did not appropriately define attribute parameters. FME is not connected to system date-time. The Date attribute on the reader feature type is not exposed. There is a Date attribute defined on the writer schema and it is receiving a value from the AttributeManager. In Exercise 2.4, we created a Date attribute on the writer schema by adding it to the User Attributes tab. At that point, it was red because it was not receiving a value from anywhere in the workspace. After that, we supplied it with a value by adding it to the AttributeManager. Even though the value is blank for now, the transformer is creating an attribute Date with a value, so it appears green on the writer feature type port.

results matching ""

    No results matching ""