Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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.
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.
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.
***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.
There are several transformers that produce fixed attributes (NeighborFinder, TopologyBuilder, SpatialRelator, etc). When using them in a custom transformer I have no idea if I am overwriting any previously existing attributes and would like the option to specify a prefix for these attributes. Our local rule of thumb is all interim attributes in a custom transformer start with _!, and that pattern is never used outside of custom transformers. So for the NeighborFinder, with a prefix of _! would produce _!_distance, _!_angle etc.
I love the new XML elements to match capabilities of FME 2016 (still on beta), was always an hassle to get the right element. It would be even better if after scanning the XML document and displaying the scan results that a little export (to txt) option would be made available.
Using Quick Add by specifying the capitalised letters associates the combination you entered with the Transformer chosen. e.g. entering 'AC' and selecting AngularityCalculator, will select that Transformer in the list next time you enter 'AC'. But I don't use the AngularityCalculator often, so next time I use 'AC' to find the AttributeCreator I have to go scrolling for it in the list. It could be nice if they were grouped together so FME remembered all the 'AC' typed/selected transformers and grouped them together, then listed the remaining Transformers after. Maybe an FME Option to reset/edit the list or toggle this mode with the existing mode.Of course I could use my own shortcodes such as 'CA' for AngularityCalculator but that's harder to remember!
Within the history of FME workbench, it would be nice if you can add a mark to a step in the recorded history. This way it becomes easier to go back to a certain moment if you are testing different possibilities. Now you really have to search to find the step you want to reset, this way you can say: go back to that mark.
When manipulating a spatial database using SQL statements, there are many cases where the syntax requires SRID (Spatial Reference System Identifier). If you are going to use such SQL statements with the SQLExecutor, will have to find a proper SRID from a documentation. It might be convenient if there was a transformer which can be used to interpret any FME Coordinate System to the corresponding SRID.
In addition to being able to provide a filename filter (e.g. *.dwg) on a file-type published parameter, it would be great to be able to restrict the user to a specified directory via a directory filter.
Adjust database(-like-)writers in such a way that you will have three input ports: insert, update and delete. Within the properties dialog box, you should have radio buttons to turn the different writer modes on and off.Example: http://www.larsdevries.com/img/database%20like%20...
Description of action is required in undo tool to understand easily what action we are going to undo and we can decide whether it is required or not.
For debugging and testing (32bit vs 64bit and also version/build number vs version) and in a couple of instances for customers with >1 installation of FME Desktop, it would have been handy to allow the WorkspaceRunner to allow you to determine which FME the sub process should run in rather the one defined by the path environment variable. An option to select or detect which FME to run would be useful.In the past I have solved this by effectively building a Custom WorkspaceRunner by using a SystemCaller to do the job instead.
Enable user to define SRID to save into SDO_GEOMETRY when inserting data into existing Oracle Spatial table, even after truncating old data. This procedure is repeatedly used in transforming data between systems in and out of the company. The target table must stay the same as it is used elsewhere - if source changes it's alright for transformation to fail (of course we have sanity checks before running it :-).
Add the import options for Named database connections to the Choice (with alias) User parameters.This is already available for Formats and Coordinate Systems.
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.
