Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Nowadays, FME log does not show all the information when SQLExecutor transformer is used in order to execute Oracle procedures.For example, If several procedures calls are used in the SQLExecutor, only the first three procedures calls are showed in the log. The others no. So you don´t know how the process is be going.
I just want to configure a tiny log file, stating the same counts of a few connections(pipes) from my workspace. Lets call tose CheckPoints.Is there a better way than adding a counter/sorter/sampler or StatisticsCalculator at each CheckPoint?StatisticsCalculator is a bit over kill, I think.If not, I wound like a new mini-transformer that just preserve the count from a pipe, so I can name each CheckPoint and collect them in a file. There got to be a way to reuse the count of each pipe, in an easy way, right?
I like using the Databse Joiner transformer when I can but my use is limited because it doesn't have a where clause option for the database data being joined.
If an Oracle Spatial table exists with appropriate metadata, when importing it as a Feature Type, could it populate the Format Parameters e.g. SRID, 2D/3D, Spatial Column, Tolerance, Extents etc. from the Metadata table?Think it would need to be an option to apply these or a prompt "Do you want to apply settings from Metadata?". Maybe it is too difficult as you may use the schema but for a different format, but if the same format why not?(Also may apply to other formats)
Having authored a Workspace reading from a database (Oracle in this case) that runs successfully, it continues to run without issue even when the table is subsequently dropped. No warning, no failure...nothing!A big surprise.
Hi, If you want to configure HTTPS for your's FME Server with a PFX file.Go to Configuration page and at the Tomcat configuration read and open the server.xml.So you must add this parameter --> keystoreType="PKCS12" and modify this another parameters keystoreFile="<FMEServerDir>Utilities omcatyourfile.pfx" keystorePass="<your_password>"Like This :<Connector protocol="org.apache.coyote.http11.Http11NioProtocol"port="443" minSpareThreads="5" enableLookups="true" disableUploadTimeout="true" acceptCount="100" maxThreads="200" scheme="https" secure="true" SSLEnabled="true" keystoreFile="<FMEServerDir>Utilities omcatmyfile.pfx" keystorePass="PKCS12" keystorePass="<your_password>" clientAuth="false" sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2" sslImplementationName="org.apache.tomcat.util.net.jsse.JSSEImplementation" ciphers="TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA,SSL_RSA_WITH_3DES_EDE_CBC_SHA"URIEncoding="UTF8" />That's enough, continue the tutorial admin and restart FME SERVER and it's doneBye Eric
Latitude and Longitude when given as degrees minutes and seconds frequently include a compass point e.g.Latitude 8° 34' 51.7'' SLongitude 40° 9' 57.7 WIt's necessary to use this information to correctly return the decimal degree value with a negative value. It's fairly trivial to do this afterwards but it would be nice to see it included in the transformer.
For ArcGIS to see the coordinate system
Similar to the 'Ignore Failed Readers' parameters, allow 'Ignore Failed Writers' but allow it to be selectively enabled. In instances where a non-crucial writer (eg. for tracking purposes) fails to write for reasons unrelated to features (eg. if the file written to is opened by another user), this would allow the workspace to continue running.
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
Please add 3D solid support for the Bentley i-model reader. I have had limited success reading 3D solids from i-model i.dng files and having the ability to read all 3D solids from an i-model file into FME would be fantastic and improve interoperability between the Bentley producst we use and our other software platforms.
Why not add the "Truncate and Insert" mode to the CARTO Writer?
Ability to download FME workspaces from server UI (much like how you can download resources) instead of through desktop.
The ability to filter completed jobs in 2018 is one of my favourite improvements, not just this year but across all releases. One thing I'd like to see improved is the ability to filter jobs by exclusion (ie show me all jobs coming from all repositories except those in x,y,x).
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.
One very frequent issue that I've come across is the need to record the timestamp during a model. Currently, the main way to do this without having different timestamps across a dataset is to capture the timestamp at the beginning of the model and then to store it in a parameter.It would be great if instead, I could use a built in parameter, such as FME_RUN_DATETIME.This parameter would capture the datetime when a model is run for use in later calculations, attribution, custom logs, and fanouts as needed without having to add multiple transformers to each model.
***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.
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.
I'm trying to use the XMLTemplater to write a web page with some javascript in it. This seems to trigger all kinds of validation issues. So I would like to have an option in the XMLTemplater to simply not validate anything and just do what the user tells it to do. This would make it more useful for writing non-XML stuff such as HTML or even plain text reports.
Hello everybody, im trying to import some XML-based ALKIS-Data into FME. Not even possible to create any Reader due to this Error: XML Parser error: 'Error at file:'' line-0 column:0 message:unable to resolve host/address 'intra-prodaaaweb.vkv.niedersachsen.de'' An error occurred while attempting to parse the XML Schema document 'http://intra-prodaaaweb.vkv.niedersachsen.de/aaa-suite/schema/NAS/6.0/schema/Fachschema.xsd' The XML Module halted on error, see the logfile for details Failed to obtain any schemas from reader 'CITYGML' from 1 datasets. This may be due to invalid datasets or format accessibility issues due to licensing, dependencies, or module loading. See logfile for more information FME Session Duration: 0.4 seconds. (CPU: 0.2s user, 0.0s System) Thanks a lot :) Sabine
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.
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.
