Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
I would like to see the inspector far more integrated with the FME Workspace. Use the results inside the inspector to guide and insert transformer in order to clean data. There are lots of simple but tidies data cleansing tasks that could be discovered and cleaned while you analyse and view the data. For example removing/replacing strings. Split or concatenate strings, find/replace text, change projection, date formatting, aliasing, data type conversions, etc... The inspector could give hints while users simple select text in the result or selects attributes... The inserted transformers (suggested by the inspector) would basically be inserted in the work-space after the inspector-transformer that exposed the results.Such radical changes could allow FME to come a step closer to basic users and it gives advanced users a quick tool that would improve building work spaces much faster. Even cooler would be to re-run the last result so you instantly see the effect of the added transformers...
Since GeoJSON features can be represented completely with text, it would be great to read GeoJSON features directly from attributes and parameters. This would allow, for example, supplying database spatial envelope filtering or clip geometries as a parameter to the workspace.
***Note from Migration:*** Original Title was: List more descriptive less abbreviated coordinate system names; preferably matching ArcGIS when imported. ie. "NAD_1983_10TM_AEP_Forest" instead of "CANA83-10TM115", so as not to be confused with “10TM115-83”
Within my workspace I have the need to filter several datasets at one or the other point, utilising AttributeRangeFilter. However, the range used is always the same. To avoid typos I was looking to set the range as user parameter and link to the different AttributeRangeFilter transformer.While able to create user parameter with range configuration, I couldn't find any possibility to link user parameters to the 'Range Lookup Table' of the transformer.Hence, I would propose to extend the AttributeRangeTransformer to use user parameters.
I'd like some quick functionality for when I'd like to enter a list of values (no geospatial data involved) into something like a creator where each line would be interpreted as a different feature. I can do this currently by creating a single attribute then splitting by line and exploding but some sort of scratchpad functionality would be great. It's something I'd mainly want to use when testing/creating new workspaces.e.g.
I have what I think is a fairly simple use-case, but FME doesn't currently has the tools necessary to readily implement it. So this is a transformer suggestion for a ListAttributeMapper or something to that effect.Basically I have a list like this:_list{0}.class = 1_list{1}.class = 2_list{2}.class = 3_list{3}.class = 5_list{4}.class = 2_list{5}.class = 1I need to know how many of any given class there are with the feature. ListHistogrammer does this nicely:_histo{0}.value = 1_histo{0}.count = 2_histo{1}.value = 2_histo{1}.count = 2_histo{2}.value = 3_histo{2}.count = 1_histo{3}.value = 5_histo{3}.count = 1My problem then is turning those into arbitrarily named attributes without a needlessly complex set of testers, let alone a PythonCaller.I want my output feature to have attributes like these:first_class = 2other_thing = 2third_item = 1fourth_item = <missing>final = 1A kind of ListAttributeMapper would be one way to solve this. You'd point it at _histo{}.value, and for any given value in that field, tell it into what attribute name to to put the index equivalent value of _histo{}.countHopefully that's clear
It would be really useful if the TableAdder could have a group by function where multiple tables can be created for each group of data.
Most times we do not see an entire log content in a chronological order; seeing last 100 lines, or logs created in last one minute or so would suffice. This would also save a bit of bandwidth.
Hi,When a Workbench workspace (*.fmw) is run, it's converted into a mapping file (*.fme) on-the-fly to be run by fme.exe.I'm using "fme" files for production (called via a BAT file), while the Workbench workspaces are for testing and debugging. This is my "best practice".But if I have one workspace that runs another, I cannot run the mapping file itself, only the Workbench workspace.I think it would be a huge enhancement, if the WorkspaceRunner could activate a mapping file (*.fme) directly, removing the need for the on-the-fly conversion. A win-win wrt. performance too.CheersLars I.
Having the option to specify a WHERE Clause would be invaluable to workflows that leverage the FeatureReader transformer. Limiting the amount of features read into FME Workbench would considerably reduce processing time.
For years, I and the folks I've trained have grown accustomed to keeping a .PDF of run .FMWs as a record for job structure and dataflow / stream numbers. For some reason, basic print setup functionality went backwards in recent releases. Current page / print setup doesn't allow us to setup something like ARCH D fit to page, landscape so that we may print to .PDF.
There are a ton of transformers and for newbies it is tough to figure out what they are for. I know about the Transformer Gallery on Safes website to help customers to get a better understanding of a transformers functionality. I am a newbie with FME, but have many years experience with ArcGIS and their geoprocessing tools. I was wondering if it would be possible to indicate which tool in ArcGIS provides similar functionalities, creating a comparison of FME / ArcGIS this way.
There are OGC web service providers that support custom URL parameters.Eg.: it is possible to include parameters in the SQL of an 'SQL View' layer in GeoServer. The parameters can be passed as query parameter in the request URL: &viewparams=param1:value1;param2:value2... (Such a parametric WMS request make life way easier when ther is a good SQL)It would be handy if WFS/WMS readers support custom URL query string parameters like in the HTTPCaller.Now I have to use the 'manual WMS' (HTTPCaller->RasterReplacer->CoordinateSystemSetter->RasterGeoreferencer) to benefit from this functionality.
Would be useful in custom transformers to be able to specify a list (multiple checkboxes) as a published parameter to the custom transformer to dynamically expose certain attributes. Often when wanting to create custom transformers that can support different data schemas the ability to expose certain attributes inside the custom transformer for either manipulation or writing out to a temporary data store increases the re-usability.
***Note from Migration:*** Original Title was: GEODATABASE_FILE reader to have 1:1 relationship between Tables to read and Where clauses I frequently want to apply a WHERE clause per Table/Feature Class
***Note from Migration:*** Original Title was: It would be great if fme desktop can output dbms_output.put_line("...") statements to the FME Log using the transformer SQLExecutor
If there is a lot of text in the String Editor in different Transformers it would be handy to doubleclick the top-bar to maximize it
Based on this question: https://knowledge.safe.com/questions/37335/does-the-fme-installer-produce-a-log-file.html An automatic log file instead of a command line option would be great.
With FME 2017 the parameter creation dialogue box exposes the Parameter Attribute Assignment (Default|Off), which defaults to Default.I would like the ability to set the default setting to No when creating new parameters.
I see that frs files, which are created when saving Raster to ffs consume a lot of space. e.g. a 2Mb Tiff file with 10000x10000px results in 400Mb of frs. I tried different compression settings for ffs, but this doesn't influence frs handling. Request would be to provide a way of handling/using compressed frs files to keep the files smaller and save disk space. see also: https://knowledge.safe.com/questions/40834/saving-raster-with-ffs-uses-lots-of-disk-space-any.html?childToView=40874 Michael
HttpCaller does not allow to send body if chosen method is delete. Many REST api's use body also with delete method.
I manage multiple FME Servers and having to change the connection parameters in the Publish/Download to FME Server window in Desktop is a pain. I can set one as a default, but I would like to be able to store others.
Please add ArcGIS Online to the possible Named Web Service Connections. I have to work with multiple domains and have to change my credentials everytime, this way I just can call the Named connection I need without having to change my credentials.
Good day FME'ers,I have recently been playing around with CouchDB as a way of storing data in lovely JSON documents. I have noticed that the options for processing data from CouchDB in the reader are not as extensive as they are in the JSON or XML readers. It would be nice to have the option to flatten the data being read from couchDB or to put it into FME lists. Thanks,David McDermott
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.
