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 nice to have a transformer that converts attributes from Cartesian angle, measures counter-clockwise from the positive x-axis, and Azimuth, measured clockwise from the positive y-axis (ie North), and back.Or possibly even a generic specify axis and direction of rotation for source and destination.
I have a published workspace on the FME Server (2017) that read an Excel spreadsheet from one resources folder and writes to another.This workspace failed (for a now known reason), but kept both source and destination spreadsheet locked.Now I am unable to delete, overwrite or do anything else with these files (and I have the fmeadmin role on FME Server) and can not successfully re-run the workspace.Even restarting the FME Server services did not help.And that option needed support from the System administrator.I would like the option to "Force Delete" files from the FME Server resources page to avoid having to go to the server and involve too many administrators.
When Joiners fail they output the following in the logfile:2017-05-16 10:42:17| 53.6| 0.0|ERROR |BADNEWS: 0 matches were found in the table used by relation `Joiner_4' (which is supposed to be 1-1) -- key values were: X== `' (relation.cpp:694) 2017-05-16 10:42:17| 53.6| 0.0|ERROR |0 matches were found in the table used by relation `Joiner_4' (which is supposed to be 1-1) -- key values were: XXX== `' 2017-05-16 10:42:17| 53.6| 0.0|ERROR |(featproci.cpp:701) - (cmrelate.cpp:227) - (relation.cpp:694) 2017-05-16 10:42:17| 53.6| 0.0|ERROR |BADNEWS: A fatal error has occurred. Check the logfile above for details (dynafact.cpp:315)Also write the complete feature that failed in the logfile (similar to putting it through a Logger) for instance:2017-05-16 10:42:17| 53.4| 0.0|INFORM|=========================================================================== 2017-05-16 10:42:17| 53.4| 0.0|INFORM|Joiner_4 - Logg failed feature: 2017-05-16 10:42:17| 53.4| 0.0|INFORM|+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2017-05-16 10:42:17| 53.4| 0.0|INFORM|Feature Type: `Joiner_4_Logger' 2017-05-16 10:42:17| 53.4| 0.0|INFORM|Attribute(32 bit integer) : `x' has value `1' 2017-05-16 10:42:17| 53.4| 0.0|INFORM|Attribute(string) : `y' has value `fads.fds.fsad.fdsafdsa' 2017-05-16 10:42:17| 53.4| 0.0|INFORM|Attribute(32 bit integer) : `z' has value `fasfasd' 2017-05-16 10:42:17| 53.4| 0.0|INFORM|Attribute(32 bit integer) : `asdf' has value `ffasdfsda' 2017-05-16 10:42:17| 53.4| 0.0|INFORM|Attribute(string) : `134' has value `234234' 2017-05-16 10:42:17| 53.4| 0.0|INFORM|Attribute(string) : `fasdf' has value `32434'
While debugging it's handy to switch on/off Inspectors in the workspace.Previously it was only possible with right-click and then pressing enable/disable.But now with the Parameter Editor it saves the user a click, when adding the toggle button there.The gain would be even bigger if this is possible for a collection of selected transformers and/or connectors.
Hi, in many cases where a workspace fails the default error message is "A fatal error has occurred. Check the logfile above for details". This error message is for example shown if a FeatureReader fails due to an invalid dataset. This isn't very helpful, especially if the workspace has been started via FME Server or has been called via the REST interface where the user might not even have access to the log file. Better error messages would be especially helpful when combined with this idea: https://knowledge.safe.com/idea/27882/errorcatcher-transformer.html What do you think? Greetings, Dennis
Hi,It's not often that you have the option to run lengthy translations manually. I have wrapped repetitious tasks into jobs in the scheduled tasks manager, and just run these ad-hoc.However, this yields a need to check the log files for any issues, preferably in a rational manner (i.e. not by manually browsing thru them).The log file can of course be read as a TEXT file, but this is rather unprecise, as the line markers (INFORM, WARN, STATS etc.) are too few and coarse for a real analysis, and used in a somewhat "easy going" manner.I suggest that a "FME Log File Reader" is created, or that the content of the log file gets an overhaul with searchable content as the intent.E.g., the summation at the button is not "STATS", but should rather be something like "SUMMAS".CheersLars I.
Idea from FMWT 2017 at Lyon, France :Add new format attributes to get modified date, created date and accessed date for all file based readers :fme_modified_datefme_created_datefme_accessed_dateWith these, you could process files only if date > XXX or date != reference.@KenAtSafe
***Note from Migration:*** Original Title was: Compatibility of old workbenchs with new versions of FME. Currently, every transformer with new version is removed.
As being a fan of both FME Desktop and Open Data, I would wish if Safe has a free/community edition for non-commercial/personal use towards Open Data readers and writers only.This could promote Safe's recognition for supporting Open Data ETL integration. This edition is not meant to be a full functionality of the standard version of FME Desktop which has numerous proprietary readers and writers, it should include the basic OGC-standard common readers and writers.
Hi,We're receiving multiple XML files from a customer on a daily basis, and we know for a fact, that their XML export utility doesn't encode attribute values correctly, sometimes resulting in invalid XML files.This of course makes FME break down, but this typically happens only after hours of converting the valid parts of the XML file.It would be a nice feature - and very simple to add, I think - to (optionally) validate the basic XML syntax _before_ any conversion is attempted. This really ought to be mandatory, but might also be an optional setting. It is not validation wrt one or more schemas I'm talking about, just a bare-boned XML file syntax check.CheersLars I.
Is it possible, when publishing a workbench to FME Server that you code to provision for checks to ensure all DB connections are embedded and prompt / message accordingly?The message below is too generic."Web services access failed (Not Authorized) - Ensure that username and password fields are correct, and that user has sufficient privileges."Keep up the awesome work though Team!!
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
The command file method could be efficient if individual translation wouldn't take a long time but the number of times to run the workspace was very large. It would be nice if the WorkapsceRunner would have an option to create a temporary command file and run the workspace multiple times with the Command File method.Batch Processing Method 2: Command File
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.
Put a pin icon on the helper windows (view > windows) in FME Desktop. When pinned the window stays open (as it is the behaviour now all windows are pinned); when not pinned the window auto hides if you have not moused over it for say 5-10 seconds (configurable in settings?). The window hides to a narrow side bar, when you mouse over / click the sidebar, it opens back out. fme.png
***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
It would be very nice if it would be possible to merge to knowledge center accounts to one. Currently I have three accounts (of which one is deactived) and I only want to keep one. It would be nice if they could be merged into a single account keeping all the experience, badges, etc.
***Note from Migration:*** Original Title was: It would be useful sometimes if the inputs for disabled readers/writers are not shown on the dialog box that appears when you hit the "Run Translation" button with the "Set Workbench to Prompt Before Running Workspace" Option
Make it possible to deploy Websites via the interface. There is a webserver running anyways...
Sometimes a custom reprojection algorithm that isn't supported by the regular reprojection engine is needed. With the current Python API it is possible to iterate over the feature geometry to recalculate the coordinates, but it can be pretty complex when having to account for all the different geometry types, aggregates, donuts, 2D/3D, arcs etc.It would be very handy if the Python fmeobjects API could provide for a method (e.g. "performCoordinateFunction") for calling a user-defined function on each coordinate using a callback mechanism.Example:def myCoordinateFunction(x, y, z): x = x + 3 y = y - 3 if z > 100: z = z * 2 return x, y, z feature = FMEFeature() feature.addCoordinate(55, 81, 233) feature.performCoordinateFunction(myCoordinateFunction) After calling the performCoordinateFunction with this sample method the geometry would be situated at (x=58, y=78, z=466). The geometry type and composition should otherwise remain unchanged.
Read/write VRT http://www.gdal.org/gdal_vrttut.html
Some ideas are not necessarily an idea for one of the current FME spaces. It would be nice to have a fourth "FME - off topic" space or something like that. It could deal with the knowledge center, support or all other sorts of stuff.
I work with spreadsheets that contain the start coordinates of a line, and then azimuths and inclinations for all the line segments. There is already a 2D version in the form of the 2DDirectionExtender; would love to have this in 3D for drill holes, pipelines, etc.
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.
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.
