Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
It would be beneficial, to have a timer in the status bar showing how long a translation have been running, stopping when it's done. Much like when executing queries in Sql Server Management Studio.Often and again you're running the same query, with minor changes, and being able to know how long the translation has run enables you to more effectively do other stuff in the meantime.
FME Desktop floating license: Extend port range on auto search. Now FME searches for available licenses on port:- 27000- 27001- 27002- 27003- 27004- 27005- 27006- 27007- 27008- 27009However if you have a big organization with many flexlmlisenses on same machine the port might be 27050. Please extend the auto-search to for instance 27100.You can also write the correct port and it will work. However when the port changes all the users need to also change the port number.
Some projects I work on do not support SMTP-mail. I would like to see some support to send emails through an Exchange mail account. I have to give the email address, mailserver, domainusername and a password.
This idea comes actually from a customer. As far as I understand FST is a faster format for storing data frames in R. You can find some information here: https://github.com/fstpackage/fst
I would like it to be possible to read the generated marks of a pdf, to be able to export them.This could generate pdf for changes, and then reload in the spatial database where the pdf was generated.
When visiting https://fmeserver/fmeserver/#/job/5/summary you can click refresh to update the log. However I want a button called "LIVE" that continuously receives new loglines. Or a button called "LAST 50 lines" that retrieves the latest 50 lines written. Right now I have to hit refresh, then scroll down and select the last page (if there is a new page).
More and more 3dmodles data are produced ,and those data is slowing when render it on our applications,It would be ideal if some transformer could create multiple LODs for 3dmodles so that any rendering software can render them appropriately according to zoom level.
I have a workspace which fires out a lot of logging from various sql Executors on a 100 000 feature basis (up to around 30 million features) that each line has been read/written.Whilst the information is a helpful factor and I don't want to amend batch sizes for the processing I would like to be able to collapse down sections of the log which are effectively the same message (Processed 5338387 of 29165145 features , Processed 5438387 of 29165145 features etc.).These messages make the log file verbose (85 pages) and when needing to debug following an error there is a lot of trawling through the messages to find an issue.If the log could be collapsed down into groups for messages of the same type it would make the debugging process a lot simpler.
When I set my start feature at 4,000,001 with max features to read to 1,000,000 there is SOOOO much time wasted reading all the features. Why doesn't it only start at 4,000,001 and read those 1,000,000 records?2019-06-11 15:15:09| 9.2| 7.2|INFORM|GEODATABASE_SDE reader: Read 20000 features...2019-06-11 15:21:29| 408.9| 7.5|INFORM|GEODATABASE_SDE reader: Read 1100000 features...
Logging in 2018.x.y.z presents you with 60 or 70 lines before getting to grips with your actual workspace. A lot of this could be presented in an 'on load' log and hidden from casual view.Perhaps consider logging levels to control the verbosity of the report - I would, typically, just like to see 'Started Transformer x', results of print statements, 'finished transformer x' and the final summary. All of the version information and memory consumption reporting obfuscates the log.
After upgrading to FME 2019, the Python interpreter is not using the entire package. After setting the interpreter to both the ArcGIS Pro 2.1/2.2/2.3 Pyhon (3.6) and also a custom interpreter pointing at the ArcGIS Pro default env. FME is not returning the correct dateutil package. This was brought up by trying to import Pandas for use with the Python Caller, an error message of "dateutil minimum release of 2.5.0 required". This is not only on Windows but also on MacOS, the same solution corrected it on both and Pandas does import correctly in Eclipse, ArcGIS Pro, Conda, etc. without error. Running a Python caller with the following import fme import fmeobjects import os import dateutil def processFeature(feature): feature.setAttribute("PyPath",str(os.path)) feature.setAttribute("DateVersion",str(dateutil.__version__)) FME returns Path (Correct) = Date Util Version (Incorrect) = 2.4.0 ArcGIS Pro returns import dateutil print(dateutil.__version__) 2.7.3 import os print(os.path) module 'ntpath' from 'C:\\Program Files\\ArcGIS\\Pro\\bin\\Python\\envs\\arcgispro-py3\\Lib\\ntpath.py' After searching some, I realized I had to replace the dateutil and python_dateutil-2.4.0.dist-info under "Install PathFME2019python" FME returns Path (Correct) = module 'ntpath' from 'C:\\Program Files\\ArcGIS\\Pro\\bin\\Python\\envs\\arcgispro-py3\\lib\\ntpath.py' Date Util Version (correct) = 2.7.3
I tried executing SQL statement containing some geography functions onto a Google BigQuery table with SQLExecutor, but it failed with error saying "ST_* is not supported". It seems that FME cannot execute a query containing geography functions.It would be nice if FME would fully support the geography functions for Google BigQuery.cf. https://cloud.google.com/bigquery/docs/reference/standard-sql/geography_functions
In the SurfaceDraper I miss an output port for features that have not been draped. Now I will have to use additional transformers to determine which features have not been draped.
The 2019 version of the ChangeDetector has some great functionality updates. Since the fréchet distance is already calculated to determine if a feature is geometric match, it would be nice if we had the option to add that value as an attribute on the updated feature.ex.ChangeList{0}.action modifiedChangeList{0}.attributeName geometryObjectChangeList{0}.originalValueChangeList{0}.revisedValueChangeList{0}.frechetDistance 2.3
Currently you can disable FME job logging if you turn off all your log options in Desktop prior to uploading your workspace to server.Create a setting in the upload process as a check box to turn logging on or off for that workspace.IS already case C117368 and PR enhancement request #30438@daleatsafe @aaronatsafe
In the FeatureMerger it would be useful to add a range/between comparison mode particularly for linear referencing event data. When the event data stored in xlsx, csv, or any table that is not in the same database as the linear features; there needs be an easy way to determine which event points fall in the range of the linear feature.
When setting up the security of a role, it would be useful if one could temporarily "switch" to that role's access, to verify everything , without having to log out as the admin and back in as the user with that role.
This idea originated from a Q&A post: https://knowledge.safe.com/questions/30088/are-there-efforts-underway-to-support-fields-of-ty.htmlLet's move it here so we can get some votes. This developement item is on our to-do list. Knowing how many people are interested in this enhancement helps us with prioritizing. (The previous target of 2017 was moved, in favor of items that had higher priority.)It would also help to know if you are interested in reading Lookup fields or writing them as well. Any comments on this would be much appreciated.
***Note from Migration:*** Original Title was: File geodatabase writer - set coded domain field width but use existing domain definition At present when creating a feature class field in a file geodatabase for a field that uses a coded domain, the 'Create Domain' box has to be ticked to enable the user to set the field width within the writer feature type. This currently necessitates providing a domain definition as well as the field width, however if the domain already exists in the target geodatabase we don't want to have to recreate the definition and FME will use the existing definition for that domain anyway when it sees the domain already exists. It would be useful to have the ability to use an existing domain and also set the field width, but not have to provide a domain definition.An example use case is where multiple new feature classes need to be created, these will all share a field with the same domain. The domain is created once in the file geodatabase outside of FME (ArcCatalog), then the feature types for all new feature classes in FME use that existing domain name without then having to define it in each feature type, and all that needs to be specified is the field width.
The Clipper's aggregate parameter was removed in FME 2019 (PR#81764). Typically I don't want multi-part features in my data and since the parameter is now gone, I use the Deaggregator after every Clipper.@jovitaatsafe, @erik_jan, @msims
Safe is concentrating a lot to enhance FME user experience, but sometimes I think a poll would be good to get more feedback from the community about the enhancements before they get into the FME releases. By far most of the updates are great, but sometimes a bit cumbersome update gets to a release, before the community has had a chance to tell its opinion. E.g. the composite test UI change in Tester 2019 is not so popular at least among Finnish FME users.Idea: Safe to create polls for bigger UI changes in Workbench or transformers.
We are trying to connect to a PI database from OSIsoft and use tables for join to GIS geometry. I know PI can go into a SQL server but we dont have that set up so have to go directly into their database. I dont see any readers for this format. Has any user been able to connect to the PI backend datasets with FME? Any help would be great, thanks.
PDF reader does not extract any information from digital signature. This feature would be super nice for different kinds of archiving processes.
Add a reader/writer for the Building Collaboration Format as defined by the buildingSMART alliance.
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.
