Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
In order to be able to easily share both plug-ins and custom transformers (both using the .fmx extension), it would be great to introduce a new file type, that basically is a packaged/zipped FMX with a bunch of auxiliary files added to it. This would be similar to the .fmwt file (Workspace Template), that has the ability to include source datasets with the workspace.Why?If you developed an FME plug-in using Python for example, you typically end up with a .fmx file and one or more .py files. This can't be shared on FME Hub unfortunately (as discussed here). Bundling it and adding support for it might solve that for those users who are not familiar with Git (if FME moves in that direction): the code file would simply be included in the package and when the user downloads the plug-in, it will all be installed in the FME transformer directory.An FMX package would allow us to include required resources, e.g. when the custom transformer requires some kind of lookup table (e.g. CSV).You could include images (GIF, JPG) that can be used for creating examples in the transformer description/help section. If you want to do that now, you'd have to host the image on a server (which means keeping it online "forever") and link to it in the transformer description/help.
I would like to see some sort of workbench version control on the server. We have staging and live servers and undergo testing of workbenches before making live. However, as the other systems largely use URLs the workbenches have to stick with the same names. I would love the ability to drag and drop versions of a workspace for testing that automatically keeps tally of the version date and release number as well as auto backup the last iteration of the workbench. Yes you can create separate folders but it can get complicated keeping a tally on each version of a workbench.
Add 'Global Search Envelope' that can be applied to all the readers.
Currently there is no way to get font name and symbology from DGN reader. The symbology and font is stored in the seed file. The DGN writer accepts a seed file. Please add seed file to the DGN reader as well.
Sometimes when I'm cleaning up my workbench to make it easier to read, I need to move transformers or writers near other existing transformer connectors. The green triangle auto-connect gets in the way and starts connecting transformers inadvertently. I would like to be able to hold down shift or something that would disable the green triangle.
Currently. The header is added with no option to skip it. Would like to have this option like the other XML transformers
All the JSON transformers except the JSONFragmenter allow the input JSON to be an attribute, free text, or a parameter containing the json, usually called JSON Document.The JSONFragmenter requires an attribute containing the text or a parameter containing the name of that attribute, which is inconsistent with the behaviour of the other transformers
***Note from Migration:*** Original Title was: To finetune the Questions form to avoid people form typing the questions in the title. Hello,I may be wrong but the text in the Title text/box is misleading the users; reaons why they type long questions in the title text Field/Box. Please see the following questions for more details:https://knowledge.safe.com/questions/51222/asking-question-in-the-title-isnt-the-right-way-bu.htmlCheers.Lyes
I am looking for a transformer, which will take a shapefile as input and then publish this shapefile on to ArcGIS Server or ArcGIS Online, this should be possible either in ArcGIS Desktop or ArcGIS Server, this is to remove the whole manual process involved in the publishing of such files.
Takes a long time to download and update FME desktop. For example Microstation Bentley has an app called Connection Client that keeps the user current. It would be nice to have something like that in Safe FME environment.
I would like to be able to change the default fill opacity in DI i.e. set it like a preset, or to be able to set it for more than one layer simultaneously.I spend lots of time changing the fill opacity in order to see through a layer or to find out if there is overlapping. Frankly said, I don't know when I really need 100% fill opacity ever.That said the simplest solution would be to change the default fill opacity permanently to 50%
One of the challenges that my office sees is that our GIS holds valuable asset attribution, which then needs to be entered into ETAP modeling for our engineers. These 2 systems work in completely silos from each other. There isn't a very easy way to get the data needed for the modeling databases from GIS other than to start typing it in. The ETAP model then follows a flow or order of detail of assets along a circuit. It's not spatially aware or to scale. These 'one line drawings' are referred to often by our electrical engineers and field crews. I'd love to be able to work between these 2 systems and seamlessly exchange data. https://etap.com/sectors Thank you for your consideration.
To be able to efficiently process raster I miss the option to read a raster not as a single object, but by "logical unit".For instance for these formats:MrSID / ECW: I want to "read by row" as these are row-based formats. So feature nr 1 will be all pixels on the first row of the raster (creating an image of 123923x1 pixels). Resulting in a number of features = the height of the raster.TIFF-files can be stored in 2 different ways. By tiles or by rows. For TIFF-files stored by rows the reading will be similar to MrSID/ ECW for TIFF-files stored by TILES the reading will be a bit different:o feature nr 1 will be all pixels in the first tile of the raster (creating an image of for instance 256x256 pixels). Resulting in a number of features = number of tiles in the total raster.This will significantly speed up processing of rasters and make FME able to read huge rasters without having them in RAM.
I often find I may have several FME Knowledge Center or other safe.com tabs open in my browser while I work on FME Server. Sometimes it takes me a while to find the right tab because all of these pages have the same icon. Would anyone else appreciate a distinct icon for FME Server?
Add new alias for Terminator transform IllBeBack.
Quite commonly I read in a zipped fGDB and would like to suggest that the auto-recognition of this format be improved. FME (2017.1) recognises a zipped fGDB as being of format "EDIGéO". fGDB is surely a much more common format and defaulting to "Esri Geodatabase (File Geodb)" would probably help many of us.
I think it would be really helpful to be able to set default styling for user annotations in FME Workbench. This could be done via a new dialog within FME Options, or there could be an option to right-click on an annotation and "Set As Default Style". If you went with a dialog within FME Options, you could include checkbox options to "Auto-color annotations by enclosing bookmark color" as suggested by @FMELizard and to "Make Word Wrap as Default" as suggested by @dorgin.
When lines are snapped to a single Point or Areas are snapped to a line, then this dropped Features should be ouput in a "rejected" or "dropped" port.Now this Features can only be found in the logfile.
When working with lots of PATH readers I find it a little hard to know which is which sometimes. While I know I can add an Annotation I think it would be great to be able just to rename it.
I have a workspace in which I would like to overwrite an existing Excel spreadsheet if it exists - it might or it might not depending on other things. If I leave 'overwrite existing file' set to 'yes', the workspace will fail when it doesn't find an existing spreadsheet. This also happens with file geodatabases.Perhaps a setting of 'yes - if existing' could be added?
It would be useful to be able to reference mapbox styles from within the HTMLReportGenerator. This would enable a user-defined style/background map from MapBox to be used. See knowledge centre question https://knowledge.safe.com/questions/50354/htmlreportgenerator-and-mapbox.html
Improve mobile UIEasier to view logs (hard to scroll all the way down)Easier to enable/disable schedules
***Note from Migration:*** Original Title was: Add more support for seismic data and make the SEGY and P190 readers more flexible I think that there is a lot more which can be done with FME in this space. There are a lot of users in the Oil and Gas community who use FME. Support for seismic data formats in FME is pretty limited at present. As a user I would love to be able to quickly create workflows to pull out the Navigation from my SEGY and stick it into a GIS. I love the CAT reader and think that this is something which could be integrated into reading the EBCDIC header. The SEGY reader should also support reading 3D Seismic.
Recently have an example where an attribute for a feature in an Esri Geodatabase where the GDB could be read by FME 2014 SP3 but with FME 2015, 2016 and 2017 the Reader dropped features with no warning message. Opening the GDB in FME 2014 Data Inspector shows some unusual characters in an attribute value.Tried the File Geodb ArcObjects reader and it writes a useful warning into the log:2017-08-10 17:30:45| 1.5| 0.0|WARN |Unable to retrieve feature from table/feature class 'IC_POINT'. This feature, and any other feature from 'IC_POINT' that cannot be read, will be skipped. The error number from ArcObjects is: '-2147418113'. The error message from ArcObjects is: {Unexpected operation [IC_POINT]}Requesting better messages/error detection when reading the GDB with the File Geodb API reader similar to the File Geodb ArcObjects or stop reading the file. It would be then possible to manage rather than losing data.
***Note from Migration:*** Original Title was: In the user attributes section of the excel-writer add the option to specify a hyperlink type. In the user attributes section of the excel-writer add the option to specify a hyperlink type.
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.
