Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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.
The Aggregator transformer allows string attributes to be concatenated, which is great for generating separated lists. But if I have multiple identical input values, the list is less useful.An option to only add distinct values would be nice.
The Dynamic Workspace action in Auomations on FME Server allows you to run multiple workspace with the same parameters with the input from a FME Server Auomation Writer. Instead of using the FME Server Auomation Writer as input to the Dynamic Workspace, this should allow one to select multiple workspace from multiple repositories with same parameters, in an Auomation directly in a Dynamic Workspace Action. This makes it easier configure an Auomation Writer with the use of only one Action, instead of multiple actions for multiple workspaces.
When a ParameterFetcher (or AttributeCreator/Manager) is used to obtain the values of a "Choice (Multiple)" published parameter the result is a space-delimited string. However, when any of the published parameter choices contain spaces the values are wrapped in double quotes. If there are no spaces in the choice value then it is not wrapped in quotes. This makes extracting the actual chosen values problematic in an FME workspace.As an example, if my published parameter choice values are:'a a''b''c c'Then the ParameterFetcher would return an attribute with a string containing:"a a" b "c c"It is not a simple task to retrieve the individual choice values from this string. The AttributeSplitter will not work because the delimiter <space> can appear in the quoted strings. A simple regex is not easy to construct because not all values are quoted. The simplest solution seems to be a TCLCaller or PythonCaller but this is not easy for someone with limited programming experience.My idea suggestion is to make accessing these values easier. To do this I would propose two alternative solutions:wrap all values in quotes, even if they do not contain spaces, to make constructing a regex simpler;enhance the ParameterFetcher to return an FME list of the choice values.
Hi,It would be great if run-time metrics of a Workbench are also part of a full FME Server Backup. This is especially important when these metrics (state) are used in the Engine Rulesets. Now when a backup is restored, the Engine Ruleset do not work the same as the runtime metrics are back to zero and thus cannot be used to determine the Engine.https://user-images.githubusercontent.com/8686001/153906648-e05aa4b5-0ae4-4520-8b33-547f3533d2f7.png
I don't know, this is an Idea or an error.Python Caller's error line number in the fme log, always +1for ex :if the error is in line number 10 and fme log says error in line 11.Please fix this issue in the next release. this has been there in many releases.
Three suggestions:Add non-geometry layers (wkb_none) support in the SpatiaLite reader so that both non-geometry and geometry features can be loaded using a single reader.Improve the mapping of SpatiaLite and FME data types in the SpatiaLite writer. VARCHAR(n) is not a SQLite native data type.Allow specifying a custom primary key in the SpatiaLite writer. Now FME adds OGC_FID.Support for SpatiaLite as a GeoPackage would be great.
1. Directory watch does not trigger topic when new folder is created in the directory unless you tell it to watch sub directories. I want to know when a new folder or sub directory is created within the directory, but do not want to monitor changes withing that sub directory.2. There is a bug where if you create a new folder or file within the directory and rename it, it will notify that the old document name has been deleted, but does not send a create or modify notification for the new document name.
FME Server records the job information of the jobs that have been run, and usually a system cleanup task will remove these after some time. That's great for what has recently occurred. But in the scenario that you want to find if a workspace has been used over a long period of time, then you would have been required to store this information and long periods of time. So right now, I can't tell and will need to records these details for the foreseeable future.So I would like a new table in the FME database with an api call in front of it, that records the last date a workspace was run and maybe a couple of other fields such what ran it (e.g. an App, webhook etc) and what user. Over time this could be expanded, so it also said also recorded the last time a Server App was run, or when a token was run (especially as users often create tokens for a range of things and it is very hard for admin to confirm they are used)
Would be great if the internal "guts" of password protected custom transformers wouldn't be logged at all - even in debug.You should only see # features per input port and # features per output port (much like with regular transformers).
When working with an Oracle database you usually get the option to remove the table qualifier within the connection parameters (Reader, Writer). However, this option is missing within the Joiner transformer resulting in a minor inconsistency within your workspace. Could you include this option in the Joiner, too?
I routinely perform QA checks on ECW and GeoTIff files. When I use transformers like CoordinateSystemExtractor, it seems that FME gets confused by the presence of the sidecar files (.ers and .tab). I can check these via another work bench, text file reader, or a string transformer. But right now, to check only the ECW or GeoTiff files, I first have to move or delete thousands of side car files; these are often found in multiple directories, so this can take a long time. I think it would be a good idea for FME to include the option to ignore the sidecar files, either in the ECW/GeoTiff reader, or within the transformer settings.
Since FME 2018 there are Quick Filter options in the translation log (https://community.safe.com/s/bridea/a0r4Q00000HbrcEQAR/translation-log-quick-filter). This has been a great improvement, but I'm still missing a more general filter where you can type in any keyword like for example a transformer name, an attribute that is causing trouble, etc. and see only those messages in the log. Basically the same as in a job log in the FME Server
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.
