Questions
Here are the answers to the questions in this chapter.
| 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 works 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. |