Shape the future of FME with your ideas
New and Open ideas are awaiting review or have been reviewed by our Product Management team, and are open for commenting and voting.
To be able to copy the path name of the workspace from the start tab . Something similar to the second image below.
Currently I have to use 2 statements to handle it, one plain SELECT COUNT(*) AS NUMBER FROM TABLE WHERE CONDITION, and the second statement performs actual update/deletion. It would be useful if SQLExecutor is able to expose number of rows affected bu UPDATE, DELETE commands.
I mean the first row versus the field values.
At the risk of sounding like a fuddy duddy, after a few days of using FME 2016 I'm really missing the help panel! The new window is too slow to load, too distracting when it changes continually when you click on different transformers, and takes up too much window real estate when you leave it open. Please bring back the olde panel!
When using the xmlupdater, there's not a good way to see which of your updates actually worked. You always get xml out, but it's not immediately obvious how it has been changed. It would be nice if there were a way to have an output of each update that was performed on the xml, or a way of seeing which features that you send in successfully altered the xml or not. Or just an output per feature that has attributes that show the results of the parameters for that feature.
It would be handy to be able to test workspaces on FME Server environments with disabled output. The Writer Redirect Parameter can not be published.
Would it be possible to implement a second type of custom transformer (CT) where the creator can state that all attributes created inside the custom transformer are local and therefore will not be added to the feature entering the CT. In the output port(s), those attributes that are the result of the analysis will be visible. In the parent workspace, the user that uses this CT can than be allowed to catch the values returned by the custom transformer ('the function') and store it in attributes with names that can be chosen by the user (or by typing or by value of an attribute). Implementing a custom transformer in this way, will allow us to completely differentiate between the feature that initiates the CT and the analysis done within the CT AND it will allow us to catch results in different attributenames without overwriting a possible existing attribute.Is it clear what I'm looking for?What do you think of this idea?
Instead of the short line and the teeny number on the right of the text box, maybe the text box itself will be occupied by the progress bar.
It would be great if the FME workbench could reveal the under lying code for Mapnik and let you adjust certain parameters through code as well as parameters. Or better still allow for a code box that can render images through mapnik code. THere are also a number of other programming laungages that have very useful open sourced libraries that would be brilliant to utulize in FE.
I wondered why there is no CSV flattener, like JSON or XML flatteners. I had to process CSV in HTTPCaller's response ('_response_body').So I made my own with Python caller (which is not utf compatible).import csv, StringIO import fme import fmeobjects # Template Function interface: def processFeature(feature): pass # Template Class Interface: class FeatureProcessor(object): def __init__(self): pass def input(self,feature): stringinput = feature.getAttribute('_response_body').encode("ascii","ignore") reader = csv.DictReader(StringIO.StringIO(stringinput)) for line in reader: for field in reader.fieldnames: feature.setAttribute(field, line[field]) self.pyoutput(feature) def close(self): pass
It would be nice to have a Launch new instance option in File menu, which would leave current workspace intact.
Take a 2-point line and return the inverse Vincenty geographic (WGS84) distance between the end points.This is to eliminate distortion caused by any projection you might be using for points over a wide area.I know Vincenty doesn't resolve with near-antipodal points but I'll live with that, just tell people 'hey its roughly 20,000 km for this one'.
People often ask me if i have any posibility to read and display different formats - in most cases they only want to see the Data and have no suiting tool. I have the posibility thanks to fme. But my local authority can't provide fme licenses for every single coworker who just wants to take a look at different data. So often i read the data in and export it as pdf or some other format like shape. I could provide a workspace on FME Server that converts some formats to other formats, but that won't help at any case.Heres my Idea:FME Server should have the ability to offer end-users a lightweight interface to upload Data in different formats and feeds a simple web-mapping application with it. Kind of a browser-based Data Inspector with basic features like zoom, pan, measure, print.
Especially a "Dark" theme.
***Note from Migration:*** Original Title was: Enhance FME Server on Linux so PythonCaller scripts can use GDAL / OGR and associated libraries The PythonCaller transformer provides a powerful way of extending what can be done with FME, when there is no native transformer available. A key set of tools for working with geospatial data in Python are the GDAL libraries and Python bindings. However, at present PythonCaller transformers that use GDAL (or OGR, or various associated libraries) do not work in FME Server on Linux. This means that one of the main uses for the PythonCaller - to extend the capability of FME itself - breaks.ProblemMy scenario is that I am using a Python-based approach to calculating raster zonal statistics via an FME workflow. The FME processing creates or supplies the zone geometries and then the Python code loads the raster files directly from disk via the GDAL library, calculates the zonal statistics, and outputs them on FME features. This enables rapid calculation of zonal statistics on huge numbers (tens of thousands) of raster files, with FME helping to manage the results. This works very well in FME Desktop, but in Server on Linux it fails because the GDAL library in Python is not able to load the raster files. The issue can be demonstrated very simply. Running the following code in a Python interpreter on Windows, or on the system interpreter on the Linux machine, will return a number indicating how many formats GDAL can read: >>> from osgeo import gdal >>> print gdal.GetDriverCount() 207 The number will vary depending on what exactly is installed. However, running this code inside a PythonCaller or PythonCreator in a workbench published to FME Server on linux, outputs a value of 0, indicating that GDAL cannot read any data formats. I think this fails because FME has its own built-in copy of some parts of GDAL and this isn't meant to be used other than for FME itself, so it's probably been compiled without that stuff built in. However instead of removing the unnecessary symbols from the FME-supplied library, they're there but crippled. Because Python runs within the FME process, the Python code also gets presented with the FME copy of the GDAL library when it tries to load it, not the system one, and therefore can't read any GDAL data. Possible Solution I think there's at least two approaches that could be taken to fixing this:Customising the FME-internal version of GDAL a bit more so that the functions (symbols) it provides don't conflict with the original GDAL ones. So when the Python GDAL library tries to call the native GDAL functions, it gets the correct system-installed ones, and stuff that's internal to FME stays that way and doesn't "accidentally" get called by a user's code. I don't think that I as a user should be able to have my Python code accidentally call things that are supposed to be internal to the code of FME. (Note, the same issue I'm describing here used to also happen with the SQLite library, which also didn't work in Python code on Server, but that has now been fixed in recent versions of Server which no longer have an FME-specific version of that library. So change is possible here!)Increasing the separation of the Python environment that runs within a PythonCaller or PythonCreator. I don't know how or if this could be done. However since on linux FME uses the system Python interpreter, then I think it's reasonable to expect Python code that works at the command line, to also work when called via FME.
writing to elasticsearch
Currently, when exporting a Revit model to .RVZ file, the Revit "Mark" (Identity Data.Mark) parameter only gets exported for certain Revit family types, such as a door family. Generic Model families, however, does not export the "mark" parameter and therefore is not part of the translation to another source, which in our case, ESRI Shape Files.Being able to export the Mark parameter for all Revit types would be extremely helpful, especially here at the Denver International Airport where we work with big data.
I am analysing a series of our workspaces using the FMW reader and trying to ascertain which have templates. I have found the DEFLINE_TEMPLATE parameter in the 'workspace parameter' attribute and assumed that where this has a value there is a template, but I cannot find the location of the template file itself. If the reader does not pick this up it would be useful to add in future, thanks.
I am really happy with the new tunnel and junction functionality in 2016.1. I have been hiding a lot of lines in my workspaces already. So much tidier! However, I noticed that when I drag transformers around, they sometimes snap to the hidden lines, which can cause quite an unexpected mess.. :)As a temporary workaround, I have disabled the "Use Drag-and-Insert Transformers" option, but I really like this functionality. So maybe it's an idea to make hidden lines "unsnappable"?
Performing translation on Autocad DWGs and realized that there is no support for the viewport freeze in FME. The viewport freeze allows for a user to turn off certain layers in the viewport but keep them on in the model space.
It would be great if using the HTMLReportGenerator we could choose an option for Vertical table. It would be good for scenarios when I am using the group by option to create tables and I am creating a single table for each record like below. I always have one heading that contains a lot of text and it would just look better within a vertical table.Name:John Smith Location: StreetRef:123456Proposal:Insert your proposed changes into this section, this is free text and contains a lot of text!!!!!!!!!!!!!!!!Thanks
There are many API methods which don't accept 'unicode' instance as their string type arguments.e.g.1st argument (attribute name) of FMEFeature.setAttribute1st argument (message string) of FMELogFile.logMessageStringCurrently users who are working with Non-ASCII locale have to add codes to check the class of each string value and convert it to a 'string' instance if it was a 'unicode' instance, to avoid the UnicodeEncodeError.Hope every method will accept 'unicode' instances as string type arguments.
As help is now online, it would be great if Safe could show bugs and enhancements request against transformers. There is nothing worse than having a process not work, narrowing it down to a particular transformer and notify support, to be told that there is already a bug report in for it. Having the ability to see existing bugs against each transformer, would be useful at narrowing down issues quickly.
In-depth courses for all FME skill levels.
Explore our extensive collection of how-to guides and tutorials.
Log an issue with us. Our support team is ready to help.
