Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
I have a script in FME Server that gets called by a URL with parameters for the WHERE clause. The querystring on the URL looks like this:some_example.fmw?Year=2010&Neighbourhood=Kensington-Cedar%20CottageThe WHERE clause in the database reader then looks like this:neighbourhood = '$(Neighbourhood)' AND year(event_date) = $(Year)As I understand it, there is no way to "parameterize" the WHERE clause to avoid an SQL injection attack. Since we are planning to expose our FME Server to the world, it would be great to have this ability in database readers.
Right now FME Server and FME Cloud allow the user to upload (or select from the resources) any file they want as a source dataset e.g. if I set up a workspace with a Shape reader but the user uploads a DXF file it's just going to fail with some horrible error messages. That's not very user friendly.What I'd like to see is an option to disallow uploading/selecting of unsupported file types, kind of what the Desktop version is doing at the moment. It can still be circumvented, but this would prevent a lot of the accidental cases.
Gravitysketch is a new 3D sketch tool where you can create 3D features. http://www.gravitysketch.comIt would be great to create 3D objects there and convert them into features for use in City Engine and Esri GIS formats.
Good day FME'ers,One of the most useful features to come in FME 2016 is the improvements to the regex engine. With this improvement came a nice little quick help guide to writing regex statements. I would find it useful to have a similar quick help guide in the DateFormatter with the most frequently used codes.Thanks
***Note from Migration:*** Original Title was: Temporarily hide table view in data inspector when showing table in central area Instead of having the Table View window display "The table is being displayed in the main window's central area" when the main window is set to Table View, close it and regain the real estate and then reopen it when switching back to 2D or 3D view.
Set Conflict resolution per attribute (e.g. FeatureMerger) in stead of supplier / requestor. Sometimes you only want a few to be overwritten and a few to be kept. This can be done now by using a AttributeRemover before the merging transformer, but it would be nice to manage these settings in the merge and filter transformers.
For Example,Editing the SQL in an SQLExecutor requiresopening the Parameters form (popup)opening the SQL Statement form (popup)at this point the workbench is now hidden behind 2 layers of windows which demand focusi.e. both of these forms have to be closed before getting back to the workbench, making jumping in and out of tools more fiddly. One example is having to close the SQL form to read any error messages generated in the Transaction LogI suggest the forms can instead be made tabs on the main window, allowing for a less cluttered interface experience and quick switching between the forms via the tabs.
I was recently playing with some notification topics for successful or failed jobs. So I created a Push subscription and didn't specify the subscriber_content. Guess what? FME pushed the JSON job result to the URL I specified. Great! Exactly what I need. No REST polling necessary!Then I tried the SQS subscriber without subscriber_content. In this case, nothing was sent, because FME did not replace the empty message body with a job result and SQS does not allow an empty message.This is what I mean with consistency: why would this behaviour be different for each subscriber?Furthermore, does anyone of you know of a documentation page where I can get a proper overview of all the job result variables I can use in a subscriber message template? For instance: as a workaround to the SQS problem I mentioned above, I am now sending an SQS message that only contains the job ID (so I can then get the job result through the REST API using that ID). To do this, I used the {id} variable in the message template, because I read that in some example somewhere. However, other variables (e.g. {status}) do not seem to work here.I would love to see a proper overview of all the variables we can use and for which subscribers we can use them.
***Note from Migration:*** Original Title was: FMEServerJobSubmitter/Waiter: Callback result or custom message from successful job Wouldn't it be nice if we could post something back to the calling workspace, e.g. in a _customMessage string attribute on the FMEServerJobSubmitter output, or by actually having the FMEServerJobSubmitter output the data from the "Data to Post" writer setting (set when you publish the job)?
Accessing and editing settings and code within parameters transformers is often fidely, often requiring: selection --> right click --> further selectionThis could be replaced with a standard 'edit' panal that always offers editable settings and is populated on selection of a transformer / parameter, immediately exposing relevant settings of whatever is in focus
When you bring in a dataset with multiple tables it would be nice to change the order the tables are displayed in to help clean up a workspace.
Currently the NumericRastrizer always gives a constant string "NumericRasterizer" to the resulting feature as "fme_basename", even if you set "fme_basename" to the "Group By" parameter. It would be better if the transformer could propagate "fme_basename" value of the input feature when the user set "fme_basename" to "Group By".In addition, the transformer doesn't recognize attribute names which are set to the "Group By" parameter if the names contain Japanese characters and "Input is Ordered by Group" is set to "Yes". This also should be improved.
Validate the attribute values against a variety of specifications (within ranges, of proper types, etc)
The File Copy Writer (already in FME) can be used to move or copy files.I use this writer quite a lot.It can be used to ZIP files too, if the destination is a ZIP file.I would like to be able to UNZIP files using this writer (source is zipped file, destination is directory to store unzipped files).
Actually FME 2016 is not friendly to non-ascii characters. I encountered several cases where Japanese characters (within file/folder paths, attribute names etc.) causes unexpected behavior.The situation is worse than 2015. I'm afraid that more hidden problems exist yet.Similar issues probably occur in other non-ascii locales. I strongly hope thorough investigation and enhancement regarding FME i18n will be done.
***Note from Migration:*** Original Title was: Auto clear text when Test String textbox is focused (FME 2016's Regular Expression Editor) In FME2016, the regular expression editor is added, it is very convenient for test of regular expression .But I also found that It is inconvenient to use. By default,It display "Enter a string to test here..." in the test text box, but when you click the text box, these texts are not disappear automatically, so every time you need to manually clear. I suggest can be like a lot of Web password text box, Display only when the text box is not entered and not in focus. Or simply remove these tips, because the editor itself is not complicated interface.
The inspector is a great tool to view features and to view filtered features but it cannot save just the filtered features. Why not add this functionality?
Actually, FME doesn't have a PDF library with Python.Can you add a PDF library by default ?Thx
Currently, you need to specify a "hard-coded" AccessKeyId and SecretAccessKey for the SQSReceiver/Sender/Deleter/MessageCounter, or you can set it through a Public/Private Parameter.In the S3Downloader/Uploader/Deleter/ObjectLister, you can omit these values and get them through a file, Java system properties or environment variables. I think it would be nice if this behavior is consistent among these AWS transformers.
FME used to have the ability for the user to add transformers to the toolbar. I found this quite useful because I could just click on the icon for, say, AttributeCreator and not have to type it. If most users didn't use this functionality, perhaps it was because they didn't know that you could do it.It didn't matter if the icons were all the same because you could put your mouse over it and get the name from the tooltip. Plus if you use FME a lot you knew where each transformer was on the toolbar. Can we bring this functionality back?
The Hexagon Point Cloud format (.HPC) is a pretty closed format and not very much support for it. IT would be nice to have to have FME be able to convert it to a standard .LAS or .E57 format that other packages can use.
Ability to be able to write 3D Printer file formats - for example, STL file. Currently i have to take a COLLADA file into a 3rd party app like MeshLab to achieve this.
If you send two non-intersecting lines into the LineOnLineOverlayer or the Intersector, the attribute "_overlaps" is set to 1 for both features exiting the Line / Intersected port, even when they do not intersect. The same value of 1 is also set if the two line actually intersect.I suggest that non-intersecting lines get "_overlaps" set to 0 to make it easier to filter the results accordingly.
With the Joiner transformer there is not option to see the data that has not joined to something successfully. It would be nice to see which features that have been unsuccessful, so perhaps a rejected or unsuccessful or not joined port out of the transformer. Currently the only way of seeing whether features have not joined is buy looking at the feature counts either side of the joiner. Even then you do not know which one did not join.
I have a customer using an older version of FME.I want to know if a certain format is available for him.But I can not find a list of formats with the version of FME in which the format has been added to FME.Can this be added to the formats information or the Readers and Writers manual?
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.
