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.
***Note from Migration:*** Original Title was: Auto clear text when Test String textbox is focused (FME 2016's Regular Expression Editor) In FME2016, the regular expression editor is added, it is very convenient for test of regular expression .But I also found that It is inconvenient to use. By default,It display "Enter a string to test here..." in the test text box, but when you click the text box, these texts are not disappear automatically, so every time you need to manually clear. I suggest can be like a lot of Web password text box, Display only when the text box is not entered and not in focus. Or simply remove these tips, because the editor itself is not complicated interface.
Actually FME 2016 is not friendly to non-ascii characters. I encountered several cases where Japanese characters (within file/folder paths, attribute names etc.) causes unexpected behavior.The situation is worse than 2015. I'm afraid that more hidden problems exist yet.Similar issues probably occur in other non-ascii locales. I strongly hope thorough investigation and enhancement regarding FME i18n will be done.
The inspector is a great tool to view features and to view filtered features but it cannot save just the filtered features. Why not add this functionality?
Actually, FME doesn't have a PDF library with Python.Can you add a PDF library by default ?Thx
Currently, you need to specify a "hard-coded" AccessKeyId and SecretAccessKey for the SQSReceiver/Sender/Deleter/MessageCounter, or you can set it through a Public/Private Parameter.In the S3Downloader/Uploader/Deleter/ObjectLister, you can omit these values and get them through a file, Java system properties or environment variables. I think it would be nice if this behavior is consistent among these AWS transformers.
FME used to have the ability for the user to add transformers to the toolbar. I found this quite useful because I could just click on the icon for, say, AttributeCreator and not have to type it. If most users didn't use this functionality, perhaps it was because they didn't know that you could do it.It didn't matter if the icons were all the same because you could put your mouse over it and get the name from the tooltip. Plus if you use FME a lot you knew where each transformer was on the toolbar. Can we bring this functionality back?
The Hexagon Point Cloud format (.HPC) is a pretty closed format and not very much support for it. IT would be nice to have to have FME be able to convert it to a standard .LAS or .E57 format that other packages can use.
Ability to be able to write 3D Printer file formats - for example, STL file. Currently i have to take a COLLADA file into a 3rd party app like MeshLab to achieve this.
If you send two non-intersecting lines into the LineOnLineOverlayer or the Intersector, the attribute "_overlaps" is set to 1 for both features exiting the Line / Intersected port, even when they do not intersect. The same value of 1 is also set if the two line actually intersect.I suggest that non-intersecting lines get "_overlaps" set to 0 to make it easier to filter the results accordingly.
With the Joiner transformer there is not option to see the data that has not joined to something successfully. It would be nice to see which features that have been unsuccessful, so perhaps a rejected or unsuccessful or not joined port out of the transformer. Currently the only way of seeing whether features have not joined is buy looking at the feature counts either side of the joiner. Even then you do not know which one did not join.
I have a customer using an older version of FME.I want to know if a certain format is available for him.But I can not find a list of formats with the version of FME in which the format has been added to FME.Can this be added to the formats information or the Readers and Writers manual?
Add a checkbox for the interesting values, rather than delete all the ones you dont want to handle at the moment. Pack the rest up in a new Hidden tag.
When using a dynamic workspace from a feature reader the only way to remove special characters or missing values is to expose each attribute and then use the NullAttributeMapper, as far as I know! What would be great is an extra dialogue within a dynamic writer that allows for the replacement of any null or missing values.
I would like to see a way of selecting some transformers and running only that part of the workbench to test it. There are some occasions where I have very large workbenches and going through muting (sound man habit still use solo and mute!) the lines or transformers can be time consuming. The ability to hight light a section or even bookmark and running only that part would make debugging workbenches a lot easier.
Route data in, apply CGA, get out 3D objects to route elsewhere
Add (small) arrow markers to each connection line segment. I can imagine the following options to set for a workspace:- Show arrow markers on connection segmentsIf the arrow markers are on, then you should be able to choose the location:- in the middle of connection segment - at the end of connection segment
UniqueValueMapper result to file. Then unique values would be easy to import to AttributeValueMapper and other transformers. Simple text file would be ok.
If a CSV or XLS file contains X/Y or Lat/Long attributes the reader will allow reading those fields into a geometry.The next step would be to allow a spatial predicate in the FeatureReader transformer.The current FeatureReader does not allow spatial selection on these formats and forces you to use the Clipper transformer to select features inside the area of interest.This could be hidden in the FeatureReader for datasets containing coordinate information.
To find the nearest candidate from a spatial dataset you have to read the dataset and use the NeighborFinder transformer.To do exactly the same using the FeatureReader would now be a two-step process (Buffer the base object and use the buffered object as Initiator in the FeatureReader, followed by a NeighborFinder.A predicate of "Find closest object" in the FeatureReader would be a performance boost and a reduction of required trtansformers. And would reduce the amount of features read into FME Workbench.
***Note from Migration:*** Original Title was: Ability to freeze the translation log during a translation (pause the auto scroll) When we run a translation, we can pause it but I would just be able to freeze the translation log to read some warnings (by example) during a translation. By freeze, I'm meaning stop the auto-scroll.Something like : if I click inside the translation log during a translation, I can up and down the log to read inside and this stops the auto-scroll. When I leave the log window, auto-scroll starts again.
We just noticed that FME Server 2015 sends empty mails when a workspace does not produce any output and you are using the DataDownload-Service with the "Email results" option.It would be really nice if FME Server would provide an additional topic:DATADOWNLOAD_ASYNC_JOB_EMPTYand a corresponding subscription:DataDownload_Email_JobEmptyto handle this case. The job result (SUCCESS/FAILURE) does not really provide a way to determine if a job was fine but did just produce no output.
The SAFE's knowledge center use the Auth0 provider for the security. Can you linked the security of FME Server with this Security Cloud provider ?
Sometimes a picture is worth 1000 words. The ability to include images in the custom transformer description would help clarify exactly what it is doing.
Currently it is already possible to average an attrbute with a weight by area. I would not like to use area, but another attribute for example length or count. If it would be possible to assign an attribute to weight by, it is still possible to weight by area and the function can applied wider.
When having tens or hundreds of custom transformers with long names, their tabs get really small in FME Workbench. It's hard to see, which custom transformer is in which tab. When selecting a custom transformer on canvas, just highlight its tab.Another option: When hovering mouse on the custom transformer tab, show the whole name of the tab.
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.
