Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Allow FME Server to use both leading and trailing wildcard exceptions in FME Server. Eg. *.domain.* within the Web UI.
I would like to propose an update to the LineCombiner that would create a list of the coordinates where a line was joined at.
***Note from Migration:*** Original Title was: Visual Preview Window should maximize when double clicking on the window header, not dock. Visual Preview Window should maximize when double clicking on the window header, not dock. Docking the preview window when double clicking on it is not a standard UI behaviour. The window should have min/max/close functionality, not just dock.
It would be nice if the geotiff writer and reader for that matter had parameter options for dealing with elevation grid data. Most DEM/DSM that we deal with are in geotiff format and the writer doesn't give you an option to specify that the geotiff is elevation grid data.
A nice feature to have on all readers which support textures/appearances would be to have an option to skip textures/appearances. It's fairly easy enough to rename the textures folder in most cases, however, this is not always possible (e.g., FME Server or with binary files where textures are in the file). The benefit here is a performance boost. The textures can be particularly slow when reading CityGML for example, One must read in the file before appearances can be removed.In certain workflows reading the textures isn't needed, such as geometry validation and or conversions to formats which don't support textures.This would be a nice addition to speed things up
Idea is to have an active directory choice box that refreshes at runtime. Let's say I'm trying to select the name of a service account owned by an employee so I can use its value in my translation. So when I open the "Service Account" publish parameter, I can go from Boss Name > Employee Name > All Service Accounts owned by Employee through the choice box interface, in a tree like this: Clicking on "Service Account 1" would allow me to use its name in my translation. Would be absolutely epic if this interface would work in FME Server as well. Currently I can import a static version of this info to the choice box, but having it actually query the AD Server when clicking through would be awesome as it would always be up to date.
If you have this data : "01/01/2020"With this pattern : "([0-3][0-9])/([0-1][0-9])/([0-2][0-9][0-9][0-9])"You can only extract data by using the number of order of the different groups you made : "3-2-1" to extract this : "2020-01-01"The official PERL documentation (which is the one recommanded by Safe to look at for REGEX) allows you to use names for groups for an easier calling.So, with the previous data : "01/01/2020"You could use this pattern : "(?<day>[0-3][0-9])/(?<month>[0-1][0-9])/(?<year>[0-2][0-9][0-9][0-9])"And extract data by using this call : "g{year}-g{month}-g{day}" to extract this : "2020-01-01".This exemple is really simple but when you have tenth of group for a very complexe REGEX search, it becomes very difficult to use.REGEX doc on Safe website : http://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Transformers/!Transformer_Parameters/Regular-Expression-Editor.htmPERL REGEX doc recommended by Safe : https://perldoc.perl.org/perlre.html
WHAT : Modular installation with possibility to pick transformers and reader categories to limit the installation. Packages would allow to add 3D, BI or PointCloud transformers and formats later if needed for example (even partial upgrades?).WHY : FME installation file and folder are becoming bigger and bigger,A lot of people are lost with so many transformers/formats,SAFE is pushing more outside of pure GIS and CAD market.
Like the PointOnRasterExtractor but for point clouds.It is becoming more and more common for terrain data and surface data to be delivered in some point cloud format which is really nice. Now, however, previous workflows which were raster based like getting the height of a terrain from a raster based on a point are now becoming obsolete . A performant method for extracting data from a point cloud based on a point location is becoming an important workflow. A single FME Tool solution would be awesome.
FME Hub is a fantastic place for members of the FME Community to share their work and solutions with each other. As the amount of content in FME Hub grows, and the usage increases, many items become flagged for updates - things break, or sometime enhancements are needed. I think it would be amazing if the entire FME Hub had a more collaborative approach, perhaps similar to Git, where members of the FME Community could enhance existing items and fix bugs - even if they are not the content owner. This practice would promote more robust content, and ensure that content does not fall out of date as FME evolves. What do you think? How often have you wanted to enhance an existing item? How often have you come across items in FME Hub that need to be fixed?
As the user is "connected", would it be possible with FME data express to open a second workspace/app based on the result of the first process/automation? In the best situation, context elements, like the background map, could be adapted. This would allow multiple stages/steps scenarios within FME data express.
This idea is for Desktop and Server versions of FME software to be able to be patched where bugs are encountered & with a simple patch process. Background ... After updating to FME Desktop & Server version 2019.1, a couple of bugs were noticed, with StatisticsCalculator, and Counter (with Excel). Due to Desktop Server versions needing to be in sync, it is not always easy or cost efficient to simply update the software, particularly on the Server, each time a bug is encountered. Workarounds have been used in relation to the above, though they are 'painful' and inefficient often needing to be fixed in later versions. Having a simpler, easier process to patch the software (the transformer) would be much preferred and have business benefits and cost efficiencies.
On feature merger when handling duplicate suppliers have an option to "Join with first supplier" and then have all other duplicates that wasn't first for that ID flow through a Duplicates port.This is useful in joining tables to at least get a join on some data and then have separate logic for the rows with duplicate identifiers.
Add an optional parameter to assume the first row of a table contains the column names (see https://community.safe.com/s/question/0D54Q000080hfEGSAY/problem-by-reading-of-html-table?t=1597311083500).
It would be nice to be able define the Time Zone at which a schedule runs instead of the time zone in which the instance lives.
It's possible you forget you have a reader disabled and when you run your workspace, it's not part of the result. Would be nice if FME notifies you before you run your workspace that there are readers/transformers/writers disabled (and which ones).
Hello, here's something I've come across many times in FME. When a translation sends no records to the writer, no files will be written for that writer. This means that if I am updating something daily and one day no records are sent to the writer, the file will remain as the day before (outdated), and this could cause confusion to customers.It is the same issue expressed in this thread https://knowledge.safe.com/questions/3785/empty-mapinfo-tab-or-shape-file.htmlHowever, no satisfactory answer is provided.The idea would be to include an option (a checkbox) in the writer or in the workbench to "allow writing empty files if no records are sent to the writer".The thing is that some systems need a file to be there, even if it is empty. Otherwise, loading will fail. So things like, removing all the files from folder before running the workbench won't work for me because the system is requiring all the listed files.Probably this is something that many people has come across already, and there are many workarounds, but this option should at least be considered, as it would save a lot of time applying those workarounds.Hope that makes sense.
***Note from Migration:*** Original Title was: Neighbourfinder: Possibility to use Start and Endpoints only for finding Neighbourhood Problem:I often Need only to use start- and end-Vertices of lines to pass through the neighborfinder-transformer (as well as Networktopologybuilder)So I must use the Workaround to:1. use the Counter to get an ID for the lines2. coordinateextractor 2 times do get first and last coordinate3. vertexcreator to create start and endpoints4. use the neighbourfinder to find out wheter a line's start- or end-vertex is nearby (what I actually wanted to know!!)5. use the featuremerger with the original Feature to get the Information on the original-FeaturePossible Solution:Upgrade the Neighbourfinder with the Parameter "used base geometry" with the possible values:"All Geometry" -- means the whole geometry, including lines between Vertices"Start-Points""End-Points""Start and End Points""All Vertices"This could be also helpful with the networktopolgybuilder (Start and Endpoint could help!!), because a lot of users seem to have problems with selfintersecting Features and other "invalid" Features (sometimes the Invalidation is only in FME, not in Reader or writer, where e.g. selfintersections are allowed)
Improve the Attribute Range Mapper to allow you to specify whether From and To ranges are inclusive or exclusive. Currently they are always inclusivee.g.Greater than or equal to 0 but less than 250Greater than or equal to 250 but less than 500
I love the emailer transformer- it's great, however, there is one limitation which is a little annoying which I think would be nice.Sometimes you want to attach an unknown amount of attachments to an email. At the moment you must zip them up (which is fine, but not always desired). If you want to work around this it's a little annoying an involves multiple emailers each with a different number of attachments defined .The solution would be to allow a list attribute. It's pretty minor really but would be a nice to have.
It would be good if the SQL Executor operates the same way on any database formats its supports. Recently I've had an issue whereby I cannot execute a 'DELETE from <my-table>' statement on SpatiaLite, but I can execute the same statement on Oracle Spatial. See the following Knowledge Centre question and supporting answers/comments at https://knowledge.safe.com/questions/50230/sql-executor-and-spatialite-delete-or-drop-command.html
It would be nice to control a job's running expiry time by which Queue it's been assigned to. At the moment Queues can be configured to a specific Repository, Engine, and designated a Priority level. So for example:Fast Queue ( < 15 mins )30 Min Queue ( 15 mins - 30 mins )60 Min Queue ( 30 mins - 1 hr )Slow Queue (1 hr + )1) This would help when your limited to a small number of engines and have to manage a high volume of jobs.2) It eliminates processes that may hang up an engine or two and cause the FME Server Job Queued List to rapidly grow. This could be to due to external sources. i.e. Database Performance Issues, Memory Constraints, CPU Constraints, and other constraints from a data source or target source perspective...3) You wouldn't need to then set the running job expiry time parameter for each individual schedule or automation, which makes it easier for FME Admins and Authors. 4) It would be easier to designate the correct Queue for a schedule or automation. You wouldn't be mismanaging Queues and you'd be able to minimize the amount of time a job is waiting for an available engine on the Server. Related to: https://community.safe.com/s/idea/0874Q000000TkrlQAC/detail
FME_SHAREDRESOURCE_TEMP and FME_SHAREDRESOURCE_DATA as a System Parameter that a user can preset the UNC in Desktop, Server/Cloud:Desktop:FME_SHAREDRESOURCE_TEMP = D: empFME_SHAREDRESOURCE_DATA = M:myprojectmydataServer/Cloud:FME_SHAREDRESOURCE_TEMP = /Resources/Temp/tempFME_SHAREDRESOURCE_DATA = /Resources/Data/myproject FME_SHAREDRESOURCE_TEMP and FME_SHAREDRESOURCE_DATA parameters can be used in a workbench for reading and writing data. When run on Desktop or Server/Cloud the data is read from or written to the specified location, no adjustment of the UNC in the workbench required between environments and no need to setup your local folder to mimic Server. Discussed with @smaccabe
It would be nice if the location and size of windows was stored. I always find myself resizing the list of attributes to select for the attribute keeper and attribute remove transformers.
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.
