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 often take screenshots of my workspace. There is nothing built-in, so we are left to use the snipping tool, or alt-print screen. Neither are that great. Autodesk Dynamo has a button where you can instantly take a picture of the entire workspace, and as long as you zoom into the nodes where they are legible, it creates a .png file where everything is readable, no matter how large your workspace is. Check it out.
I suggest you open the ability for Partners to pay (or pre-pay) by invoice, and put that as an option (without having to contact tech-support). We pay everything else by invoice, so this would make life so much easier.
I was curious if this would be possible to add a future enhancement that would allow for tabbed workspaces within FME Workbench? I think this would be really nice in order to have all of your open workspaces available to you within one instance of FME workbench.
The LineOnAreaOverlayer cuts lines with the polygons. Sometimes, you need to cut polygons with lines (e.g. split a polygon by its centre line). Currently, we use the PolygonCutter of @lars_de_vries (Thanks, Lars!). A dedicated AreaOnLineOverlayer, part of the xOnxOverlayers, would certainly deserve its place. Or maybe, make it optional that the current LineOnAreaOverlayer also cuts the polygons?
***Note from Migration:*** Original Title was: Add ability to pause an FME Engine job. Look at integrating the trick that desktop.
When using the JSONExtractor the JSON Query can only be hard coded or user parameters. It would be nice if the query could be constructed using attribute values.ex. json[@Value("json_index")]["test"]
To be able to use the mouse less and keyboard more I have tried to use TAB key to switch between parameters within settings of a transformer. I notice that the order they switch between is not logical in many transformers. Below is some examples. Would be a great summer-job to go through all transformers in TAB-way and fix the order in a more logical one!.
when adding attributes to the SpatiaLite Writer, FME converts them to lowercase. However, sometimes output needs to be in camelCase. This was logged at Safe Software with track number FMEENGINE-60521. Hopefully this idea will get the attention it needs to become a higher priority. SQLite and GeoPackage (which is in fact a SQLite implementation) do not have this behaviour in FME.See also: https://community.safe.com/s/question/0D54Q00008gn7IDSAY/camelcase-in-spatialite
I'm looking into different storage stategies for storing IoT-data in our Data lake (ADLS Gen2) and i would very much like to be able to read data from the Data lake and into FME for both analysis and transform-operations. We have more or less decided to store our cleaned IoT sensor data as AVRO since it is such an optimized storage format. It is also possible that we will store Parquet-files for specific use cases but for now the focus is on AVRO. However, i cannot seem to find an easy way to consume AVRO/Parquet in FME apart from struggling with AVRO modules in Python etc. It would be neat to have an AVRO and Parquet reader since they are such common big data formats.
Hi,As long as upgrading FME version is time consuming, there will be people with multiple installations on their computer (no mass upgrade for transformers etc..). Would it be possible to have some improvements to deal with this situation such as :list of recently edited workspaces with the build and not for all FME installations,a way to automatically open with the version used for the last editing if it is present,an automated naming option offered based on build number,a warning in workspacerunner if the build used to edit the launched workspace is different.etc... Thanks!
Currently it is quite difficult to expose attributes using a SQLExecutor to read in data from a SQL Server DB. Its currently very difficult if not impossible to have a dynamic workspace using a SQLExecutor to aquire the data. The reason I would like to use SQLExecutor rather then a reader or feature reader is the ability to allow the SQL server to do most of the grunt work rather then FME server. The sql query can order by distance to a location, search just to the nearest data point etc.A schema port similar to the port on the feature reader will allow for dynamic workspaces using largely SQL queries to grab data on the fly.
I'd like to see the start time and a running time graphic added to the banner of the Translation Log. This would state two items:1) A fixed statement of when the translation commenced (the time when Run was clicked)2) The running time of the process so far (obviously this would be constantly changing)It could have a third 'estimated completion time' item, but I appreciate confidently estimating completion time may be tricky.I've added a mock up of how it could look.
It Would be really nice with a right-click option to convert an existing writer to a FeatureWriter, keeping alle parameters and schema intact. If multiple Writers points to the same destination database, it would be nice to select multiple and convert to one FeatureWriter.
Similarly to RandomNumberGenerator, why not use RandomTextGenerator? In parameters of transformer, there should be field to define text values which should be randomly generated to specified attribute.
Currently, if you set an HTTPCaller method to GET, the body section of the transformer configuration window is disabled. I'd like to request this section be enabled.I have a REST API I must interact with that, for whatever reason, requires the parameters of the GET request to be submitted as json in the body. This makes FME and this REST endpoint incompatible.Thank you
Hi ,The idea I have got about the fme inspector. We are trying to change the symbology each time when the inspector finished. My suggestion is if possible copy the symbology settings from one window to another to paste it.If you can do it, we will save a lot of time.Thank you.
Assuming one is a responsible netizen then HTTPCaller should be able to handle multiple concurrent calls and send & catch interleaved jobs. I want to hit the REST endpoint of an ArcGIS geoprocessing service and I know how many service instances there are and I know I'm the only user so I want to have at it.
I want the HTTPCaller to support async get requests. This could really increase the perfomance of HTTPCaller. Now HTTPCaller wait for every request to come back before it fetches the next request, this is a big waste of resources, the program is basically in idle until it recieves its request. A naive look into async:You need to get multiple get requests, so instead of sending a request, getting answer for the request, send a new request, get the answer of the new request and so on. the program would quickly send all requests in a loop without waiting, and then start to recieve requests as the come back in a unordered sequence.
It would be nice to have a type "Time" as an option of user parameter. Currently, only Date/Time is available.
I've had an issue that's taken an hour or so to solve - my outputs were not consistent going into the next transformer, depending on the route they took!A colleague happened to accidentally click and slight drag one, revealing the exact same transformer (with a different SQL query embedded) underneath!Is there any way to stop being able to stack transformers on top of each other?Thanks,
Having had my fingers substantially burnt when upgrading Writers recently, I think it would be a really good idea to show a side by side comparison when doing this, as happens with Transformers.I upgraded just the Writer, not the Feature Types, and didn't notice that because some of the Writers were quite old, the options had changed. This meant they switched from the equivalent of "Truncate existing" to "Create if needed".If I had seen a side by side comparison, I would likely have spotted this and been able to correct it before running the Workspace and having duplicate data to sort out. Of course I should have done due diligence and checked the Writers first, but seeing the side by side might have made that job a little easier.
I'd like to see the ability to add additional destinations in one writer. This is where I would want the same output (with the same output file name in the same format) to go to to two (or more) destinations. At the moment I would need to add additional writers and set the additional destination in that. It would be great to achieve it on one writer.I can imagine a situation where I just expand the Writer in the Navigator and right-click Destinations. There could then be a new option to add additional destinations.
It would be useful to add support for the ability to timeout a desktop license that is being held by an idle user. In the event a colleague went on vacation and left up FME desktop on his desktop he would indefinitely hold a license until his return, preventing others from using that license. If the ability to timeout that checked out license to effectively return that floating license back to the license pool it would be available for use by others. Currently FlexLM has support for a timeout function but it is not supported by FME.
From SQL Executor, when Attributes are exposed and passed by FME they are automatically Alphabetized and the column/attribute order set is lostIn the case where SQL is used, Columns/Attributes should remain in the order they were set in the SQL statement
***Note from Migration:*** Original Title was: Use geojson-geom/wkt/prepared-geometry as geometry filter for for geospatial database connectors One could generate a custom geojson really easy now days. for example by visiting geojson.io you can draw your own polygon. Of course this is just an example as there are numerous similar other sites that can generate similar outputs. I would be nice if i could use this geojson as well instead of only having the option of a Search Envelope.
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.
