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 neat to have a mobile app that allowed me to provide all the sensor data from my phone to a workspace run on FME Server or FME Cloud.I'd want to be able to use any FME Server, probably multiple and any workspace. In some cases I would just want to run the workspace, but in other cases I would want the output of the workspace to be provided back to the phone. For example: PDF, Powerpoint, or cool stuff like Augmented Reality or any new app that might come out and which uses data.I don't want a complicated app! Just let me run the tasks (workspaces) and see the result.
The current FME(2016.1.0.1) only allow the user to save one setting. But many times we need to switch between in many Settings, I hope I can save multiple setting, and can be set each name.
The ArcGIS Online reader and writer are quite slow to use. For every feature type, in every AGO reader and writer, FME currently loops through all accessible groups twice (once to find the feature service, once again to find the layer). When a user only has access to a few groups within his organization, it's merely an annoyance. When a user has access to a large number of groups, waiting for FME to find the correct layer can add minutes to the time it takes to run a workspace. There is a workaround where the HTTPCaller can be used to directly access a layer, much faster than the AGO readers/writers can, but this method has several other downsides. It would be great if the official AGO readers/writers could be improved to be a lot faster.
From @lefred06 at https://knowledge.safe.com/questions/96349/s57-customized-files-location.html Customized S-57 CSV files should be stored outside of the FME installation directory so they aren't lost when FME is upgraded or reinstalled.
We run 32 and 64 bit versions of FME Desktop along with Dev and Prod environments for FME Server. Some of the more complex workspaces we create involve a fair bit of manipulation of inputs, outputs and resources between these instances.I am currently in the process of writing a startup python script to identify which environment (desktop 32, desktop 64, Server Dev, Server Prod) a workspace is running on - this works. From there I can read a config.csv which has parameter names and a separate column for each environment - this also works.The next step would be to set appropriate user parameters, to circumvent the need for manual changes in the different environments, but this seems to be a sticking point as user parameters need to be predefined.Could provision be made for the dynamic creation and setting of user parameters at startup?
I have a workbench where I have multiple readers and each reader goes to their own DuplicateFilter. Each DuplicateFilter creates a DuplicateRemover table in the Temp folder. When the reader finishes, I wish the DuplicateRemover temp file used for that reader would be cleaned off. I've begun running into memory issues as the files I've been reading in have grown.
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.
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'.
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.
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.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.