Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Credit to Joshua Abaygar for this idea.Could row numbers be added to the Tester transformer so that it would be easier for users to create Composite Expressions?
Some transformers, like the tester and the testfilters, gives you an simplified version of the expression you currently have in the "Composite Expression" by representing each clause in the Test Clauses table by its respective row number. This may help you in reviewing your tranformer, but this may also become hard to understand if you have a lot of clauses included because you have to manually count the rows in order to locate which clauses the numbers refer to.I suggest that we should be able to show the row numbers within the table itself.
Good afternoon,I just experienced a situation that caused my workflow to stop because the source had a value that changed the datatype of a row. For instance, the table was expecting a date, but because the date was not formatted properly the SQL Writer thought that I was trying to pass a string into a date data type.Another case were this could have been useful is when my input has orphan records from a related table. the SQL writer had an issue because the source had items that violated database relationships-- meaning there was a record that didnt exist in the parent table.These two scenarios were painful to diagnose and currently there is no work around for them with out having to build another tool from scratch.Thanks for the help
Is the Community interested in FME Supporting SQL Server Analysis Services. If so, please add your thoughts, and specific use cases to this thread.From existing posts on the FME Forums, there seems to be some interest in reading from SQL Server Analysis Services, and pulling in the tabular model and cube.
It would be great to be able to populate the envelope parameters using a background map view and selecting 2 points to form a rectangle.
When FME prompts for search envelopes or bounding boxes in general, it would be really nice if there were an option to draw the bounding box on a map instead of keying it in one coordinate at a time. The background map setting from the Data Inspector could be used to provide the context.Ideally the same option would be available when FME Server prompted for a similar thing as well.See this site for inspiration: http://boundingbox.klokantech.com/ The FME Lizard wants to know -- how useful would this be for you?
Implement a reader for Autodesk Infraworks IMX file.
As I’m writing this FME 2024.0 just added support for multiple-port Python transformers this week (though that’s not supported on PythonCaller yet, users need to use the Transformer Designer and figure out how to use FME’s Tcl macros for that). That change has been a long time coming, but it is a massive step in improving the flexibility of Python-based transformers and is going to unlock some extremely useful use-cases.However, I believe it is still lacking a few parts, namely a hook to signal to the Python transformer that an input port is closed and will no longer be recieving any features (a role usually filled by close() when there’s only one port) and bulk mode transport that can vary across ports. For context, consider all the flow control issues I’m pointing out in this other idea:Making a rudimendary version of the sort of transformer I’m proposing in this idea isn’t too complicated and ends up looking like this: The idea here is using a FeatureWriter as a proxy for knowing when the PriorityIn port closes, and not letting any features from DelayedIn through before then, but otherwise letting PriorityIn features flow freely, and ideally letting DelayedIn features flow just as freely once PriorityIn is closed (in practice, FeatureHolder actually blocks all DelayedIn features until the last one has arrived). It wouldn’t be possible to make such a transformer with the 2024.0 Python changes alone, due to how close() is only called when all input ports have sent their “All done” signal, instead of having a separate close method that gets called for each port. Not being able to configure individual ports for bulk mode support is also going to be a problem, because DelayedIn features that come in early will probably need to be buffered until PriorityIn closes (which is illegal in bulk mode), but PriorityIn can still operate in bulk mode just fine, and in fact so can DelayedIn if PriorityIn is already closed by the time the first feature comes in.That means that, in order to fulfill that use case, two new methods should be added alongside the new input_from():input_port_has_support_for(self, support_type, input_tag), called once per port, but only before the first feature for that port comes in, so the behavior can change based on the state of other ports. has_support_for() would probably no longer need to be called if this one is present, based on my current understanding of bulk mode. input_port_closed(self, input_tag, is_connected), called when the upstream node(s) to a given port signals it has no more features to send, or some time between initialization and the first feature being sent to any port for ports that are not connected to anything.I’m only using the priority fence example because it’s the easiest I have to explain that requires both, but these additions would be very useful for a number of cases that are currently tricky to handle, whether with Python or other transformers.
Hi!As the attribute types are available more and more along the workspace, it would be nice to have ways to feed the AttributeValidator with those (type: number, string, char(20) etc..)For example :Attribute1 is defined as a stringimport type to ValidatorAttribute1 Type StringThis would allow to identify outliers in datasets early.A bit harder but i guess possible, use the cached data to generate rules (min,max, categories..).I currently use EDA tools for this as it is too slow to go through all attributes manually with FME.
The arithmetic editor in the PointCloudExpressionEvaluator (PCEE) is missing a dozen math functions compared to ExpressionEvaluator.It would be useful to have at least the statistical functions in the PCEE, such as min, max, average
I have source data with fairly expansive arrays that I need to convert to fields in a destination dataset. I can modify the source data with a couple listexploders, a bulkrenamer, and a featuremerger, but enabling the SchemaMapper to map fields to/from list elements would be much more straightforward.
The IfcZone groups are currently not supported by the FME reader. As these groups become more and more common in BIM models for building authorizations, I think it would be worth adding support of this type in the IFC reader. For the IFC writer, this would require allowing editing of groups, which is a bit trickier as it adds a new paradigm. It would nevertheless be interesting too!
I would like to be able to use thematic mapping in Data Inspector so I can inspect the values of different columns in raw data before I run translations. That would help me to find what data is relevant to the raw data I receive from our clients and would help me to answer my own questions of how I am going to transform the data by looking at how it looks spatially. I'm typically looking at multiple columns and unknown values in raw data.
It is currently not possible to access the database|web connections (username, password, host,etc.) with FMEObjects.Usage scenario:In the Python Startup Script (Scripted Parameters, PythonCaller, PythonCreator, Shutdown Script) we want to access an Oracle database via cx_oracle. While the Oracle Reader/Writer can use a Named Connection we have to expose additional parameters for our python scripts to be able to connect to the database.Please expose functions in (Python) FMEObjects to be able to use existing Database|Web Connection details.
The traditional AGOL reader has the option to read attachments using the "Include Attachments" option, which is not present in the "Feature Reader" transformer. Including the option to read AGOL attachments using the feature reader would allow for a more streamlined workflow using initiators supplying a WHERE Clause dependent on logic upstream.
FME should include a feature to automatically re-authenticate web connections. I have scripts that read data from AGOL and they constantly fail after maybe 30 days when esri requires the web connection to be re-authenticated. I'm not sure if the other type of web connections do the same thing but the connections are saved in FME option so maybe FME could re-authenticate each time a workbench is opened or run that contains one of the connections so we don't have to babysit the connections manually.
Per this question on the FME forum:https://community.safe.com/s/question/0D54Q00008bqqnFSAQ/how-can-i-allow-other-users-to-edit-my-fme-server-appPlease update the FME Server security model to allow alternate users (other than the original creator) to edit FME Server Apps without requiring "manage FME Server security permissions " permission.The use case for this is to allow multiple users in a team to be able to make changes/edits to an FME Server App configuration.
It would be extremely helpful if the FME ServerCloud UI could report the current server time and timezone directly to the interface. This is important when trying to work out schedules or understanding event timings. Currently there is at least one place where this is done under the 'schedule' trigger in Automations but it would really help if it was reported to the main interface, perhaps with the Server version and OS details in the bottom left corner of the UI. Cheers
It would be extremely helpful if the FME Server\Cloud UI could report the current server time and timezone directly to the interface. This is important when trying to work out schedules or understanding event timings. Currently there is at least one place where this is done under the 'schedule' trigger in Automations but it would really help if it was reported to the main interface, perhaps with the Server version and OS details in the bottom left corner of the UI. Cheers Migration Note: Idea originally posted on 2020-08-11
To be able to play a beep/sound when reached a certain stage of a translation similar to this: https://hub.safe.com/transformers/beeper
Dear FME Community,On a normal workday I was browsing through the Tools>FME Options and one feature there caught my attention: the ability to play sound events for different operations, like insertions, translations,etc. I immediately tried it out and started to assign some funny and ridiculous sounds to different actions.However, for the moment this feature only seems to work for insertions of objects (transformers, Annotations, Bookmarks,...). Imagine the excitement of hearing a triumphant fanfare when a translation succeeds, or the subtle acknowledgment of a gentle chime when a deletion occurs. These auditory cues would not only enhance the user experience but also provide valuable feedback during the development and translation process.Here are a few reasons why I believe this enhancement would be beneficial: Enhanced User Experience: Adding sound events for all actions would make the FME experience more immersive and enjoyable. It would create a sense of accomplishment and satisfaction. Improved Feedback: Sound cues provide instant feedback, allowing users to quickly identify successful or failed translation actions without having to constantly monitor the interface. This can significantly improve workflow efficiency and reduce the likelihood of errors. Accessibility: For users with visual impairments or those who prefer auditory feedback, sound events offer an alternative way to interact with the FME interface. By extending this feature to all translation actions, we can make FME more accessible to a broader range of users. Customization Options: Giving users the ability to customize sound events according to their preferences adds a personal touch to the FME experience. Whether it's choosing from a selection of predefined sounds or uploading their own audio files, this feature would allow users to tailor FME to their unique workflow and style. Overall, extending sound events to all actions has the potential to enhance the FME experience in meaningful ways. I look forward to hearing your thoughts and suggestions on this idea. Best regards,Warre
Adding a menu or option to the FME Cloud server that could be used to controle the zipfile name or prefix of the data download. Preferably with the option to give different topic/subscriptions there own flavour or combination. See for more info. https://knowledge.safe.com/questions/73985/create-custom-data-download-zip-name-for-fme-cloud.html
It would be nice if it was possible to create simple startup and shutdown scripts using regular transformers. This could e.g. be implemented using functionality similar to custom transformers:The tabs "Startup" and "Shutdown" would always be visible when you create a new workspace and would have fixed input/output ports. This could supplement the existing scripting possiblities (Python, TCL) and would make it easier for beginners and those with little or no programming experience.
When encountering a workspace with a startup script, it is somewhat hidden and you might not notice. It would be cool if these scripts had their own canvas representation. Maybe in some different color or design to not confuse them with actual transformers. So they can be seen, placed and access from the canvas.
I just follow this tutorial (https://knowledge.safe.com/articles/34364/using-a-template-file-when-writing-excel-data.html) try to write data to Excel table and found looks difficult, see attached image, write to Named Range in Excel looks perfect. Thank you. fme-exceltable-test.png
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.
