Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
If you write an FFS file with FME 2018, it's not readable by FME 2017. It would be nice if there was a parameter on the writer where you could specify compatibility with older versions
I would like to see that the ArcGIS Online writer supports the fme_db_operation attribute. Now you have to choose and have to add multiple writers if you want to execute e.g. update and insert operations. I would prefer steering this through an attribute.
I would like it very much if it would be possible to filter data in the 3D view in the Data Inspector, as can be done with the 2D view. Currently Filter is greyed out in the 3D view.
It would be great to be able to test a named connection within FME Server in the same way it is possible to do in FME Desktop.
Hello,please, is it possible to add typical combobox to PDFPageFormatter transformer parameters, for "Page Width" and "Page Height"? I miss quite a lot the offer to choose width and height according to attribute value.I miss combobox for parameters Page Width and Page Height like that:Thank You so much!Lubo
I work on Internet of Things projects. We have lots of sensors that provide data that needs to be timestamped with milisecond accuracy so that we can see which combination of sensors recognize events and objects. I want to do correlation between data at a milisecond accurracy. The issue is that I cannot directly convert the time information (milliseconds from epoc) to date with the DateFormatter, since the %s directive only takes integer values; http://docs.safe.com/fme/html/FME_Transformers/FME_Transformers.htm#Transformers/dateformatter.htm
***Note from Migration:*** Original Title was: Having timely updates to the ADAC scripts within FME will allow organisation to fully utilise the benefits of each ADAC version update.
Add a writer so you can move terrainmodels, houses, road, pipes from FME to this great game! Based on the Unity 3D engine! http://www.citiesskylines.com/ https://www.youtube.com/watch?v=9xj4ciP0Riw
When the user needs to sort huge number of features grouping by an attribute value, it could be performed more efficiently if the Sorter had the Group By and Parallel Processing Level parameters. In the expected Sorter, when the user has set an attribute to the Group By parameter but not set sort keys, it should work to just make the order of features by group. If it could be done efficiently in conjunction with parallel processing, the performance of a following transformer that has the "Input is Ordered by Group" parameter could also be improved. e.g. Aggregator.
In many cases, especially when integrating FME Server in custom applications it is neccessary to know if a given parameter is optional or not. For example to give the user visual feedback if a certain parameter may not be empty. This information exists in the workbench, but is not published through the REST Interface.
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.
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.
