Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Migration Note: Idea originally posted on 2015-10-29
Hi, with uncertain input (Excel spreadsheets) full of junk of variable types. I suggest allowing the Attribute Trimmer , when trim to nothing is set , add the option to setting the result to null. This would allow easy selection of attributes, trimming to zero length and then setting t o null thus avoiding wasting time finding (or not) a regex expression from the internet that will do the above in the null attribute mapper.It could also be implemented in the null attribute mapper. Migration Note: Idea originally posted on 2024-02-04
Migration Note: Idea originally posted on 2015-11-05
Instead of configuring tomcat files, it would be awesome to have a drag and drop way to load certificates and turn on or off HTTPS/SSL in the FME Server web ui
Markdown/HTML support is great on Workspace - Description Overviews and displays nicely in the FME Server Web-interface GUI. However when this workspace gets published as a web app it can not display the same data as the "Description".1. Should be possible to "Use same as description in selected workspace"2. Support for Markdown/HTML.
See https://knowledge.safe.com/questions/74015/custom-coordinate-system-monte-mario-italy-1.html for detail about this coordinate system
All readers today is for only one extension in a time. Sometime you have to upload multiple files in a flow. It would be nice to be able to add a zip with multiple files. And then the path for each files to use in a reader at your choice. This pythonscript read all files in a zip and returns the path. You need a attribute exposer to get the attributes. import zipfileimport osimport fmeobjectsclass FeatureProcessor(object): def __init__(self): pass def input(self, feature): zip_path = r'yourzipfile.zip' extract_to = os.path.dirname(zip_path) with zipfile.ZipFile(zip_path, 'r') as zip_ref: zip_ref.extractall(extract_to) for file in zip_ref.namelist(): f = fmeobjects.FMEFeature() f.setAttribute('file_name', file) f.setAttribute('file_path', os.path.join(extract_to, file)) self.pyoutput(f) def close(self): pass
Supporting CityJSON 2.0 would be very nice. It is currently supporting a version from 2019. Is it in the works to support 2.0 (aligning with citygml 3.0)? I can't find any topics on this and thus want to ask if/when we can expect it.
With the rebranding you get rid of free home licenses. No warning, nothing.Like nany others, for years i build personal projects and contributed with some ideas and bug fixes. Now i simply cannot access to my projects unless i pay almost 10k from my own pocket. So, my idea is simple: give all free home license users an oportunity to buy a licence at the price you guys said not intended to raise. Thank you
There is a custom transformer named RandomPointGenerator which can generate random points in polygons. However, it can only use the same single integer value for all polygons. If the possibility would exist to create N number of random points, where N is an attribute value different for each polygon, this transformer would be much improved.
I noticed that Shapefile Writer in FME 2022 adds prefix "Q_" to destination attribute names beginning with a Japanese character.See the attached screenshot.I think it's a side effect caused by the design to automatically avoid attribute names starting with a digit or a symbol, but it's just annoying for Japanese and other non-English users.I found a workaround, that is removing this line from {FME_HOME}/metafile/shapefile.fmf".=========ATTRIBUTE_CASE FIRST_ALPHA=========However, it's hard to find this workaround for most users.I think it would be ideal if you could add an FME option in FME Workbench interface in order to users can swith the function on/off.
From FME 2019.0 there is a parameter in the Esri SDE Geodatabase Writer for preserving Global IDs. It would be very handy to have the same feature for the Esri File Geodatabase Writer
Get rid of the FlexLM licensing system for FME Desktop and move to something more flexible and new.Perhaps follow Microsoft and see if its possible to use the Etherium blockchain to do this. More information here: https://cointelegraph.com/news/microsoft-wants-to-use-ethereum-blockchain-to-fight-piracyAnd directly to the research paper here: https://www.microsoft.com/en-us/research/uploads/prod/2021/08/Argus_SRDS_Camera.pdf
For example, I have several AttributeManager transformers that can be upgraded and I want to upgrade them, but I don't want to have to upgrade each of them individually.
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.
