Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
As an FME user, I want a section for common code snippets (math, string, date expressions) to be more accessible because it can be difficult to find exactly what you are looking for by sifting through the Q&A forum. It would be great if there was a section on the FME Hub that made it easy to search for these expressions.
I would like the ability to globally remove all extra vertices from all connections in a workbench.
ShortestPathFinder can currently handle either one-way or two-way streets, but it doesn't handle a mixed network well. Setting Cost Type to "By Two Attributes" and setting the reverse cost to a large number for one-way streets works as a workaround, but it's not very elegant and not foolproof. It would be great if we could indicate that a street is one-way by setting the reverse cost to negative or null.
It would be great to be able to use the DateTime functions into the default values when we create a user parameter.More explanation here
I don't think it is possible to do that in FME right now, but it would be cool to be able to modify the attributes font when writing a XLS file. I like my attributes to be in BOLD when I create and share a XLS. Thanks Safe!
Is it possible to add the Tolerance parameter for the Spatial Filter as well? I have some issues with the 12th decimal number in an AutoCAD file. So, I was disappointed not to find this option for this Transformer.
Apply styles to your the HTML output of the HTMLReportGenerator or other HTML before writing out via the HTML writer. This could include numeric precision, font styles, heading levels, list bullets etc.
Add support for different shapes for annotations and bookmarks. Different shapes could include e.g. circle, rectangle with rounded corners, cloud, arrows, etc. Changing the shape could work by selecting a bookmark or an annotation, and a row of shape icons would appear above it, and the user could select the shape.
***Note from Migration:*** Original Title was: Database writers: support Handle Multiple Spatial Columns per table instead of per writer It is not possible to write multiple spatial columns to some tables and one to the others in the same writer.Using 2 writers (or the single and multiple spatial column tables) makes the first writer to write the tables on the fly but the 2nd (and subsequent) writers to hold all the features and write out when the 1st writer finishes. It eats up memory when both writer gets huge amount of features (eg. updating basemap).Would it be possible to set single/multiple spatial columns per table so no 2nd (blocking) writer is required? (SQL Server and Oracle writers in my case but PostGIS and other databases could work the same way)
Your ideas are extremely valuable to us! They help us make the product even better, and give us insight into the common or innovate ways you use FME in your workflows. We take these ideas seriously.To help us understand your idea, please consider addressing these key questions:1) What exactly is your request? Explain the idea in as much detail as possible. Examples, mockups, and comparisons can really help illustrate your vision.2) What challenges does this help solve? Tell us exactly why this idea will help you and your organization – and of course, benefit the thousands of other FME users! We want to understand where this fits into the puzzle and how its value can be measured.Does your idea already exist? If you really like the sound of an existing idea or have something to add to it, please use the voting and commenting capabilities. Votes and comments help drive product development and increase our understanding of the problem.An Example of a fully formed Idea:I use FME every day at my job managing water resources and struggle to find relevant data for my region. To help my mission, I want to be able to read daily satellite imagery and associated metadata from the Planet Data API so that I can use it to analyze vegetation data for my area of interest which will help my organization to prioritize areas requiring more resources.We believe that following these suggestions will give us excellent information and lead to important improvements in FME. Thank you for contributing!
Currently, the only way to access the majority of the FME Server REST API functionality via Workbench is to use the HTTPCaller.The problem with this approach is that you need to hard-code the server URL into the HTTPCaller (or use a published parameter) but this is not dynamic between environments. If I want to publish a workspace from DEV to PROD, I need to go in and update the server URL.It would be nice if a named FME Server Web Connection (which already includes the FME Server URL) could be used for both authentication and base URL configuration.A simple wrapper around the existing HTTPCaller would probably be all that is required, so that the base request URL is automatically supplied from the web connection.If the above is too difficult, please create a transformer to allow for the web connection URL to be queried in the workspace, so that this can be passed in to the HTTPCaller.The ultimate solution would be to have a full FMEServer_API_Caller transformer that would allow REST API queries to be dynamically built within the transformer... but that's probably asking too much. :)
The FeatureWriter releases the features to the output ports when all of them are written. Holding a large number of features eats up memory.It is normal for some formats. However there are formats (eg. databases) where features are written one by one or in small groups. Releasing the features from these writers would make the FeatureWriter non-blocking and could decrease memory usage. The summary port could still be released at the end like Cumulative and Summary ports of the StatisticsCalculator.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.