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 formats that store indexes to the DatabaseJoiner transformer - like MapInfo TAB, ESRI SHP file, etc. that includes indexing on the writer.My use case is looking in tile grids,.. rather than having to convert to a database format to use the Joiner, or having to read all the data using a FeatureMerger, I would like to be able to be to read features based on a where clause directly from the file (or on the FeatureReader), so using the Joiner (or a where clause on the reader if it was possible) I could do that
Add support for an FME date calculation function (either as a datetime function or within a transformer such as DateTimeCalculator) that works on a 5-day week or 'business days' system. Excel has a NETWORKDAYS function that takes a start date, end date, and holidays input to do this kind of calculation.
It would be nice to see the feature number going into and out of a transformer with hidden connections. Much like the number of features coming out of a Rejected port.
BE great to get FME updated to the latest NetCDF releasehttp://www.unidata.ucar.edu/blogs/news/entry/netcd...
Add support for writing Sketchup in Linux (not sure if this is possible at all?)
I'm using the new "FME Workspace (FMW)" reader (2016) and I love it (before I was using a Workspace to parse the XML header inside FMW files to get Tranformers list or versions).But it seems that the feature type "Transformers" is unable to read/list normal transformers inside custom transformers (am I wrong ?).So I would like the abilty to see informations about normal transformers inside custom transformers (maybe with lists ?).
This data is used by print viewer "Field Access to Automated Records" created by the NMT Corporation
Currently the ListRenamer allows you to promote a list list{}.x -> x{}, but there is no mechanism for the reverse. x{} -> list{}.x
I would like to have a Feature Type TransformerInputPorts at the FME Workspace Reader.Similar to the existing feature type TransformerOutputPorts.I'm using a custom transformer throughout numerous workspaces for which I would like to evaluate all input ports of that custom transformer that are connected / not-connected in these different workspaces.
Currently, "Format Parameters" tab exists in nearly all feature types. This allows users to quickly choose values (usually parameters, attribute name etc), however it often fails to allow for attribute values to be chosen, even those these are valid in most instances. For instance, the jpeg writer allows parameters to define compression or optimize the jpeg. But you can not use a dynamic attribute value to set these with "Format Parameters". Expose these as "Format Attributes" and then you can pass a dynamic attribute. By not showing these abilities in "Format Parameters" users don't believe they can accomplish as attribute values. Updating these, would then convey some of the true strengths of FME
I have upwards of 15 data sets being read for various tasks in my workbench. When something goes wrong in one section of the workbench, it is nice to disable the non-offending readers to save time on testing. This is currently limited to a single reader/writer. It would be nice to select multiple readers/writers, and disable all at once.
Looking for the support road map for FARO *.fls (FARO Laser Scanner data)point cloud (LiDAR) file format in FME. Since fls is currently not supported in FME, I would like to understand if there is a possibility of this format getting supported in the near future?FME users with similar interest please up voteHappy FME:-)ing
In certain cases, it would be useful if I could add an image, like a screenshot, to the canvas.This would be mainly for the purpose of documenting a workflow using images or graphics that I create outside of FME.Does anyone else think this would be useful?
The discussion here suggests it might be super-easy, but it would be nice to have a solution that didn't involve renaming files. Thanks!
The JPEG2000 reader does not seem to read at the full resolution possible; opening my files in other viewers results in much better quality. Quality seems to deteriorate the lower you look in the image.
Grids in the form of layer of gridded-squared-polygons are used a lot to display indicators, index and other thematic mapping. Hexagons grids have a number of advantages over rectangles (see http://pro.arcgis.com/en/pro-app/tool-reference/spatial-statistics/h-whyhexagons.htm based on "Birch, Colin P.D., Oom, Sander P., and Beecham, Jonathan A. Rectangular and hexagonal grids used for observation, experiment, and simulation in ecology. Ecological Modelling, Vol. 206, No. 3–4. (August 2007), pp. 347–359.") including the very important one of being more appropriate for generalization. Adding an option to "2DGridAccumulator" to generate hexagon grids directly in FME would be very useful
It would be nice to have a toggle for invalidating the entire dataset if any record failed an attribute validation rule. An all or nothing option. Otherwise if I want to kick the data back to the original requestor, I have to do record count and tester and it's rather cumbersome. Thanks!
I was looking around for a way to identify aggregates in order to deaggregate them.I hoped for GeometryFilter but couldn't find it. So I ended up with a Tester for fme_geometry = fme_aggregate.Would be nice to have an option for Aggregates in GeometryFilter though.
FME needs an out-of-the box AGOL Feature Collection Writer. If you want high-available data on AGOL, Feature Collections are the way to go.
It would be great if FME could support the BIT data type in MySQL / MariaDB.For more information: https://mariadb.com/kb/en/library/bit/See also: https://knowledge.safe.com/questions/58629/how-can-i-write-a-bit-value-10-to-a-bit-column-in.html
I checked the documentation but it doesn't actually appear to be possible to create a User Parameter from a workspace parameter. That is, the right-click options for the parameters listed under the "Workspace Parameters" heading are limited to just one option - "Edit Parameter Value..." I'd really like to be able to create a published User Parameter from the Writer redirect parameter. Here's why: I have some workspaces which I am regularly testing in order to improve them and often in this testing I'll redirect the output to the Inspector or limit the number of features being read. Aside from running these workspaces interactively when I'm testing them, I also kick them off weekly or so in a batch process that uses the command-line. Whenever I do that, I want the workspaces to NOT redirect the output and to process all reader features. I'm able to do the latter because I published "MAX_FEATURES" and have that set to an empty string in the batch process. I'd like to set the Writer Redirect to "No Redirect" in the batch process but since I can't create a user parameter from it, I can't publish. So if I forget to change the Writer Redirect parameter to "No Redirect" and then save the workspace, on the subsequent batch run, it redirects the output. https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Workbench/Workbench/Publishing_a_Parameter.htm
Currently, if you specify the folder path to filecopy_source_dataset, the contents of the entire folder will be copied, but many times I just want to copy some subfolders or files. I hope to provide include and Exclude filter for FileCopy Similar to Fastcopy (free file copy software from Japan).This will make FileCopy more powerful.eg.Include:2017*.shp ?Just copy the shape at the beginning of 2017?Include:2017* ?Just copy the folder at the beginning of 2017?Exclude:2017*.shp ?Copy all subfolders and files except the shape file at the beginning of 2017?Exclude:2017* ?Copy all subfolders and files except the folder that begins in 2017?
Add a handshake to TCP transformers to allow a credentialed login to the host
Within a complex workspace it can be useful to reference other parts of the process. Idea suggestion is to allow the insert of an anchor in the annotation text that zooms you to another workspace object e.g. a bookmark/transformer. So it would be like an internal link almost an enhancement of the bookmark/navigator zoom functionality. (I guess the difficulty might be tracking these as the objects are removed/edited but the Safe dev team are smart :) )
It could be greyed out for non-spatial formats.
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.
