Open ideas have been reviewed by our Product Management and are open for commenting and voting.
I would like to see the omf included as a reader/writer - most mining applications now support this format so it could be a quickwin for FME.https://www.linkedin.com/pulse/open-mining-format-more-important-than-you-think-industry-large/ Myself (and most mining houses) would also like to see FME native support for:Micromine - https://www.micromine.com/micromine-mining-software/ - .dat files, simple text files but be good to native supportLeapfrog - https://www.seequent.com/products-solutions/leapfrog-geo/ Datamine - https://www.dataminesoftware.com/solutions/studio-rm-resource-modelling/ - .dm filesDeswick - https://www.deswik.com/software/IOgas - https://reflexnow.com/product/iogas/Surpac - https://www.3ds.com/products-services/geovia/products/surpac/ - again simple text files but be good to native supportBeing able to reproject to and from custom mine grids to UTM etc would be great as well as filtering transformation as a start.
Add an option to the BulkAttributeRenamer which replaces non-ASCII characters in AttributeNames with ASCII in a standardized way.e.g. Ö->O, Ø->O, ø->o, æ->aeUTF-8 code c380 to caafWould be useful e.g. with PostgreSQL writer etc.
There seems to be a notable hole in the geometry handling of FME.There's no easy way to split a polygon by a line. This is something even kindergarten kids can do ("if you cut the pie here, how many pieces do you have?"), but FME can't.So can we please have a transformer that splits a polygon by a line. If you search these boards you'll see it's a commonly requested question (how to).
Source data for buildings and other BIM related objects often comes as wireframes with 3D vertices. For example Microstation Smart solids are read by FME as wireframe data. We often need to recreate true solids or faces in FME for these features to write to BIM formats such as IFC or Sketchup etc.Safe PR#39030
PythonCaller has no attributes to set apart from grouping and output parameters, and of course the code.Any input parameters to be set outside the code, needs to be set in another transformer like AttributeCreator.It would be nice to have a small list of input parameters, so one can easily change input parameters without changing the code. Just a simple name/value list, just like other transformers. The values could then in turn be tied to user parameters in the workspace/custom transformer if need be.
It would be helpful if you could save an empty workspace. I would like to start my workflow by selecting 'Blank Workspace' and then being able to save it. At present you must begin editing your workspace before you can save it. This means you often forget to save the workspace and if FME crashes you loose what you are working on.I find adding any old transformer to a workspace in order to save it discrupts your thought process. Not a ground breaking idea but would be a tiny improvement
Could it be possible to add a new transformer with Moral global & local autocorrelation indexes?
When a distribution is not normal you need addittional measures to shape the distribution: Skewness and Kurtosis.If they can be added to the StatisticsCalculator transformer would be perfect.
The geometry picker should have an easier interface for setting basemaps and it could also support other formats than WMTS and also other CRS. If one could put vector layers on top of the basemaps to indicate where is data, it would be nice too. These updates could provide very powerful and easy way to e.g. let citizens or other organizations to download data from the provider organization. For example: administrator sets up a FME data streaming server app with geometry picker that has a basemap with polygon(s). The polygons tells the boundary/boundaries of any spatial dataset. Everyone with access to the app could easily see where they could get data, then just simply draw an area of interest that overlaps the polygons, and get their requested data through web browser download.
As an FME Admin I would like to have an FME server rest api call that can help me determine if users are creating/ using notification topics to let them know that the workbench failed.Enhanced workspace rest api call that automatically associates the email of the workbench author so that I can easily on notify them when something fails.
It looks like FME is very flexible in reading JSON files containing smaller errors. In our case we detected an extra "," at the end of an array. The JSONValidator detects this error clearly with the following error message: 'A trailing comma was found after the last value in an object or array'. But the JSON-Reader never validates JSON files and seems to be flexible and okay with minor issues like the one occured here. Please improve the JSON reader to validate the content of a file by option.
It would be useful if FME Server could be configured to have a maximum file size in the DataDownload service before splitting/spanning the archive into multiple files.
I would like to be able to pan beyond the extent of the workflow, which I believe is currently not possible. This would make it easier to create room for additional workspace items, which I would currently do by zooming out.
When a workspace app features a streaming service and is configured to run immediately, the URL is automatically extended by "/streaming/fmedatastreaming/[repository name]/[workspace name].fmw" after workspace app was triggered.Any user who likes to bookmark this page receives a 404 error code when trying access the page because the bookmarked URL including that annex is not working. For the sake of a better accessibility especially for non-professional users, I suggest to either hide/suppress the URL annex or let a workspace app also work when directly addressing the entire URL.
Following up on my question here, I would like to know if there might be more FME users out there who'd also like some enhancements for 3D.I am mainly thinking of full appearance support, meaning that FME should be able to deal with complex materials that include alpha maps, bump maps etc. and not just the basic texture. This is important when converting format A (e.g. SketchUp) into format B (e.g. Google KML/COLLADA), because visual information gets lost in the process, which might lead to a 3D model that simply doesn't look the same or even looks bad.Let me be clear: I don't need full 3D support. This would take years to build and there are many programs out there that are probably more suited for the job. I also don't think that the Data Inspector should become so advanced that it's able to render these complex appearances.What would be nice though, if tools like Grasshopper (Rhino) could work side by side with FME. It already offers a very similar user experience. If these two applications could be combined, it would become a very powerful 3D ETL suite!
Writing to SQL Server can be frustrating if you don't pay attention to the attribute types. Generally Varchar is needed as any whitespace may cause issues with styling data in Arcmap or other GIS programs. The default character type should change to reflect the best types for any given writer.
See this request for Data Interoperability:https://community.esri.com/t5/arcgis-pro-ideas/implement-capacity-to-view-and-work-with-new/idi-p/1250477https://www.tgs.com/press-releases/tgs-launches-new-open-source-solution-for-multidimensional-energy-data
Often I will build a workspace in FME desktop and it runs fine. Then I publish it to FME Server only to discover later that it fails to run on FME server because of a “Python Compatibility” issue. It would be great if FME Server could check Python Compatibility during the publishing process.
We cannot write a dgn mesh geometry type. We do lots of work reprojecting dgn files from one coordinate system to another and all our meshes get exploded to lines. This is less than ideal, please add support for writing dgn mesh geometry.
Seen in this community post: https://community.safe.com/s/question/0D7Dm000000994eKAA/detailWould be nice if this was handled natively within FME. Currently there is are workarounds, to use multiple writers or to use an SQLExecutor transformer.
Our organization is growing in its use of Tableau and Tableau works more efficiently with Hyper files than with .xlsx and .csv files. There is a need to continue to use FME to clean data and prepare it for Tableau use and FME is preferred to use over Tableau Prep because we already have in place coding to run updates on Windows scheduler on our servers where we would need to purchase additional software to do this with Tableau Prep. As a result, we have identified we can write files from FME to a Hyper format, but there is yet no Reader available to read the files written and check them for accuracy. We would like to see a Hyper file reader added to address this. This will save having to open the files in Tableau Desktop or Tableau Prep to view them outside of FME.
StringLengthCalculator currently supports usage for just a single attribute. This transformer should be expanded so that multiple fields could be selected at once. This would help with determining maximum lengths of data to help troubleshoot data truncation issues, but also with validating or setting field lengths for output writers.The output could be individual attributes or perhaps a list.
My HTTPCaller returned a JSON response body, and now I'm using JSONFragmenter to grab some returned records to use in authoring a workspace. I started fragmenting 42 minutes ago and it's still running. Really just wanted to return ten records or so.I suppose the slowness is partly due to caching (while authoring) with retention of the response_body over a few thousand records. FME Workbench is using quite a bit of CPU and memory, and is storing to disk.
"Night mode" / "dark mode" of FME Workbench and InspectorMerged Ideas:Changing the background color of Workbench or adding a dark mode by mathieu_ambrosy on September 7, 2017Totally useless so totally indispensable : the ability to change the background color inside Workbench (the main tab).So we could use a dark background for example.And less specific, why not a "dark theme" or a "dark mode" in Workbench ?Nice idea for FME users falled to the lure of the dark side...
In a similar implementation from the Navigator and the Transformer Gallery pane, it would be nice to have a search box that would filter the list of attributes or attribute types on the Feature Information pane.During data exploration, JSON, XML, and flattened semantic data can have many attributes and lists. It would be nice to shorten the list in the Feature Information pane without minimizing the attributes in my canvass. A good sample to filter would be "Date" if there are many and labeled with suffixes and not as prefixes.
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.
