Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Simplified exposure of any ERROR level events in job results. So rather than have to wade through and find and open log files, and then try and find the error (something that most end users cannot do), publish whatever the ERROR level event(s) are somewhere nice and obvious if the job fails. Should increase the ability to self-help, at least a little.
Add dynamic log filtering to FME Server just as it has been added to FME Desktop 2018. It would be a time saver over having to scroll through multiple pages of long log files in one's web browser or downloading the file and scrolling/searching through it.
Many settings on the FeatureReader/Writer transformers are format agnostic (e.g. the transformer name). It would be great if the transformers could be configured to NOT re-read from database connections when these types of settings are changed.I almost always pass in my connection details as attributes or published parameter values so having to navigate the file system to find an SDE connection file, or specify a database connection each time I make a minor change to the transformer settings is frustrating. It's a minor inconvenience, I know, but just one of the "little things" that I think could be easily fixed.I used to be able to work around this in many cases by editing the settings directly in the Navigator pane but in FME 2017 this option has been removed as the settings are more tightly integrated with the transformer.
Add MapInfo Workspace Reader/Writers. Read and write .wor, .mws, and This would be great especially if the .mxd reader/writer were implemented.
An internal Alter/Notification would be very helpfull to monitor the FME Server without additional software.So an Notification should be triggered, if one or all engines are down...
I want to have an pause-mode (break) to do changes in large workspaces. For example to change connections or transformers without an internal validating the workspace after every action.In very large workspace it may take a long time for FME to ckeck, if everything is valid after every change.So i'd like to have a possibility to stop this validation temporally.
Would be nice if the ChartGenerator would be able to produce space time cube visualisation (in 3D as a bonus). Could also be an option for an separate transformer. I can do it now with the R caller but would be nice to include it in the software itself.Input route/point data with time and date + raster or spatial as 'back/underground'output: (3D) Space time cube, Space time path or Space time prism.Also, everything with space time in front of it just sounds cool. :)Example
HiAGOL has no UI to create an attribute index, there is only a REST endpoint:https://developers.arcgis.com/rest/services-reference/add-to-definition-feature-layer-.htm#example2if you need to make queries on a key field an attribute index would speed things up.
Add reading and writing support for object properties such as Constraints, Identity Data, and Phasing among others for DWF.
My organisation uses a floating licence server which contains licences for different FME Desktop editions (e.g. Professional, ESRI, Database etc.). However, the end users often do not know which edition they are using and sometimes end up using inappropriate licences for their roles.I am aware this information is available under Help > About FME Workbench, but it would be useful if users could easily see which edition they are using each time they open the application. This information could be displayed either:On the splash screen – after ‘Checking license…’ the edition could be displayed below ‘FME Desktop 201X.X’On the status bar – next to the FME version/build number
Hi,I hope that oneday that FME could have a voice contrl feature to make converting data so easy like to use Alexa.Cheers,Jing
It'd be cool if there was a waterfall view of a running workbench similar to the one in chrome tools so you can see how long each part of the model is taking in a graphical manner, rather than trying to interpret the logs. Each reader/transformer/writer would be a line on the table. If a transformer rejected features it could be highlighted in red. You could also have columns with the number of features that pass through each transformer, its start and end times etc
It would be nice to have the ability to convert a writer into a reader. In some occasions you write a dataset and then want to use it right away.
Include the options for setting the time limit for an objects expiration.
Until now, FME is creating new dgn/dwg files with the help of writer.But there is no option to update / change / delete specific feature i.e. changing the colour of line from red to blue / deleting the specific feature / changing the layer/level / etc... This is something like UPDATE in database. If we have to update small changes then we have to create entire dgn/dwg file which is not advisable...
The answer to the following KB question lists some limitations on the S3Uploader (and I would assume the other S3* transformers):https://knowledge.safe.com/questions/31838/s3uploader-and-network-proxy.htmlSpecifically, the limitations are listed as:...there are some non-supported configurations:Custom proxy mapsNTLM or Digest proxy authentication (as seen when you go to Tools-->FME Options-->Network Proxy-->'Use Authentication')It would be great to see the S3* suite of transformers updated to honour the full set of proxy configurations. We are specifically interested in NTLM authentication, but why not bring it inline with the rest of the FME software and support everything?
In all parameter boxes, there is today an option to "Save As My Defaults". This would extend this to allow named sets of defaults so you could have several setups that you flip between in a parameter box.
libpostal is a C library for parsing/normalizing street addresses around the world. Would be cool to use this to prepare addresses for geocoding.https://github.com/openvenues/libpostal
According to the documentations, the @StringLength function has to be equivalent to the StringLengthCalculator transformer. i.e. it should return the number of characters in the given string.StringLength(str) Returns the length of the input string. Equivalent transformer: StringLengthCalculatorhttps://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Workbench/!Transformer_Parameters/StringFunctions.htmStringLengthCalculator Usage Notes Note that in non-ASCII character sets, the length is the number of actual characters (some or all of which could be multi-byte) in the string, which may not match the number of bytes used to store the string.http://docs.safe.com/fme/2019.0/html/FME_Desktop_Documentation/FME_Transformers/Transformers/stringlengthcalculator.htmHowever, the function could return wrong number if the given string contains muti-byte characters.For example, if the given string was '???' with UTF-8 encoding, the number of characters should be 3 and the StringLengthCalculater returns 3 correctly, but the @StringLength function returns 6 on Windows. It seems to return the number of bytes, but the correct number of bytes is 9 for the string with UTF-8. That is, 6 is not either number of characters or number of bytes.I think the implementation of the function should be fixed so that it exactly complies with the documentations, i.e. always returns the number of characters as well as the StringLengthCalculator.
Would be GREAT to have a matrix and search similar to this: https://www.safe.com/fme/formats-matrix/#! - BUT it shows which GEOMETRY types are supported for READING and WRITING for each format. For instance that SHAPE can read POINT,LINE,AREA and WRITE POINT,LINE,AREA but not SURFACE or MESH.When working with different kinds of 3D-formats you often need to convert between "similar" 3D-objects and it might be difficult to find the right 3D-format.
Hey guys,The map info extended writers write speeds are excruciatingly slow. It is taking nearly 2 days to write 2 million features. This is to the point where I have written a mapbasic script at the end to convert a mid/mif to mapinfo extended rather than writing to mapinfo extended in FME. This is a pretty ugly thing to do. Regards,James
It happens frequently that we would like to ensure that a workspace in FME Server runs only once or want to limit a workspace from taking all resources. Tagging engines is useful but is limited and in most cases doesn't deliver the real optimal result. If workspaces or repositories would have the advanced option to define the maximum instances that can run simultaneously or/and the option how long they can stay in the queue a lot of these weaknessess could be removed.
For the workspaces published on the FME server, a setting would be good, with which you can choose that this workspace can only be started if it is currently not running. So a parallel execution can be prevented. Thus, when using multiple engines can be prevented that the workspace is carried out in parallel and thereby disturb themselves. Even using just one engine, it may make sense to stop this process from queuing up.
When you've run a Workspace with multiple Writers with multiple FeatureTypes, it would be great if you could window select all the FeatureTypes you want to inspect and then either right-click to Inspect or activate the FeatureTypes toolbar popup to be relevant to all FeatureTypes that have been selected.
Option to choose and set glTF appearance/shading setting for Cesium 3d Tiles writerFor example, options to set metallic factors, roughness factors etc. Or option to choose if for example "KHR_materials_unlit" extension is used. Materials unlit extension would improve appearance especially for buildings with image textures. Now buildings with image textures tend to get too dark because of the shading, and changing these settings manually is time consuming and difficult.
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.
