Open ideas have been reviewed by our Product Management and are open for commenting and voting.
A CEMAR connector
Introduction of a new a reader or improment to the projectwise connector to access the incoming and outgoing communication transmitted via Deliverables Management
When inspecting features that have filtered user attributes, only show the attributes selected in the reader/in the workflow in the Feature Information Window. The Table View does this currently - could it be implemented for the Feature Information view as well?
Hello all,Since the revamped date/time implementations in FME, my use of small python-snippets has been reduced dramatically. No more 'import datetime' to do some simple operation.Now the bulk of my python-use involves the os.path library, like splitting, joining or testing for existence.There are a couple of transformers who have path-functionality, but I often need it in text-editor like situations. e.g. building the output-file-name of a writer from parts of the input parameters. Splitting and concatenating using 'text-methods' is not platform-agnostic due to the path-separator. So I put in some python-scripted-parameter.So please, give the os.path methods the same treatment as the datetime library got some years ago.Martin
It would be great to have FME Cloud hosted in France (Paris Region)
See https://knowledge.safe.com/questions/74063/not-able-to-install-fme-desktop-on-fedora-28.html
If I am running multiple Webhook Automations on FME Cloud / FME Server, each for a different client, those clients will usually want those webhooks to be restricted to source IP addresses that they would provide to us. This gives both the client, and my organization, peace of mind that their webhooks can only be triggered by known machines.
When using the new WMTS feature readers, if the service returns a 4xx or 5xx for a tile, it leaves it as blank and continues on with a warning message in the logs. When a tile returns a 200, but with unreadable content, it makes the full feature reject.There should be an option for how to handle these errors. In my case the way a 200/invalid data tile is handled is what I would want for a 4xx or 5xx error.I've had to create a little Lambda proxy inbetween FME server and the EMTS to make this happen.
We have been previously exported .asc format for floating TIFFs. However we would like to see FLT as export format which creates smaller files than .asc.https://www.coolutils.com/Formats/FLT
So we have the good old writer with that nice feedback if all attributes are connected. But yes it's a dead end an I'm not using it that much anymore.Then we have for some year the FeatureWriter with the ability to keep flowing. It's great and I can not do without it anymore.Shoulden't we combine the strengths of both solutions and make an enhanced FeatureWriter?
Since the Inspector supports changing the drawing style of geometry it would be nice to have the FeatureColorSetter have opacity and width parameters.
We can list any files from folders in Google Drive and add useful attributes like _file_last_modified or _sharable_link. But we don't read and list the actual Google items like sheets, docs, presentations etc.
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.
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.
