Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Hi,Are you also in charge of a multi-version/bit-affinity FME installation ? And is keeping track of which version with which to run a specific workspace getting to be a hazzle. It was for me.So I created a small utility tool named "FME Version Selector.exe", which I tied to the "fmw" extension in Windows Explorer. I'd like to share this with you.The tool gets run whenever I double click on a workspace file in Explorer. It then reads the first 20 lines from the workspace file, looking for a reference to "fme.exe" in the commented section, and uses it to determine the appropriate Workbench to run. It then spawns this particular Workbench with the workspace as argument.It can also be run stand-alone without arguments, in which case it shows a file opening dialog, in which you choose the workspace you want to open.I'm attaching the tool as a freeware ZIP with its C# 2015 source code. Find the EXE itself in the bin/debug sub folder. It's based just on .Net 2.0, so it should be fairly accessable.fme-version-selector.zip
Ability to download FME workspaces from server UI (much like how you can download resources) instead of through desktop.
Hi,The FeatureWriter is powerful, but the button "Apply to..." is missing. Is it possible to add it?Thanks!Rémi
You can start DataDownload with REST using a direct URL, what is really useful for sending or downloading zipfiles of results. The disadvantages that currently no JobID is returned when submitting it. Would be nice to support the return of the JobID of the workflow when using &opt_showresult=true both async and sync.
I wonder why there is no published parameter called "Attribute Value" in the dropdown list of available parameters when creating a Custom Tranformer.Should be standard, when you use any other transformer you expect the value to be passed when you submit an attribute.I know there are many workarounds, but still it should be there.
***Note from Migration:*** Original Title was: Maintain attribute order when using "Apply to..." to copy attributes to another Writer I love "Apply to..." in Writers but it would be great if the order of the attributes was maintained when applied to another Writer. For example, you have a Writer with attributes in this order:DACBIf you use "Apply to..." to copy the attributes to another Writer, they currently appear in the other Writer in alphabetical order i.e.:ABCDI would like the attributes to appear in the same order in the target Writer as the source Writer they were applied from.
The new feature "Dark Mode" in FME Server is so cool! Is it at all possible to apply this for the REST API page? http(s)://my-fmeserver.com/fmerest
The ShortestPathFinder creates a list of traversed edges for each path that is found. It would be useful if the list contained an attribute indicating the accumulated cost at the beginning/end of the traversed edge. This would allow an estimate of elapsed travel time at various stages of the path.
"Shared FME Folders" is a great way to share setups between 32/64 bit instances, between versions, and even between machines and colleagues on a network drive if warranted.It seems that there are much documentation on how to share database connections and coordinate systems using these "shared folders". And I even got the shared "Transformers" repository working.But there are still a number of elements of an FME installation that are not easily shared, e.g. such as custom formats.Wouldn't it be a good feature to expand Shared Folders to include all possible custom developments ?I.e., have FME look for its modules and dependencies in more locations than one.
Fme 2018 allows users to set the connection style. I personally use Curved, but not all workspaces are suitable for this style, especially if I open a workspace created by someone else with Squared or Straight. It gets a mess, so I want to save the connection style as a property of the workspace and the workspace.
It would be useful to be able to create a publication rss/georss feed in FME server and subscribe to it in your FME workspace to use the feed to perform another task like update your geodatabase.The rss/georss notification protocol is currently not available
Currently, the Logger only allows the severity value to be hard-coded or specified via a published parameter value. It would be helpful if the severity could be specified by an attribute value on input features.
It would be nice if the RasterConvolver could have an additional parameters. (In order of importance)Apply kernel:at all valuesonly at specific valuesdon't apply at specific valuesCompute Value:use all values in computationuse only specified valuesignore specified valuesReplace or Append BandCurrently the RasterConvolver replaces the existing band with the results of the convolution. On occasion it would be nice if the results could be appended to the original raster instead of having to send the original raster and the output of the convolver to a RasterBandCombiner.Potential use cases include:eliminating a specific class from a classified raster with a majority filter.filling in nodata values with the average of the surrounding values, but leaving the data pixels untouched.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.