Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
***Note from Migration:*** Original Title was: Preselect Columns to Display in Data Inspector via Attribute Selection Dialog in Inspector Transformer When non-geometric features have many attributes, viewing them in Data Inspector is inconvenient if I'm only interested in seeing a small subset of the attributes. Every time I use the Inspector transformer I must reselect the columns to display using the 'Table View Schema' dialog. To improve this, I propose an attribute selection dialog be added to the Inspector transformer that can optionally be used to preselect the columns to display in Data Inspector. Related to: https://knowledge.safe.com/content/idea/40200/save-column-settings-in-data-inspector.html
Hello FME Community:When I create a new 'Author' role level user and grant it ability to access the Schedules page, the user is actually able to see the schedules created by all other users including Admin, from repositories that it should not have access to. When I click into one such scheduled task, some fields will be blank (due to no access), and the scheduled task details look 'incomplete'. It appears to be able to click on "Ok" and I'm not sure if that means it'll try to save the Schedule.I think it'd make more sense if a non-Admin user does not see schedules that it does not own, or at least have the ability to differentiate them and definitely not have the ability to click into them by accident. Or, if this is something that can be resolved by better configuration of the roles, please advise. I have been unable to find this in the Security tab.Thanks!Ray
***Note from Migration:*** Original Title was: Configure a set running job expiry time for each workspace (vs. each run/scheduled job) Related to the FME Server 2017 "running job expiry time" (tm_ttc) parameter that cancels a job if it runs beyond a specified length of time:https://knowledge.safe.com/idea/18984/configure-time-limits-for-a-job-and-alertcancel-if.html-------I'd like a time limit per workspace.
Add the option to open a recent "Custom Transformer" from the File menu:I can open recent workspaces and templates but not custom transformers.Please add "Open Recent Custom Transformer" to the "File" menu.
I'm missing a Zoom-to-feature-Function in Data Inspector:in the tableviewat the Feature information
I work with input in files that are not always aligned & would like a way to process multiple files that require DIFFERENT offsets (or warps). My concept is to use a joiner type setup where the filename is matched to the join file & if found processed. The join file would have either 3 or 5 columns: filename, offset_x, offset_y or filename, source_x, source_y, target_x, target_y. Output ports would be "changed" & "unchanged". the output could then either be reprojected or warped as needed using existing transformers
I'd like if FME would check that the output files can be wrote to before it starts, this way it won't do all the heavy lifting and bomb out because I was silly and left the excel sheet open.
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.
https://cloud.google.com/storage/
From FME 2017 there's a neat error trap that means you don't trip over the 'rejected features' issue when writing to the Shape format quite so much. If you add a CSV reader and a Shape Writer to the canvas, the semantic capability of FME kicks in and drops a GeometryFilter on the canvas to route the null geometry records straight to a FeatureType with the shape_null geometry setting. You also get a FeatureType for points. Since the first thing you often do in this scenario is make points this means that you don't end up with lots of points being sent to a Feature Type with the wrong geometry type set. BUT, whilst this is 99% better than previously, the Null port of the GeometryFilter is auto connected to a FeatureType that gets named ' CSV_geom'. This confused a number of training delegates recently who argued that this should be called 'CSV_null' instead.A very small change needed really.
Hi. I am trying out FME and noticed the ".bil" format for ITT ENVI .hdr RAW raster is not compatible for IFSAR DEM BIL raster file format. Would like to know how many IFSAR users out there affected by this to warrant Safe consider including this support. Thanks
***Note from Migration:*** Original Title was: Connector properties Listed as Private Parameters so they can be referenced in Workspace It would be useful to have FME web or database connections parameters available as private parameters to the workspace similar to how FME Server properties are available. Use case is that when we are running in a DevOps environment where we try to automate promotion of work from DEV to TEST to PROD, we need to repoint web api calls to the instance URL described in the connection (HTTPCaller). In the case of Salesforce, base url for sandbox is test.salesforce.com while production is login.salesforce.com. Similarly for Maximo, AMANDA, Cityworks, SAP, and others.
***Note from Migration:*** Original Title was: For the 2D Grid Creator I would like to have the option of adding the width and column length in Degree Minutes Seconds instead of just decimal degrees.
Currently the Joiner transformer does not allow for all formats that the Reader does. For example, the Esri Geodatabase (File Geodb API) is available in the Joiner but the Esri Geodatabase (ArcSDE Geodb) is not.Add all available Reader Formats to Joiner transformer
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.
Hi(Generic Styler)I don't know whether FME has this option or not but the requirement is to store a symbology in common set of attributes or any common structure so it can be used for any of the format.For example:- Exposing set of attributes from DWG file and then using that fields for full fledged styling of DGN file.My idea is to create a transformer that read the symbology related attributes then convert and store them in common structure which can be used for styling of any format at time of writing the file. (Generic Styler)
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'.
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 ?
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.
***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?
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.
