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 helpful if the COLLADA reader would support reading Geometry definitions stored in the DAE as definitions so we could use the Shared Item tools. Currently the COLLADA writer supports this - I can create a COLLADA file with a single model but unfortunately it seems when reading that these definitions are read as aggregated mesh objects. When writing the same file back out to COLLADA the size blows up because a new geometry definition is created. When working with a file with 1000 of such geometries it blows up from about 1 MB to over 250 MB...
I love the glTF writer and we have been using it a lot in conjunction with our Cesium based applications to help bring customer data into their interactive 3DCityModels.glTF is awesome because it supports both vector (lines/points) and True 3D surfaces. One issue we're running into, however, is that I'm unable to style the vector features in the output. The fme_color attribute appears to be ignored and the GeometryColorSetter/AppearanceSetter rejects it because it is InvalidGeometry...This means we're unable to bring in colors from CAD drawings which makes it lose some of its valueI would love if the gltf Writer would recognise the fme_color attributes.
In the Navigation tree, we can click on a Bookmark and the canvas is centered in its content.It would be also useful (at least for me) if in an Annotation we could create a link to a bookmark.In my case, I tend to create individual bookmarks for the SQL sentences used in Readers and Writers or for code samples of the PythonCaller or SystemCaller... The idea is adding an Annotation to the Reader/Writer/Transformer with a short sentence about what they do and a link to the bookmark where extended information can be found.
When pushing the refresh button in the Inspector, it refreshes all data sets. Sometimes, you want to refresh one data set only. The idea is to add 'Refresh Dataset' when you right-click on it. Similar where you find the possibility to 'Remove Dataset'.
Could you make the icons for transformers that have more than one input have a visible difference to those with only one (a small number, different colour or input lines on the left).Often times I don't really know what to search for to achieve a goal, but I will know that I need two inputs not just one, so if I can visibly see the difference when searching for a transformer it will make narrowing it down much easier.
Currently on FME Cloud when you launch an instance you have no control about the virtual private cloud (VPC) it is launched into (we actually launch it into our own VPC). I am interested in soliciting feedback on whether adding support to launch into your own AWS VPC would be beneficial. We have already had quite a few users request this, as for a lot of customers their first step in moving to the cloud is the hybrid cloud. Just to propose some ideas. Allow you to launch into your own VPC in FME Cloud and then allow you to link to your VPC to ours via VPC Peering.We could allow you to launch directly into your VPC but this is likely to bring with it some limitations and additioanl configurations.
It would be great to be able to test an external database connection from within FME Cloud to ensure it is set up correctly before having to run a published job.
I attended the Partner Summit 2019, which was fantastic! Only thing I was missing was specific, advanced training sessions to the partners. We should know new functionalities of FME very well, and of course we study by ourselves, but it would be a great opportunity to learn e.g. IFC writing from Safe experts or how to write IMDF and other indoor mapping formats. The sessions don't have to be long; just 1 to 2h would be enough. I suggest that in upcoming partner events, some of the tech sessions and roundtables could be changed to training sessions.
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.
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.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.