Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
I do not know if this is possible or not, but it would be nice to have the ability for Readers and Transformers that connect to databases (SQLExecutors, Feature Readers, DatabaseJoiner), to have the option to close the connection after the data has been read out. Currently the connections stay open for the entire ETL run, even if the data has been read out, so if the ETL takes 35 minutes to run, and we have a firewall timeout of 30, the ETL will fail even though it has already read out all the data from the source, as it cannot close the source connection, as it has been terminated by the firewall at that point.
FME has recently integrated property sets support.Would be nice if values from properties that can be chosen from a drop down list were supported too.
When using a reader to a very long path and filename. Or to files within a zip-file with very long paths and filenames FME usually gives "File not found"-error in the logfile. Give a better explanation to the user when the path is very long so the user can just move the files to a folder with less letters.Or when reading a file with long name (more than 260 characters - mspoweruser.com/ntfs-260-character-windows-10/ ) try to move the file to FME-temp folder and then read it from there.Since some project-disks are long by default it is not possible always to shorten the path where the original data lies
When gathering a list of relevant values, it would be nice to be able to compare an attribute value directly to these values, to determine whether it's found in the list or not. Now I must create a concatenated attribute, which must be comma separated, prompting all kinds of formatting problems. Simply comparing to a list would be much cleaner and efficient. This is also relevant in all other transformers that utilize test conditions, like TestFilter et.al.
When configuring a distributed FME Server install, it seems that there are still ports opening in the high numbers, that are not controlled by setting the FME_SERVER_PORT_POOL. These are causing problems where firewall restrictions mean not everything works as expected in FME Server.It would be useful to add port_pool configuration parameter for the web app (tomcat).
This should be a fairly simple addition, but it is almost certain that the underlying code in InlineQuerier has an inbuilt option for creating and executing the DB in RAM. All it needs is to be exposed to the user in the Transformer Parameters.Currently InlineQuerier creates a temporary SQLite database file on disk, and executes SQL queries against this. This makes the Transformer dependent on both the available disk space and the speed of writing/reading from that disk.However the underlying SQLite engine used by the Transformer has In-memory database creation options as a standard part SQLite. There are three ways of creating different databases, but all use the same base functions and commands.I've tested all 3 methods with the similar SQLite FeatureWriter, and all 3 seem to work which seems to indicate that FME can already do these, it is just lacking a Parameter in InlineQuerier to expose the different performance optionsIf you call"sqlite.exe filepathname" or "rc = sqlite3_open(filepathname, &db)" depending on accessor being usedthen this creates the database on disk. This is what InlineQuerier does now.However if this is altered to:"sqlite.exe :memory:" or "rc = sqlite3_open(":memory:", &db)" depending on accessor being usedThis creates the database in RAM, if available.A third hybrid option is available that again uses the same command, and creates a temporary "pagefile" like file that if allocated RAM is consumed then it will mix data between RAM and on-disk:"sqlite.exe "" " or "rc = sqlite3_open("", &db)" depending on accessor being usedSQLite technical documentation here:https://www.sqlite.org/inmemorydb.html
I often encounter the same problem and need: I want to add text input in my workspace for various reasons. You could use standard transformers for this task, as AttributeManager or AttributeFilter, but I think a new type of transformer would be more appropriate. I give you the most common scenario:You want to filter out certain id:s (perhaps from a long list or a database) to try your methodology. The id:s could be found elsewhere and you just want to copy and paste them in your workspace and then hit Run. Let's say that you have 10 or 20 id:s you want to check.The new transformer, called TextInput or something else, would look something like a merge between a standard tranformer and an annotation. You could just click the annotation area and paste your text and it will automatically be put as the attribute fme_text_input.The only parameter for this transformer would be a checkbox if you want the textinput to be transformed in to a list and a choice which delimiter that should be used for creating this list.
ArchiCAD is a widely used BIM software mostly for architects and FM specialists. http://www.graphisoft.com/archicad/ A cleint expressed the wish to have an ArchiCAD Reader / Writer in FME, mostly to exchange data from and to AutoCAD.
We have LTO-tapes, Diskettes, CDs, DVDs. But would it not be great with a Spatial Archive format? Quite similar to FFS - however with more "unlimited availability" in the future? This was the "Archive" in SAIF in the early days also.Should this be a new format for archive? FFS-Archive ? That is meant to be just packaged away, but be able to read also in the year 2100This post got me thinking about this: https://knowledge.safe.com/questions/104218/ffs-files-versioning-and-compatability.html
When debugging a workspace, it's often necessary to use the "Redirect to FME Data Inspector" to prevent overwriting production output data.However, this fails miserably without warnings when working with dynamic schemas.Would it be possible to add support for dynamic schemas when using the "Redirect" feature ?
Inspect intermediate data as soon as the algorithm finishes the task (without necessarily waiting for the end of the entire process)
Occasionally its nice to turn off a segment of an integration without having to modify and redeploy the entire integration.A simple example scenario would be:-Currently we trigger the workspace jobs with .bat files on a schedule and use the parameter references within.-When 'x' happens in an integration do 'a', 'b', and 'c' [which are different transformations connected to 'x'].-I no longer want 'b' to happen when 'x' happens. -So I go to the connector param reference and set to off --ConnectorB "Off".-If I ever want 'b' to happen again I can set it back to --ConnectorB "On".I know, I know, there are probably other ways to do this. But isn't this easier? :)This could be an option for some transformations also.
Currently, the FME Server Engine names can be changed by manually editing the processMonitorConfigEngines.txt file. But please don't rush off and try this! You will lose the ability to manage FME Server Engines via the web interface – for example, changing the Engine count. This also isn't exactly a "feature" as it has not been rigorously tested! Buyer beware when making this configuration change. It would be amazing if we could use the FME Server web interface to change the names of FME Server Engines - perhaps on the Engines & Licensing page. What do you think? Are there any drawbacks I haven't considered? Is anyone doing this now? Wait, so how do I change FME Server Engine names? Add NODE_OVERWRITE=true to the top of the file, and find the START_ENGINE lines at the bottom to make some changes. Make sure to save and restart FME Server for the changes to take effect. (And remember, any changes to the FME Server Engine count must now be reflected in this file!) Example... Original: START_ENGINE_MyFMEServer_Engine1=!TEMPLATE_START_ENGINE!Renamed: START_ENGINE_MyFMEServer_LiDAREngine=!TEMPLATE_START_ENGINE!
I would like to be able to read a *.dgn file with the iModel reader.Currently, I have a workaround to append file name extensions to change from *.dgn to *.i.dgn so that I can read the file with the iModel reader.
It seems that XMLUpdater ignores any replacement values that is generated as xml-fragments by XMLFragmenter. Or rather, the updates fail.Please tweak the code of XMLUpdater to allow this.
Hi, I was wondering whether it had been considered to have the version Control pop-up box as a default when selecting Version Control in FME Server? We're finding that even with Version Control selected, it is pretty easy to miss the box needed to be filled in, when uploading a new version of a workspace to Server. If, when Version Control is on, if a user can be forced to fill in details of the version, if would help to keep the control consistent?Thanks,
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.