Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Many transformers have the option to save settings as My Defaults, it would be great to have that functionality on writers as well.For instance, on the jpeg2000 writer, we have standards in regards to the Compress By Percentage parameter which is not the default 75. Every single time we add the writer we need to remember to go and change it.
Add the keyboard shortcut Ctrl + Shift S in order to Save As... within FME Workbench.
In FME Desktop, when I press Ctrl-F to bring up Workspace Search, the cursor should automatically be inside of the search box. (Currently, I have to click inside of the search box.)Additionally, when the most recent search term appears, it should highlight the entire string so that I can either press Enter to redo the last search, or just start typing to enter a new search term.
***Note from Migration:*** Original Title was: JSONFragmenter/Flattener should route input feature to port if HTTP request fails You can set a URL to the File/URL parameter in the JSONFragmenter/Flattener to read a JSON document from a Web server. Currently FME stops the translation if HTTP request fails with the transformer, but I think it would be better that the input feature would be routed to the <Rejected> port so that the user could define a subsequent process if necessary.cf. the XMLFragmenter routes the input feature the <Rejected> port if HTTP request fails.
I think it'd be great if we could have an option to handle 'no-data' or write off values like '9999' for point clouds.
I've been thinking for a while, it would be great to have a button in the mini-toolbar that comes above the feature types or transformers for opening datasets in the OS default application. For example when writing in Excel, you could open the written file directly from FME Workbench without having to open the containing folder and clicking on the written file.
I think there is a PR for this somewhere but no Idea that I can find. The most common use case I see is datum transformation between ellipsoidal heights and gravity based heights. CsMapReprojector can do the job but not write the VCS metadata to ArcGIS formats.
The current version of FME (2019.0.0.0 (20190328 - Build 19238 - WIN64)) S-57 (ENC) reader only accepts data with file extension (*.000) for ENC base data files and (*.030) for Catalogue file. According to the International Hydrographic Organization (IHO), the current ENC standards had been upgraded to version 3.1 hence the file name of the most of the ENC catalogue files would be "CATALOG.031". It is suggested the FME S-57 reader shall also be upgraded to allow the change in the IHO standards. Furthermore, according to the IHO ENC standards, the data structure of the updating file (with the file extension *.001, *.002 etc) for ENC data is identical to the ENC base data. It would be a huge benefit to users to validating this S-57 ENC updating files if the FME S-57 reader allows files with extensions *.001, *.002 etc.
To speed up work, with cartographic base, you do have to draw areas on an existing cartography. Using the PDF annotations, they could be exported as well as the rest of the information. To this day you can not export the annotations created with the adobe. thank you
It would be very nice if the administrators could adjust the FME Server website so that possibly even a company logo can be placed there. We use, for example, 2 different FME Server instances. To distinguish these we have different logos placed on the page. It would therefore be very nice if there would be a wildcard on the website for such purposes.
I'd love a way to expose data type/encoding (32 bit integer, UTF-16LE, 64 bit real etc) as values. These encoded values already show up next to the Attribute Name in the Feature Information Pane. An example could be:OBJECTIDNameAgeAddress01Andy22.51234 main St, college station, tx02Joe43143 2nd st, college station txwould output as:OBJECTIDNameAgeAddress32 bit intString64 bit realstringThe reason I'm trying to do this is to help with describing sensitive tables with support groups, be it Esri or FME or other. I've been trying to make a custom transformer that'll do it but can't quite crack it. Thanks
It would be useful if the list created by Matcher would include an attribute that indicates whether the element (matched feature) is oriented in the same direction as the resulting feature, or if it's in the reverse orientation. In other words, include an attribute that indicates whether this element was matched because we selected "lenient geometry matching".
When Labeling closed polylines with "Label position" parameter set to left or right and a value for "Label offset" parameter, some label feature texts overlap the polyline or are offset more then others (visualy).I got a workaround for this by setting "Label offset" to 0 and using the Offseter transformer to Polar coordinates Mode, Distance by Conditional value: 0-90 half the label height, 90-270 the label height and 270-360 half the label height, and Polar angle set to @Value(_parallel_rotation)+90. Actually, the label height plus something to clear the linewidth.It would be nice to have this implemented in the transformer.
Would it be possible to add a refresh button to the FME server job submitter so that when a workspace is republished to FME cloud with additional parameters, you don't have to re-map every parameter in the workspace.Currently to update the transformer you must select a different workspace before going back to the one you wish to update and then re-map all of the parameters.
Right now the Microstation DGN readers doesn't support Mesh element types. When the reader encounter such a object the following warning is shown in the log: WARN |DESIGN READER: Found element of type '105', which is unrecognized or unsupported. Skipping elementWhen working with infrastructure projects Microstation is widely used and the mesh element type is as common as butter on a toast.A question about this topic was asked already in February 2014 here.(For further reference to Microstation element types, here's a good link)
In FME 2019.0 transformer presets were introduced. This is very helpful to reuse existing settings for transformers.It would also be very handy to have a possibility to have preset groups for multiple transformers. For example for certain areas, when you load the preset group it will choose the presets for all transformers that are in that group according to your settings for that specific area.
if I need to use the function of a transformer in a PythonCaller for example, please add a sample Python snippet after the help description of the transformer to quick utilize in the editor.
When I leave the PythonCaller unintended with the Cancel button or with the Esc key and I have done a lot of programming, everything is lost.It would be great, if FME asks me if I want to save the unsaved changes in the PythonCaller.
Hi,An extension to the current Choice parameters is to add a parameter where you can select multiple choices and if the choice isn't inside the list you can add your own one (or multiple ones).Currently to achieve this it's necessary to work with 2 different parameters, making it sometime very complicated.As the Workspace developer I already know certain options, as such I can put them already in the list, however new choices can be developed every day (theoretically speaking), with the Multiple choice + text, I don't need to update the workbench everyday.So the multiple choice or text would be a cleaner way to provide this than working with 2 different parameters.
Currently it is rather cumbersome to manipulate schema features using the attribute{} list to e.g. remove or rename attributes. It would be great if e.g. the AttributeRemover / AttributeRenamer could auto-detect if a schema feature had entered (based on the presence of attribute{}.name) and then do its magic directly on the schema definition as well as the feature itself.
We would create three.js javascript from 3D objects. This could then be output directly in a text file for later inclusion in a webpage, or wrapped into a .html file and output by FME. Some samples made by a prototype in FME: IFC->three.js at https://dl.dropboxusercontent.com/u/173473402/threejs/ifc.html and go to Paris with https://dl.dropboxusercontent.com/u/173473402/threejs/eiffel_tower.html .
I'm running a WorkspaceRunner associated with a workspace which intentionally has enabled Inspectors. However, every time a workspace is completed and another View tab is added to the FME Data Inspector it wrenches the window focus away from other windows very unpolitely. FME Data Inspector should play well with others and update when not in the foreground...
FME’s Minecraft implementation is fantastic, but as someone attempting to do very large translations, as well as making use of programs external to Minecraft, having support for schematic files, a more compact, but still NBT based file for storing combinations of blocks, would be incredibly useful. Schematic files are fairly simple, and I’ve already built a rudimentary prototype for reading them as point cloud features, however as an inexperienced FMEer and data manipulator in general, I don’t feel equipped to tackle this one on my own. I wasn’t sure whether to post this as a question, or a suggestion, but any thoughts are appreciated.
Dear Mr./Ms., I work in a Portuguese Government Institution: Direção-Geral do Território (Directorate-General for Territorial Development). My Institution is the Central and National node of the National Spatial Data Infrastructure (SDI) and is responsible for monitoring and reporting information to European Commission (INSPIRE - Infrastructure for Spatial Information in Europe). I am working on a project for the Portuguese Government and the coordinate reference system is EPSG: 3763, PTTM06 - ETRS89. Unfortunately the FME Software does not have this coordinate reference system in the options. Therefore, I request your attention and help in the creation and availability of this reference system in FME Software, because all the data and projects in which my governmental institution works at national and international level (INSPIRE), are in this coordinate reference system. Best regards,Sérgio Ferreira
FME Desktop includes limited options to customise the interface to support people with impaired vision for example, other than alterations to the font.I frequently work with colleagues and customers with some level of colour-blindness and the ability to discern the difference between a red and green attribute port arrow, or a transformer parameter button, or a featuretype connection arrow (the main offenders) colour is difficult or impossible. This means that 'issues' in the design or setup of an FME Workspace can often be overlooked with the resulting data problems.This makes interesting reading regarding some of the challenges:http://www.colourblindawareness.org/colour-blindness/types-of-colour-blindness/The ability to apply a blanket colour change to some of these port colours would be very handy I'm sure.
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.
