Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
It would be good to have the ability to use the math function @round() inside the PointCloudExpressionEvaluator transformer. I would use it to round Z values but @floor() and @ceil() is not the same thing
Add the functionality so that fme can read a csv with quote (or other character) escaped fields that contain linebreaks.
When I use the string Editor or the Arithmetic Editor, The left side of the window will display the list of attributes, parameters, and functions. When I need to find a item ,especially a function. I often need through the scroll bar to find the function, if can add a quick filter function to the String Editor and the Arithmetic Editor, Will should be more quickly to find the item required.
***Note from Migration:*** Original Title was: Everyone attending #fmeuc should get a real life copy of all their knowledgecenter #badges :) Everyone attending #fmeuc should get a real life copy of all their knowledgecenter #badges
Make it possible to deploy Websites via the interface. There is a webserver running anyways...
In the HTTPCaller we can specify some settings that will be represented as a Header of the request. For example the Content-Type parameter specified in the Body section sets the Content-Type header of the call. This is not very obvious to see as you can still specify a Content-Type Header in the Header section. Often, if two different Content-Type Headers are set the request may fail, because they compete. The Authentication option also sets Headers behind the scenes.The Query Parameters show a similar behavior. If we set a Query Parameter it will be added to the end of the request URL behind the scenes. But if this parameter is already part of the URL both will compete.It would be nice if the Headers and the Query String would be updated on the fly when the URL or a parameter (Body, Authentication) is modified/added and vice versa. The Postman REST API Client is a nice example for this functionality.
FME Server can be configured in a distributed install to use an external database (e.g. SQL Server) and for high availability installs this is actually a mandatory requirement. It is not possible to use the embedded FME Server database in a high availability installation.The current FME Server configuration requires that the connection to the database specifies the port number that the database is communicating on. If the port number is left blank, then (for SQL Server databases) it defaults to 1433.Independent of FME, as a security measure, SQL Server can be configured to run using dynamic port allocation. So the SQL Server connection port changes over time.All online references that I have found state that simply removing the port number from the JDBC connection string should be adequate to make use of dynamic port allocation, however, when the port number is removed from the JDBC connection string in the FME Server configuration it is being replaced with 1433. I believe that this is being done by the FME Server code.My request is to allow FME Server to be configured to make use of dynamic port allocation with SQL Server backend databases.
Not sure if it is possible, but also import email adress from Active Directory-user using FME Server web-gui.
In order to save the space when resizing/adding more windows to the interface, please add a check box to enable the Logger window's word wrap option in Tools> FME Options >Appearance, to permanently save this effect.
***Note from Migration:*** Original Title was: Add common date/time formats such as FME Date/Time (%Y%m%d%H%M%S) to Source Date Format in DateFormatter Add date/time formats such as FME Date/Time (%Y%m%d%H%M%S), Locale Date (%) to unknown - Automatic Detection in Source Date Format drop down list in the DateFormatter. As well as being handy, it would help to avoid confusion - see https://knowledge.safe.com/questions/42603/warning-tip-ymdhms-datetime-values-in-csvs-are-not.html
The DateFormatter doesn't recognise <date>T<time>Z format for example which is valid as of ISO 8601. Removing the ending Z is a workaround but it would be nice if the transformer accepts any valid ISO date/time as web services tend to produce all spectrum of valid ISO date/time strings.
Include some helpful hints in the spatial filter parameters for those of us who struggle to remember which way round the tests are performed
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.