Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Imagine a case where the source XML document has more complex structure and every <record> element contains much more child elements than shown in the below, and you need to fragment the document into individual record but want only preserve a few attributes. e.g. only "id" and "attr1" are necessary in the subsequent process.<records> <record id="1"> <attr1>11</attr1> <attr2>12</attr2> </record> <record id="2"> <attr1>21</attr1> <attr2>22</attr2> </record> </records> You can do that using the XMLFragmenter with Flattening Options followed by the AttributeKeeper etc.. [Edit] My bad. I thought the XMLXQueryExploder with this XQuery expression could perform that more efficiently, but it doesn't work as expected in fact. I don't know why, but the fme:set-attribute function in the expression seems to retrieve the value of <attr1> element under the last <record> element always.for $r in //record return { xs:string($r/@id), fme:set-attribute('attr1', $r/attr1/text()) } Also, the transformer has Remove Source XML Attribute? parameter now, but the source XML attribute name won't be hidden even if you set Yes to the parameter. I hope the attribute name could also be hidden.
Hi,I'm typically using the AttributeManager in a certain way just before final output, namely adding all needed attributes as new attributes at the top, and setting all input attributes below to "Remove". This makes for a very clear and simple interface to maintain later.My suggestion is to use this strategy by creating a new AttributeManager transformer that consists of the list with the new attributes to output (as in AttributeCreator), and having it remove all other attributes automatically.Cheers
In many transformers it is possible to set 'Null' as an output value. In some cases you would like an attribute to go missing if it matches certain conditions. I would love to see that option added to the context many where 'Null', 'No Action' and 'Clear Value'.I think it won't be used directly, but especially in Conditional Statements it would be an improvement.
I think it would be great to have the AttributeValueMapper integrated in the AttributeManager. Off course it is possible to create a list of conditional statements, but that works much slower (in both setting it up and running a workspace) than using a AttributeValueMapper. I would love to see it as an extra option next to 'Conditional Statement'.
If you have multiple attributes that you want to split the same way, e.g. by pipe or space, it would be useful to have an option in the AttributeSplitter to do this rather than having to insert multiple attribute splitters one after the other. You would specify the delimiter and then in a separate section all of your attributes - you could toggle which ones you want to split and give the list name for each one there and then.
From this Question: Is it possible to deny changing password of an FME Server user?I think it would be useful in some situations if the administrator of FME Server could control individually these permissions on a specific user.Change PasswordUpdate EmailManage Token
Zoom to Selected Object (Transformer, Reader, Writer, Bookmark, etc): user is able to progressively zoom closer to a selected object(s) with the + and - zoom buttons and slider. Currently when the user has a selected object and presses the +/- the page zooms in/out on centre and not the selected object of interest.Zoom In/Out Tool: User clicks on the Workbench with the zoom in/out tool the page zooms in/out based on the location of the click to re-center the workbench. This alleviates the need to drag the page to recent on an area of interest.Bookmark Zoom: User selects to view/zoom to a bookmark. The screen would be refreshed with the upper left corner of the bookmark positioned to the upper left of the display. Currently the bookmark is entered to the display and the user must scroll/pan to the left to see the start of the process within the bookmark.
The translation log has a summary of the number of features read and written. It would be nice to have a summary of rejected features as well.When using FME server, you don't have the nice visual cue of Red Bubbles, nor color coding when scanning the log. The summary would be an easy indicator that you need to go look in detail at the log.
FME Server 2017 now allows us to cancel a job if it exceeds a certain time limit. It would be nice if we could set up a Notification Service instead.
Copying parameters between workspaces (like copying transformers)
Support panoramic / 360 degree photos (and videos). Allow clipping by view direction, conversion between cubic and equirectangular formats, etc.
Similar to uploading items on FME Hub, it would be awesome if we could specify a custom icon for anything uploaded to FME Server. This might help convey functionality to end-users.Initially this could be restricted to FME Workspaces, but maybe there is demand for other items? Comment below!
From this Q&A: How do I create a folder whose name is based on the date the Workbench is run?It would be nice if FME could create automatically a new directory which is specified via the Target File parameter in the FTPCaller.
Any plans to go non-apple and support ARCore? https://developers.google.com/ar/discover/
Not so much a format as a source/destination for data files. Idea is that FME would retrieve or push data in / out.
On FME Server - RESOURCES. Add option to right click and "Save as" or "Download to" - so you can choose where to save the files instead of the default location.
Instead of EC2-based FME Cloud, would it be possible to run FME Workspaces as a service: something like AWS Lambda and payment would be per run. This would serve cases when FME isn't used continuously / often, but needs to be available when needed.
Hey guys,I needed to install FME on Debian 9 (Stretch), and since I struggled a bit to do it, I thought someone else would appreciate to read what I've found.So the first step is to download libpng12-0 as described in this post:wget http://http.us.debian.org/debian/pool/main/libp/libpng/libpng12-0_1.2.50-2%2Bdeb8u3_amd64.debInstall it using dpkg:dpkg -i libpng12-0_1.2.49-1+deb7u2_amd64.debThen download the Ubuntu 16.04 version of FME:wget https://downloads.safe.com/fme/2017/fme-desktop-2017_2017.0.1.2.17292~ubuntu.16.04_amd64.debAgain, use dpkg to install it:dpkg -i fme-desktop-2017_2017.0.1.2.17292~ubuntu.16.04_amd64.debThis should end with an error message, but don't worry, everything will be fine.Use apt to fix missing dependencies:apt --fix-missing -f installIt will install a lot of missing lib to run FME.Now, if all the previous steps ended successfully, you should be able to launch the engine:/opt/fme-desktop-2017/fmeYou should get this result:FME license system failure: FME is not licensed for this machine. Contact your Distributor. Your registration key is XXX-XXX-XXX-XXX. Program Terminating Translation FAILED.then you only need to setup your license and you're good to go!Edit : new link for libpng12-0
***Note from Migration:*** Original Title was: Remove duplicate and nearly duplicate coordinates in sequence using a tolerance in the GeometryValidator Add the ability to the GeometryValidator to remove duplicates coordinates that are within a set tolerance of each other. @oliwerurban
Add a reader/writer for Bentley ProjectWise
***Note from Migration:*** Original Title was: Non-spatial formats. "projectwise" , "Sharepoint" , "Other document management systems.
This transformer could:convert datetime values from one time zone into another;set time zone;reset time zone;remove time zone.The time zone can be provided as UTC offset, <utc> (for +00:00), or <local> (for system local time zone).Please vote this idea if this transformer would be helpful.
***Note from Migration:*** Original Title was: Update New Zealand Datum Transformation Grid (NTv2) to account for plate movement A new grid has been issued to account for major movement of parts of New Zealand after the Kaikoura Earthquakes. Some areas have moved by as much as 6 metres. Using the old grid will give significant errors and will not align with the cadastral layers provided by LINZ.Replacing the grid can be a user operation, but it would need to be done every time a new FME version is downloaded. https://www.linz.govt.nz/data/geodetic-system/datums-projections-and-heights/geodetic-datums/new-zealand-geodetic-datum-2000-nzgd2000/nzgd2000-deformation-model
Allow ability to selectively 'Ignore Failed Transformers'. This would be very useful with notifier-type transformers such as Emailer or SlackConnector when a web connection cannot be made and their actions/output are not crucial to the workspace. If some transformers can be selectively ignored, then simultaneous workspaces processes that are important to the user will not be stopped.
As with the AreaBuilder, the LineCombiner is used a lot in combination with snapping.Adding a snapping tolerance to the LineCombiner would allow to handle the features just once and could improve performance.And it would be consistent with the AreaBuilder.
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.
