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 would like the FME Server Job view to have a better design, making it more visually pleasing and more space efficient. Necessary improvements to the FME Server Jobs page would include:Decrease font and element sizesDefault column sizes need re-thinking to prevent uncessesary line wrapsAuto refresh: Button to activate/deativate automatic refresh and field to set refresh intervalAllow filtering based on any column, including StatusExample showing how much space is lost because of default element sizing, column widths and font sizes. Regular 10 point Consolas text shown next to it for scale. In this example one single job takes the vertical space of 5 lines of regular text:
In FME Server 2017 there doesn't seem to be a way to have the user create a new password if they forgot the old one (they can change it but they have to be logged in to do that). I would like to see an option for a user to change their password themself without having to contact an admin (right now if you're running an FME Cloud and you forget the superuser password you've essentially locked yourself out...)
***Note from Migration:*** Original Title was: Jobs page: when viewing a individual job - allow for quick navigation between next and previous jobs When I'm viewing a job, I want to be able to skip to the next one or the previous one very quickly.
1. Get "File and Directory reader" faster on NETWORK DRIVES 2. Get "File and Directory reader" faster on LOCAL DISKS
FME 2015 and I see 2016 comes with Python 2.7.Upgrading to Python 3.x would allow the use of the improvements those versions provide, including native UniCode Support (an extension of takashi's Idea here: https://knowledge.safe.com/content/idea/19381/pyth...)
Hello,Would it be possible to implement the possibility of vertical transformation for raster? For example: the reprojector transformer would handle elevation raster by taking the single band array as vertical information (Z value) and transform the elevation stored inside to a different datum.For now on a very slow workaround is possible but very inefficient (raster -> pointcloud -> reprojector -> NumericRasterizer)Thanks!
juste like the SQLExecutor transformer have.executor.pngupdater.pngjoiner.png
Please add a tolerance parameter to the alignment snapping resample method of the RasterMosaicker. This would be similar in functionality to the new raster tolerance parameter in the Reprojector.
Is it possible to make the 'FeatureReader' remember the 'Parameters...' 'Schemas for Table Listing'?Steps I usualy follow:Insert a FeatureReader -> Select Format Postgis -> Pick ConnectionParameters... -> Schemas for table listing = mySchema -> OKFeature Types to Read -> [...] Select Items = mySchema.myTable -> OKOK on the FeatureReader Parameters.Then I think. Let's narrow the objects down to what I realy need.Edit FeatureReader Parameters:WHERE Clause: -> [...] Unfold Database Tables -> (oeps only public.raster_columns) CancelParameters... -> Schemas for table listing = mySchema -> OKWHERE Clause: -> [...] Unfold Database Tables -> Unfold mySchema.myTable -> Pick myColumnmyColumn = atValue(myColumn) -> OKAnd every time I need another Table from my Scheme or when I want to edit the Where clause I need to go back to set the 'Schemas for table listing'.I would like it to remember this setting so I only have to change it when I need another set of Tables.
When working with Oracle Locator Spatial there are a lot of cases that require an alias on a table. This works really well in the "select" statement of the Oracle reader but it limits the update of column names unless the select clause is updated as well. It would be an awesome enhancement to add in an alias option to the where. The table name is not allowed unless you add the where as an alias.i.e. in the where clause allowa.shape.sdo_gtype = 4402
Hello Safe,PROJ.5 has just been released, and it seems to be a great improvement to PROJ.4.It looks like all manner of "difficult" projection will be supported (with polynomials and Helmert), so is Safe planning to take advantage of this, and implement PROJ.5 support e.g. in the next major release ?I know for a fact, that Danish legacy projections will be implemented shortly (if not already), with full accuracy, and henceforth will be maintained here. This enables centimeter accuracy in reprojections.Cheers
***Note from Migration:*** Original Title was: FeatureWriter-transformer should optionally log the written Features to the variable "FME_TotalFeaturesWritten" If i use the FeatureWriter-transformer, the written Features are only count in a seperate log.I'd prefer, that there may be an checkbox to enable writing the count of written features to the variable 'FME_TotalFeaturesWritten' as well.In my case it is important to get the whole number of written features in the python-shutdownscript. In ideal case in a direct way.I believe that it would be the easiest way with such a checkbox.
Currently when you add a new Reader/Writer you need to hard code the connection parameters, the process then uses that information to connect to the database allowing you to then specify the Feature Types to be included etc.I would love to be able to specify scripted parameters when defining new readers / writers. Seems silly that i need to first hard code them and then replace the values later with scripted versions of those parameters. This becomes a huge issue when I due to incompatibilities between reader/writers versions that are embedded in the FMW, requiring me to re-create them. Instead of being able to just link the new reader writers to my existing scripted parameters I have first hard code them, and then later replace those values with scripted versions.
Create simple MS Word documents. Features specify headings, text, pictures, tables which are strung together to make a document.
Could the Attribute & CoordinateRounders possibly offer the chance to round to a number of significant digits? I'm currently doing it by calculating the length of the number before the decimal, but it would be nice to have this baked in.
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)
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.
