Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Consider adding support for Survey Figures in Civil 3D.
We saw it at the FME Days 2019, the problem to show a lot of people in a presentation a big workspace. Would be nice to have a Prezi like Workbench presentation mode. Or to get a from up to down dataflow mode where you can add comments for presentations also for Powerpoint.
It would be very useful if the tester Transformer would provide a preselection of the attributes depending on the selected attribute on the Right Value page.
It might be useful if there was a transformer that kicks a post process after completion of the main translation. A potential use case is to upload writers' outputs to a web server in the same workspace without writing shutdown script. The FeatureWriter coming in FME 2016 may also be used to embed such a post process into a workspace, but the expected transformer can be used not only for writers' outputs but also for outputs from transformers such as XMLFormatter. The transformer doesn't have input ports. It outputs feature(s) after the main translation has completed.The transformer works only in the Main workflow. It does nothing in a custom transformer and custom format.The executing order of two or more ones should be controlled through their parameter settings.Adding the ability to some existing starter transformers (e.g. Creator, PythonCreator, SQLCreator) is also a choice.
It would be great to have an "attributes that must differ" option in the LineOnLineOverlayer (and probably the intersector too). It would make it more straightforward, for example, to find lines that intersect between discrete datasets without reporting intersections within the same dataset.
I think it would be an enhancement if one could give the KMLStyler not only a hardcoded name but also a name via an attribute. This makes it easy to give different features it's own KML-styling according a feature's attribute.
To be able to fully automate the FMEserver it is nescecarry to be able to create the Automations by API methods.The idea is to extract all sources and targets of all workspaces or a set of workspaces on the server.Put them in the correct order of dependency and try to parallelize as much as possible.So the FMEserver is used most efficiently.If yoou think about cloud and effincient use of Fme engines this is the most optimal configuration.
***Note from Migration:*** Original Title was: ARCGISONLINEFEATURES and ARCGISPORTALFEATURES to support setting a coordinate system by WKID Hi all, to link a KB question I had about how to do this (you cannot yet), when creating a new feature service the underlying API supports specifying a coordinate system by specifying a well known ID (e.g. EPSG number) but this is not exposed in the writer, and the default Web Mercator projection is used. Feature services are more likely to contain 'real data' captured at large scale or tied to survey control, and not features tied to a web tiling system. The portal will attempt a suitable geographic transformation but even so this can move your data. Lets support a WKID so coordinates go in accurately.
Route 3D objects to this video gaming format for end users to walk through and explore
It seems FTPCaller uses these ciphers on SFTP: aes256-cbc,rijndael-cbc@lysator.liu.se,aes192-cbc,aes128-cbc,arcfour128,arcfour,3des-cbc However some of these are insecure and not recommended to use and therefore not possible to use on newer ssh2-servers. Supported ciphers currently is: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc ref: https://www.freebsd.org/cgi/man.cgi?sshd_config(5)
This is not an idea, but a publication of a new reader format: (Borland) Paradox. Hope it may come in handy for someone.It's (still) not possible to upload custom formats based on Python to FME Hub, so here's my take on how to publish it.Attached is a ZIP with all the necessary files. All files are stored with paths relative to the FME_HOME of your installation, so they should be unzipped with that in mind.The reader uses the "pypxlib" library for handling the Paradox tables, and ought to handle all parameter types. However, my test data set is limited, so please report any problems with other data sets to me.Although there are template files included to support both writing and geometry handling, it's sofar just a pure alphanumeric reader. But with FME it's easy to generate geometry using embedded coordinates. Maybe writing and geometries will be added in the future.It supports a single parameter, the code page of the DB file. It defaults to "cp1252", i.e. Windows Latin1/ANSI. Please refer to available Python docs on code pages if cp1252 doesn't work for you.paradox-format-lifa.zip
***Note from Migration:*** Original Title was: RasterExpressionEvaluator should support duplicating rows and other copy/paste functionality The various tester and attribute creators allow one to copy/past or duplicate a row in it's entirety. It would be nice if the RasterExpressionEvaluator had the same right-click context menu as the other transformers.Currently right click does nothing, you have to go into the cell and select the contents to copy, and then go into the subsequent cell and paste and then set the interpretation manually.
It would be super handy to land on the FME Server scheduling page and tick several schedules and then push a "Run Now" button. The button would sit with the New, Remove, Duplicate etc buttons to issue the selected job schedules immediately, rather than having to click into each one and tick 'Run Immediately'.
Recently my FME Server encountered an unexpected shutdown.As a result my daily scheduled job did not run.I did not check that on restarting my server what caused me to loose information.I would like to be able to schedule a job to run after the FME Server startup.That would allow critical jobs to be run after an unexpected restart of the server (which according to Murphy always happens at the time a job is scheduled to run).So next to "Immediate" and "Interval based" I suggest "At startup" to be an option for a schedule to run.
When I upload a file with sidecar files, this triggers the directory watch to start a workspace for each file which I don't want and uses up my engines. It'd be great to have the option to add file type filters so that the workspace is only started if I upload a *.shp for example.
A workspace subscribed to multiple notifications, fires on every notification. Effectively the multiple-subscriptions are evaluated as a logic 'OR'. A workspace runs on notification '1' or '2' or '3'.As described in my forum post the usability of notifications would greatly improve for me if I could evaluate them as 'AND'. A workspace should run when notification '1', '2' and '3' have been given.With this I could improve the distribution of tasks and workloads in a large transformation process.e.g.: When the new populationdata is available AND the new boundaries have been processed, I can recalculate the population density.Please read the linked forum-post for more details about the nature of this idea.Kind regards, Martin
I find it quite easy to whip up a workspace to use in FME Server in about five minutes, but it takes me way longer to create a way for an end user to run it.Currently I can:Have users run it through a simple URLGive users access to FME Server with a guest account to run it thereCreate my own custom web page with a form/interface for parametersBut a URL doesn't work when I want the users to provide parameters (most of the time) and I usually don't want to give users access to the FME Server interface because it gives them access to other workspaces and functionality they don't need to see (and forces them to log in).Creating a custom web page is good, but it can take a long while to set it up (plus where do I create it?)So, I'm thinking it would be useful to have a "Run Only" page on FME Server; i.e. I can provide a link to a user and it takes them to an FME Server page. The page allows the specified workspace to be run, but it doesn't require a log in, and it has no menus or advanced content.Something like this:Any thoughts or votes? Does anyone else find it hard to create a quick way to share a workspace to run it, or have any ideas on how it might be implemented?
Currently the datadownload service only supports output from writers. It would be nice to also support featurewriters. For more information see Question
User works at a higher level and simply specifies the key elements Trigger: Email, s3, File, message, etc. Action: workspace that is to run Delivery: email, S3, Directory, Ftp, web socket etc.
Outlook - reminder for when license expires: check. However when noone see that notification..... it expires and everything will be a disaster. So:Auto send e-mail to all users (or only admins) - 7 days before a license expires - and also 1 day before. From FME Server.This way all the users that do not know about licensing are atleast aware that the license might expire at a certain time - even though there is another person responsible for renewing the license.
A security audit of an FME Server application has highlited that users can have simple passwords to login as a problem. It would be nice to be able to set the rules a users password must adhere too.
It would be very helpful if you had an option for a concatenation of workspaces in the scheduler of the FME server.At the moment, I use an additional FME process (with various FMEServerJobsubmitters) to concatenate the workspaces.I would prefer it, if you could set this chaining in the admin interface of the FME server for the scheduled jobs.This would not require an additional management process in the future.In my case, I can not set up several scheduled jobs because they have a temporal dependency. For example, the following process may be started after the previous one completes successfully.
Since you now have the workspace viewer it would be helpful to have a minimal workspace workflow designer web UI where one could chain/link/connect multiple workspaces to run in certain order with success/fail logic.I feel that FME Server does not handle parent / child workspaces very well (more it’s just seeing the master workbench). We use this a lot since a lot of our datasets have to process in a certain order.I would use this by linking the flow of workspaces, some can run as soon as an engine is free, some have dependency’s etc.This would solve the challenge with the master locking up an engine when run in sequence and also we can get log files and reporting as default on child workspaces
Currently, in FME Server the number of active tokens per user is limited to 1. For some applications it would be useful if multiple tokens could be used per user.
This idea has been created to track interest from the FME Community for displaying line numbers for the Log on the Job Details section of the Jobs Page (pictured below). For example, the line numbers could appear when the 'Show Time Stamps' is toggled on. Please add any additional comments or suggestions!
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.
