Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Is it time that the FME Options tab 'Workspace Defaults' got its contents combined with one of the other Options tabs? Arc/Ellipse Stroking seems like an odd option to separate out and give it a tab all of its own.
It would be great if workspaces ran as soon as you hit the run button. At the moment the larger the workspace the longer it takes for FME to start the translation. This makes testing and authoring inconvenient as it takes a lot longer to run simple tasks.Scenario: run a workspace with only a 'Creator' enabledLarge workspace: takes 12 seconds to startStarting translation... 2017-09-06 11:00:45| 12.0| 12.0|INFORM|FME 2017.1.0.0 (20170731 - Build 17539 - WIN64)Small workspace: runs instantlyStarting translation... 2017-09-06 11:01:25| 0.0| 0.0|INFORM|FME 2017.1.0.0 (20170731 - Build 17539 - WIN64)
It would be helpful if FME 64 bit had a work space parameter that limited the total memory that can be used by that work space. This would allow users to more easily run multiple work spaces that are RAM intensive without causing failures due to memory issues. I run several work spaces in Amazon environments with 60+GB of available RAM and I have had issues where one work space will consume over 59GB on one transformer which in turn causes my other work spaces to fail. I have particularly found the SpatialFilter and Intersector transformers to be some of the most aggressive RAM consumers. Thus it would be useful to be able to set limits on either the work space itself or even on individual transformers on the amount of RAM that can be consumed.
Currently, the MongoDB writer doesn't allow me to add new attributes to an existing collection. It only allows me to write exactly what is present in the collection already. To get the attributes I want, I have to drop the collection and recreate it (drop and create), but that means losing existing data. I don't want to lose existing data, I don't want to re-read all data and I don't want an extra step of creating JSON in FME myself. See this Q&A also.
It occurred to me that in the rare occasion someone might want to remove their FME Desktop App from their Mac.
Hi FME community, I propose to have multiple views in FME Desktop to represent the different views for the same script. These views can be tabbed views or dock-able. This will help working with very complex and dense scripts where referring to different areas in the script is essential and managing through bookmarks can become cumbersome. There could be limit on number of views. This could be similar to what Microstation has. I think this will really help! Thanks.
Ability to inspect by clicking on the connector while the workspace is running. E.g. a long translation writing errors to a excel writer, if we can inspect by clicking the connector connecting to the excel writer, I do not have to wait until translation finishes. Using the inspector data I would be able to start debuging instead of waiting unit it finishes the translation.
It would be nice to have a little more flexibility in the attributes to ignore section of the schema writer. Things like wildcards would be useful, i.e drop all attributes containing the word 'test'.
Something very similar to the Database Updater transformer. The ArcGIS Server Web feature service writer is still missing and the ArcGIS Portal Feature Service is still broken in the current version. I hope Safe can get these writers released to production and then have this updater transformer next.
Our IT group have decided to use this new Micro Focus Vibe 'dropbox lookalike' plateform for sharing files. Would it be possible to have a web connector for that service so I could upload my files created by my FME workbenchs to this plateform ?
***Note from Migration:*** Original Title was: Copy boundingbox, polygon or xmin, xmax, ymin, ymax from the Data Inspector into Workspace The Inspector is often used to narrow down a specific area to a boundingbox to be used in Readers, Clippers etc. Users often transfer these values manually by looking at the coordinates. Personally I often measure the distance and copy the result from the log-window in the Inspector to a Creator in the Workspace. Even made a custom transformer to parse this result into a boundingbox:Measure Distance in UTM83-10: 259.3745 (METER): (485831.2113, 5460647.1841) To (486053.7504, 5460513.9494)But wouldn't it be great if this could be done much easier? For instance there could be a "Copy Extent" to GeoJson or FME XML. Then you could just paste this into a GeometryReplacer. Could even be much fancier with a drawingtool that could copy any drawn polygon to GeoJSON in the clipboard?
When you find an "item on hub.safe.com - you should be able to discuss this in the knowledge center in its own folder. For instance autocreate /WebConnections/Github as a "product"/"folder" on knowledgebase to dicuss enhancements that can be done on that particular FME hub item. Also it would be nice to pubish everything on FME Hub on github. So anyone with a github-account can upload a new version of that transformer. The goal here is to get many users to contribute to improve errors and features for Custom Transformers / Webconnections etc. https://hub.safe.com/web_connections/github
Hi,The "Choice with Alias" user parameter is great because we are able to import coordinate systems, readers and writers.Why not the ability to import "Character Encoding" items too ?It would be great ie for a shapefile writer. We could import easily a selection of character encoding in a user parameter.Mathieu.
Currently the ESRI Reprojector does not support composite transformations like ArcMap does. It would be great to see FME could adopt this functionality. A common reprojection from NAD27 to WGS84 typically requires a composite transformation and the way to do this with FME at present (FME 2017.1) is to use two ESRIReprojectors. For those used to the ESRI workflows this can be a big trip up.
It might be nice if FME had improved database transaction support.Here are some ideas:Continue with the load if a record fails to insert and is rejected?Ensure that child-parent records are written inside the same transaction.Share a transaction between the FeatureWriter and the SQLExecutor.In the FeatureWriter, output features (via rejected port) that failed to commit, but also continue to write the remaining data.Control when transactions are shared between SQLExecutors and writers.I wonder what others think is important?
If I have shared FME folders, FME_TEMP set, use a TempPathnameCreator and so on those file name options are hard to apply to the File Name parameter. How about adding those options to the file name picker?
It might be good for FME to support reading and/or writing Redis.I wonder how others might work with Redis and FME?Would reading or writing be more interesting?
It would be nice to have a publication service for REST services (like MapServices & FeatureServices). This would be useful for those organizations who want to set up something to run to either do a complex field calculation or send an email notification automatically when a new record is added to the REST service.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.