Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Either a new transformer (DateTimeSorter) or an extra option in the regular Sorter to sort on date/time attributes as depending on the notation the alphabetic/numeric options don't always give the right results.
Let's say that before an Oracle writer, I have a Counter and Stats Calculator. I use the total count of features as a condition in my Oracle writer to commit or rollback my transaction. If the right number of features were inserted, commit. Else rollback. Recplicating this with SQLExecutors is possible but involves a lot of hardcoding.
Please add PTS reader as native LiDAR format, because reading it as a CSV is veeeeeery slow.
It would be cool to have a "canvas cleaner" in the toolbar where when clicked remove all your inspector, logger & unconnected transformer. Also you could add parameters in order to let the user choose default options such as : keep logger
Rasterising Open Street Map should be much easier by allowing a stylesheet to be loaded into the transformer since manually entering 250 or so style lines is not practical.
There might be a certain mark or notification that shows the user that advanced settings are set (changed from default settings that come along with every writer/reader). I think that could prevent getting surprising results for users who are going to use another user's workspace straight forward without doing a deep inspection. A visible hint in the navigator near the corresponding reader / writer / feature would catch the attention and encourages user to investigate the special setting before running the workspace.
Simple python scripts as a drop-down in a transformer or easy (easy search, single click away) access beginner documentation. Starting with a blank python screen is intimidating for beginners or novice users.
***Note from Migration:*** Original Title was: AttributeManager - apply same action to multiple attributes by highlighting in list If AttributeManager is intended to replace AttributeKeeper/AttributeRemover, then it needs something to be able to remove a whole bunch of attributes easily. One way of doing this would be to be able to select (highlight) several attributes, then choose the action from the drop-down list and it would apply to all the attributes you selected. Ditto setting a value, etc.
Hi, I was trying to start following some of the topics, but there was no way for me to search the list without paging through them. Can you add a search there? Is there one that I didn't see?
***Note from Migration:*** Original Title was: Feature Connection Window Improvement: i think it would be great to have a visual cue such to indicate whether a source feature has been connected to a transformer or destination feature.
Hi,I am creating maps in PDF format, using among others the pdfpageformatter. That works nice, I manage to create various layers in each map. I also manage to define tooltips.What I would additionally like to do is:- By clicking on a text or symbol in the mapframe, certain layers should be switched on/off (Action button)- The tooltip text is displayed horizontally, e.g. : "field1: value1; field2: value2" etc. Is it possibleto arrange the tooltip text vertically,e.g.field1: value1field2: value2etc.?
It would be helpful to have a job history summary page that groups by job name and gives average run time for that job and number of times it ran. Having the capability to change the date range would be an added bonus (e.g. show me a summary of all jobs in the last 24hours). Currently I am achieving this by directly querying the FME Server POSTGRES fme_job_history table and sending the info via email. A cleaner approach would be the ability to do so in the FME Server interface and even drill down to specific jobs to find failures and view logs.
Add the ability to borrow a floating license for less than 1 day. This is useful when you have some people working in the evening or different time-zone, generally the come onto the network to check the license out but then want to disconnect for speed. You only want the license for your shift say 8 or 12 hours.
NOSQL Databases like amazon simpledb, apache cassandra, apache hbase -- indicate which in the comments. Note that MongoDB has its own card above. Note that FME currently supports Apache CouchDB, Amazon DynamoDB and Google Big Query.
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!!
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.
