Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
A visual compare and diff between two workspaces. Which transformers, readers and writers are added changed or deleted. Compare two workspaces and tell the differences in color.Merged Ideas:Visually compare two workspaces (Duplicate of this idea) by stalknecht on August 22, 2017A visual compare and diff between two workspaces. Which transformers, readers and writers are added changed or deleted. Compare two workspaces and tell the differences in color.Identify Differences Between Two Versions of Same Workspace by mark_f on November 6, 2015Currently difficult to compare two versions of the same Workspace. You can use a standard diff tool on the FMW files but there are often too many minor changes in the file to identify the real differences.FME workspace compare tool by ynaphade on January 25, 2016After seeing the demo of workbench reader, I was thinking we may need some tool to compare 2 versions of FME workbench to see what changes developer has done. we can do text compare but if developer just moved the transformer there is more noise and facts.
Fonts like Fira Code (open source) make source code more readable by representing common character combinations with unified symbols. For example, == looks like a double-wide equals, -> looks like an arrow, >= looks like a standard mathematical greater-than-or-equal symbol. I already have support for fonts like this in my JetBrains editors, but it would be nice to also have it in the PythonCreator, PythonCaller, RCaller, and TclCaller transformers, as well as the scripted user parameter editor.
When transfering FullName to the Username in a Windows Active directory, FME server uses the "User logon name (pre-Windows 2000)" which has a 20 characters limitation. This has the effect of truncating the FullName which can cause problems when making API calls to the Username. It would be helpful to be able to configure FME server so that it uses "User Logon Name" instead of "User Logon Name pre-Windows 2000" to help with that character limitation problem.
***Note from Migration:*** Original Title was: Autocad DWD/DXF Parameters allow Read ALL Paper Spaces beside of manually choosen ones When I read several DWG's, I don't know the names of all the Paper Spaces that may be there.I want to filter the viewports, or reading the Model Space Entities through viewports with Name starting with....When I read in all DWG's only with all Paper Spaces and without Model Space, then I can read in the right Paper Spaces with a second feature Reader.
Add the "EWKT" Geometry Encoding definition to GeometryReplacer and GeometryExtractor.EWKT is a simple extension to WKT that allows to include the coordinate system with the geometry, for instance: "SRID=4326;POINT(-44.3 60.1)" instead of "POINT(-44.3 60.1)"https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometryEWKT is supported by Postgis and can be found in many open datasets.
The Group By option on transformers with several input ports is usually used with attributes which occur on both/all input ports.Can there be an option in the attribute selection window to only show attribute names that both input ports have in common?For instance, on the clipper, both the Clipper and the Clippee should contain the attribute I want to group on. So it would be great if I could display attributes that are existing on both input ports.
Please consider adding bulk mode support to the PythonCaller.
Okay, I know it's irrelevant to most people here,But this is a small idea, which can enhance the user experience for a many people!In Hebrew, as in other languages, we read and write from right to left.When I publish a server app for our clients, the title of the parameter is to the left of the box that needs to be filled.It makes perfect sense if the parameter was also written in English, but for our customers, we prefer the local language,So it creates confusion in the eyes.If there was such an option to set where we want the title of our parameters, it would be great!Thank you!
When running the SurfaceDraper transformer on 3D polygons as the surface, a surface polygon may throw an "invalid third dimension" error/warning. The message, however, does not specify which feature caused the error. It should. For me, anyway, I work with very large datasets, and identifying the offending feature is nigh unto impossible. In fact, I have this problem at this moment, and no amount of geometry checking in either ArcGIS or FME has been able to identify the offending feature. Simply identifying the offending feature in the error message in the logfile would make all the difference.
As a Python developer, I would like to be able to import an FME Python API package/module from a Python module on a machine with FME Desktop/Server installed and call any transformer that is present in the gallery.This would be similar to Esri ArcGIS Desktop arcpy package exposing all the geoprocessing tools from ArcToolbox.This would let streamline integration of FME and Python ecosystem!
Hi.I just experienced FME crashing in a fairly limited translation. The problem was the feature caching.I used a HttpCaller to fetch a GeoTIFF into an attribute, tested it twice (for HTTP result code, and for it being an exception) before writing it to a file. I.e. the output from the HttpCaller is cached by 4 different transformers.The problem is, that the GeoTIFF in question was 1.5 Gb in size, and I had 6 feature instances with this attribute. I.e. that FME needed to cache approximately 36 Gb in memory. This made it crash off course. Running without feature caching solved the problem.Howeever, the 4 times cached value for each feature is really unneccessary, since it is the exact same attribute value for each feature.My suggestion is:- to only cache such very large feature attributes once, and just link to it in each transformer cache ?- alternatively, and maybe simpler, enable turning off feature caching on individual transformers ?Cheers
Such feature will help us to audit and code-review FME workspaces.
I'd like to be able to use 64-bit FME more widely, but we're dependent on Personal Geodatabases for some of our projects. In particular, I'd like to be able to upgrade FME Server to 64-bit, but that isn't feasible right now...On top of which, if we do ever fully transition to 64-bit, presumably we'll be left with a whole pile of unusable MDB files. Any chance of getting them added to the 64-bit version?
***Note from Migration:*** Original Title was: Allow to receive JSON format parameter through FMEServer.runDataDownload function I noticed that FME removes every double quotation from a parameter value formatted in JSON if it was passed via the JavaScript API FMEServer.runDataDownload function.This is a simplified workspace: fme-server-json-parameter.fmw (FME 2017.1.2.1)If you run it from the FME Server Web UI, the JSON parameter will be preserved correctly. Good.However, if you run the workspace from an external web application with the API function, FME will removes every double quotation from the JSON parameter, and therefore it cannot be parsed as a valid JSON document. e.g.<!DOCTYPE html><html><head><title>test</title></head><body onload="onBodyLoad();"><div id="result"></div><script type="text/javascript" src="http://api.fmeserver.com/js/v1.1/FMEServer.js"></script><script type="text/javascript">function onBodyLoad() { var server = 'https://xxxxxxxxxxxxxxxx.fmecloud.com'; var token = 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'; FMEServer.init({server:server, token:token}); var jsonParams = { 'param1' : "A", 'param2' : "B", 'param3' : "C", }; var repository = 'Tests'; var workspace = 'fme-server-json-parameter.fmw'; var parameters = 'JOB_PARAMS=' + JSON.stringify(jsonParams); FMEServer.runDataDownload(repository, workspace, parameters, function (obj) { var res = obj.serviceResponse; if (res.statusInfo.status == 'success') { document.getElementById('result').innerHTML = '<p><a href="' + res.url + '">download</a></p>'; } else { alert('failure.'); } });}</script></body></html>Log:Is there a way to preserve a JSON parameter correctly in use of the API function?
The current version of FMEServer.js supports a subset of the V2 REST API and is useful for integrating FME Server functionality in javascript-based applications.It would be great to have an updated version that supports the new API capabilities introduced in the V3.In particular, it would be helpful if the following two methods were added:Query the status of an asynchronous job: /transformations/jobs/id/<jobid>Retrieve the job log: /transformations/jobs/id/<jobid>/log
It would be good if for AnchoredSnapper, a Snapping Tolerance could be an attribute? Currently it only accepts parameters. I understand why not for a Snapper - because everything might move around, but for an AnchoredSnapper, that's not a problem, the base doesn't move.The attribute could come from the "Candidate" (and only the candidate). Then each candidate can snap to a different tolerance to the base.
http://www.simplecloud.info/The System for Cross-domain Identity Management (SCIM) specification is designed to make managing user identities in cloud-based applications and services easier. The specification suite seeks to build upon experience with existing schemas and deployments, placing specific emphasis on simplicity of development and integration, while applying existing authentication, authorization, and privacy models. Its intent is to reduce the cost and complexity of user management operations by providing a common user schema and extension model, as well as binding documents to provide patterns for exchanging this schema using standard protocols. In essence: make it fast, cheap, and easy to move users in to, out of, and around the cloud.
I would like to be able to run FME Server on a RPi4. To be able to do this, I would like to have FME Server in a Docker container for ARM.This idea is from this post : https://knowledge.safe.com/questions/45838/is-it-possible-to-run-fme-server-on-raspberry-pi-3.html?childToView=97215#comment-97215
I have a workspace with a published parameter. This parameter can take several values from a list.When this workspace is used for a server app, it is possible to either show completely the parameter to the user, with all its possible values, or to hide it completely.I would like to be able to propose only some values from the list to the user of the app.
When using the "Manage User Parameters..." interface, private parameters cannot be visually identified as such. Some color, symbol or other identification that sets them apart from published parameters would be great.Right now, one has to either select each parameter individually to look at its "Published" checkbox or quit the manager to (squint hard and) look at the padlock symbols in the now combined User Parameters list of the Navigator.
GLTF 2.0 supports double sided material, however, even if a surfaces has a double-sided appearance in FME the output does data not honour this.For reference, here is the gltf specification the double-sided materials can be defined. https://www.khronos.org/registry/glTF/specs/2.0/glTF-2.0.html#double-sidedThis is of particular importance because it can be really difficult to correct incorrectly oriented surfaces - being able to create double sided materials can help to overcome this challenge.Here is an example workspace which shows the issue
When you use a User parameter in a Reader/Writer first time it appears the name $(PARAMETER_NAME), but after you check the OK, if you reopen this Reader/Writer the parameter changes for its value. It would be great if when you come back to this Reader/Writer it still shows the name of the parameter that you are using.
Hi Folks! We're tracking this one as (FMEENGINE-59393) but upvoting this idea will give us a sense of how much this functionality is wanted as well as a way for you to be notified when it's been addressed. Let us know what your thoughts are on ElasticSearch v7 and what your use case is!
Create an option for all raster transformer, to specify a template output grid. Basically ESRI's snap raster.
Add support for FME Data Express to be able to run FME Server Apps with authentication enabled.
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.
