Hot answers tagged

4

You can open the properties dialog (for the original writer) and use the Writer option there to move that table from one writer to the other. That way you don't have to copy from one table to another. As the above screenshot shows, it doesn't even need to be the same format. FME will automatically adjust the data types to match the new format. However, ...


2

Simple. Use the PointOnAreaOverlayer transformer. In the parameters dialog set a list name. The polygon features will emerge with a list of which point features fell inside, including their attributes. Then use a ListSummer transformer to add up the attribute X in that list. I put an example workspace (template) on Dropbox at: ...


2

Add an AttributeExposer, expose the fme_feature_type attribute Connect the AttributeExposer to a AttributeCreator to push fme_feature_type out an attribute (named fme_feature_type below) In the PythonCaller, get your attribute by: layer_name = feature.getAttribute("fme_feature_type")


1

I'm going to assume your text file is like a CSV with a header called "LayerName" and each row is a different layer. In that case, your function would be something like this: import fmeobjects def processFeature(feature): # Get which layer is currently being processed layer_name = feature.getAttribute("LayerName") # do some logical processing ...


1

As Fetzer says, it's going to be prone to error because the RGB values will vary. However - for what it's worth - here is an FME workspace that you can probably adapt to your requirements. I made this workspace to detect swimming pools in aerial imagery. Basically it extracts the RGB values and compares them to each other. I was looking for cells where blue ...



Only top voted, non community-wiki answers of a minimum length are eligible