Questions
Here are the answers to the questions in this chapter.
| Miss Vector says... |
|
For each of these scenarios, tell me if it is a Data Download project, Data Upload, both, or neither.
1. The user logs on to a web page, draws an area on the map, and is sent a copy of the data within that area: Data Download 2. The user submits a dataset to a web site that scans the data for errors, and returns a corrected copy: Both Data Upload and Data Download 3. The user publishes a workspace that writes data to the user's account in an online PostGIS database: Neither Data Upload or Data Download 4. The user starts a GIS application, clicks File > Add Data to Map, and pastes in a URL from FME Server: Data Download #1 is a simple download of data. #2 is obviously both. #3 is neither. Publishing a workspace is not Data Upload and writing to a database is not Data Download. #4 would be a special type of Data Download. In FME we call it Data Streaming; the workspace runs and the output is sent directly to the application that requested it. |
| Miss Vector says... |
|
When a workspace is not registered against any service, how can you run it? Select all that apply.
1. With the FMEServerJobSubmitter transformer 2. With the run dialog in the web interface 3. With the URL specified under Developer Information in the run dialog 4. By setting it to run under a schedule You cannot run the workspace in the web interface (the run button won't work unless services are available) or with a URL (none will be provided). |
| Miss Vector says... |
|
When a workspace is registered against the Data Download service (and no other), how can you run it? Select all that apply.
1. With the FMEServerJobSubmitter transformer 2. With the run dialog in the web interface 3. With the URL specified under Developer Information in the run dialog 4. By setting it to run under a schedule It will actually run under all of these tools. Of course, only the web dialog and the URL return a zip file for download. The others just output the data to the specified workspace location. |
| Miss Vector says... |
|
How well do you know the types of FME published parameters? Decide which of the following are real parameters, and which are fake.
1. Color: Real 2. Double: Fake 3. Password: Real 4. Text (Multiline): Real |
| Miss Vector says... |
|
Let me throw an easy question at you! If the Generic Writer parameter is published to determine what format to write data in a data download system, what would the Generic Reader parameter be used for?
1. To determine what format of data to read in a Data Download system 2. To determine what format of data to read in a Data Upload system 3. To determine the correct Styler transformer to use in the workspace 4. To determine whether I'm connected to a Data Upload or a Data Download system Right, I'm uploading some data and I'm going to tell FME Server what format it is. Why would I care (#1) about what format of data is being read in a Data Download system (and how could I tell)? Similarly (#3) it's the output format that determines which Styler to use, not the input format. #4 is just plain nonsense! |
| Miss Vector says... |
|
Why is the FeatureReader the preferred option [for filtering data in a self-serve system]? Pick all the reasons that apply:
1. It can be quicker and more resource efficient 2. It allows multiple areas to be used as the existing areas 3. It work with raster data 4. It has more choices for spatial filtering The FeatureReader is more efficient where the source dataset is a format that has a spatial index, because it won't have to read all of the source data. It also has more filtering choices than a Clipper transformer (though not a SpatialFilter) The FeatureReader does allow multiple areas to be used, and it does support raster data - however so does the Clipper transformer, so there is no difference between the two in those scenarios. Additionally, the two are equivalent in performance where there is no spatial index (i.e. both will need to read the full dataset) |
| Miss Vector says... |
|
If the incoming geometry string is XML, there is a shortcut [to passing/using it in a workspace]. What is it?
1. Use an XML Reader with the source dataset parameter published 2. Publish the source dataset parameter in the FeatureReader to send the XML straight into it 3. Replace the GeometryReplacer with an XMLTemplater 4. Use a Creator transformer with the geometry parameter published If you publish the geometry parameter in a Creator transformer you can pass XML directly into it and FME will automatically generate a spatial feature from it. This removes the need for any AttributeManager and GeometryReplacer transformers. |