Shape the future of FME with your ideas
New and Open ideas are awaiting review or have been reviewed by our Product Management team, and are open for commenting and voting.
Hello,There is an Automation Writer to configure the geojson to be sent as a message. This is great, especially the debug mode to see it locally. I wondered if the generated geojson could be also imported as a reader for the subsequent workspaces.In the current examples, I have only seen ParameterFetcher used, even the geometry is extracted as an attribute (and so replicated..). It is a bit painfulIs there some work in this direction already? Thanks for the great work, FME Flow UX is getting better and better!
Can you update the API call to enable us to see who ran a job? I am trying to better support my users but I would like to be able to include the user that ran the automation into an email that I receive when a job fails.
With the following ministerial decree, Italy formalised RDN2008 as the new official reference system.It would be appropriate to include the EPSGs referring to the RDN2008 datum natively in the software, in order to avoid Italian users having to write the definition of reference systems by hand.The list of reference systems can be found in this post
Dear FME Enthusiasts, I'd like to draw attention to a current limitation within FME regarding job statistics on Flow Streams. Unlike other FME processes, the Flow Stream lacks the capability to provide detailed job statistics due to its reliance solely on translation completion. While other FME processes exhibit CPU usage metrics, the Stream does not offer this visibility. Introducing job statistics for Flow Streams would immensely benefit the community. With access to CPU usage data specific to Stream processes, users would be empowered to optimize their workspaces, potentially reducing CPU load. Moreover, this enhancement would enable better monitoring of resource utilization. In our company, we've observed that a running Stream consumes approximately 4-5 seconds per hour. However, despite this resource consumption, monitoring tools such as the database and job history reflect zero usage, even after the Stream has terminated. Effective management of CPU resources is critical, especially for Streams, to avoid excessive CPU hours on Dynamic Engines. Providing insights into CPU usage for Streams would aid in this endeavor.I encourage the consideration of this enhancement to improve the monitoring capabilities within FME, benefiting users across various workflows. Reference: FMEFLOW-21844. Examples of jobs completed and CPU usage
When resolving fields it would be useful in certain instances to have the option to NOT have the _resolved field set to <null> when the original value can’t be found in the domain. In these instances it would be useful to have the original value put in that field:For range domain fields: There is no code-description look up so all values are currently set to <null> in the _resolved field. All data from the original field is lost. For coded domain fields: When the coded value isn’t found in the domain the value is set to <null> in the _resolved field but there are instances where it would be good to have the option to not lose the original value (maybe also include a warning in this instance as stated in this other idea).
You cannot move files and folders between an FME Flow resource folder and a user-defined network resource [https://docs.safe.com/fme/html/FME-Flow/WebUI/Manage_Resource_Connections.htm]. Please add this to FME Flow functionality!
The user has interest in an OData Writer. The user explains that writing seems to be possible using the HTTP caller, but they are wondering if there are plans for an OData Writer since there isn’t one. They want to make sure they are building their processes correctly in FME.
I would like to set the Tab Color when writing to an Excel spreadsheet (without the need for a template file or Python script). Community member alc33 asked a similar question 4 years ago:
Not sure why this is not already implemented, but it is something that would be extremely helpful. I use view extents hundreds of times every day.
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.
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?
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.
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 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
On the Run Workspace Page in FME Server there is an optional parameter 'Email results to' which can be used to send out Workspace results if the corresponding Subscription has been configured. When I create a Server App I would like to have this parameter listed as optional to 'Show in App' alongside the workspace published parameters.
It would be great if within your repository you could create sub-repositories. Like Sub folders. I find I end up with so much within one repository and wish I could organise it better. I could create new repository but the workspace is relevant to the repository its in and I don't want to end up with 50 repositories either- it would be handy to be able to drill down through a repository so I can organise better
We have a service which we'd like to publish on an FME Server app - no frills, nothing too special, however, we'd like to be able to restrict the upload file size because we don't want users uploading huge files. As far as I can tell there is no way to restrict a file size in an FME Server app. This would be a great addition. I know I can check the filesize in the workspace by using a path reader but it's a bit hacky and not ideal.
It would be great if there would be an option to stream result of one workspace in the automation. I presume max one workspace per automation would have that option.Alternatively, there could be new action in automation builder that would stream result.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.