Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
As far as I can see in FME 2018.1 there is no option to 'Auto-connect Attributes' when relating to a Feature Writer Transformer.This would be really helpful I think.
Esri has support for writing the layerType 'Building' in i3s. However currently it only is possible to write those from Revit. Options such as IFC are not yet possible. It would be great if Safe can support the 'Building Scene Layer' to be able to built those from IFC files.
Please please please :-) do some work to improve processing speed in FME of JSON.Using the JSON fragmentor I'm processing a JSON document with 20k simple records. FME processes each record in ~2-3 seconds. Unusably slow.Using Python I can process to document is ~5 seconds.A sample document is available here and I'm interested in the attributes of the feature array.
When using the File Geodatabase Open API Reader, any domains are automatically resolved to their values. Please can an option be added to the Reader so we have a choice about whether this happens, as we do with the ArcGIS version of the Reader.See...https://knowledge.safe.com/questions/73616/resolve-domains-in-file-open-api-geodatabase.htmlhttps://knowledge.safe.com/questions/72775/is-the-fgdb-open-api-reader-able-to-read-fgdb-doma.htmlIt appears that a few people would find this useful.
I'd like to see a transformer that replicates the Fanout function for writers. I.e. I want to be able to filter a feature by an attribute(s)
Hi,I know that FME has WebMapTiler as one of transformer utilities and it's good for creating image tiles in 2d web map applications.However, as 3d web gis is evolving and as there is more possibilities to build nice 3d web gis applications using libraries like CesiumJS and similair, i wonder if there is any plan in near future to enable tiling of 3d datasets using FME.For example, that you have 3d mesh and you want to create quantized-mesh tiles using some FME Transformer ? I know it's probably not so easy to implement at the moment but I would like to know if it's something that is on TODO list or not?Thank you and kind regardsIvan
Currently the following header information is not updated when writing to a LAS file:system identifiergenerating softwarefile creation day/yearIt would be more appropriate to have these fields populated with the details of the creation of the new LAS file by the FME writer. At present it is retaining data from original LAS read into the workspace.
improve sorter => consider accented words ! Ex : Zoo, École, Auto FME sorter ASC : Auto, Zoo, École.
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.
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.
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
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).
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.
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.
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.
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.
