Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Currently is no option to assign a data type of "DATE" to an attribute. Having this option would eliminate having to use another transformer to manipulate a date field.
The coordinate system ISN2004 / Lambert 2004 (EPSG:5325, https://epsg.io/5325) has replaced the old ISN93 / Lambert 1993 (which FME has support for). Please add EPSG:5325 to the lists of coordinate systems.
The idea is to be able to view the datasets or features we want to use and drag those we need as writers into the workbench. This would help choose visually the feature types (CAD being the ultimate example.)
Currently there appears to not be a way to relate an annotation to the transformer or reader to which it is attached. This would really help in creating documentation of FME work spaces, so one could get out what the source of the data in the reader is and the ports, and then also a annotation that describes why the workspace is reading that source, that kind of stuff.
Miss Vector points out on page 356 of the FME training handbook that you can't select one transformer, right click, and choose Create Bookmark. Well, why not? You can do it for multiple transformers, and you can select one transformer and choose the Insert Bookmark button on the toolbar... why not do it on right-click for just one transformer?
That way we’d get a connection to piles of web services instantly. Goal is that FME triggers the zap and gets JSON back.
***Note from Migration:*** Original Title was: Read files on the fly (without complete download) from web file systems (e.g. S3) It would be great if FME began reading in files as they were downloaded rather than waiting for the entire file to download and then reading them. Especially for big files on S3.
I would love the ability to read OSM data in pbf rather than xml format http://wiki.openstreetmap.org/wiki/PBF_Format
I'd like to be able to write glTF 2.0. Maybe others would too? How might you want to use it?
I use scripted parameters from a configuration-file, similar to explained in many blog-posts.Te location of the script is passed through a public parameter of the type 'file(existing)'.This parameter sometimes contains an absolute path, when the config-file is stored somewhere on the filesystem, but sometimes part of it is a FME parameter such as $(FME_MF_DIR) when the config-file is stored close to the workspace. Also, on server, I deliberately use a server-parameter such as $(FME_SHAREDRESOURCE_DATA).To cope with this, I have had to hack a quite nasty looking bit of pythonimport fme import ConfigParser import os import re fmeParam = re.compile("A$(FME_[A-Z]+_[A-Z]+)") fmeParamName = re.compile("FME_[A-Z]+_[A-Z]+") def findAbsolutePath(fileParamName): paramValue = fme.macroValues[fileParamName] fmeParamList = fmeParam.findall(paramValue) if fmeParamList != []: fmeParamKey = fmeParamName.findall(fmeParamList[0])[0] fmeBasePath = fme.macroValues[fmeParamKey] relFilePath = fmeParam.split(paramValue)[1] absFilePath = os.path.join(fmeBasePath,relFilePath) else: absFilePath = paramValue return absFilePath filePath = findAbsolutePath("conffile") conf = ConfigParser.ConfigParser() conf.optionxform = lambda option: option conf.read(filePath) return conf.getint("Parameters","MyBeautifulNumber") testing for the presence of FME-parameters, filtering out the key I need to get them from macroValues, and glueing it all together for an absolute path where I can find my config-file.Could there be a function like fme.getAbsolutePath('[key_of_filepath-parameter]')?Kind regards,Martin
Initial code in those 2 transformers needs to be aligned to match PEP8, e.g.- blank lines between functions in a class- whitespace between keywords in function definitions- newline at the end of PythonCaller class definition
Currently the RasterBandMinMaxExtractor is unaffected by raster band and palette selection, however for large rasters this can be a very resource intensive process, and if I'm only interested in one band out of a hundred band image, this adds a factor of 20 to the processing time needleslly.
Issues are being reported about connecting to the FME Store through either a firewall, a proxy, or both.If you experience any such issues - in FME2016 or newer - please upvote this idea and leave a comment below to describe your situation.You should also contact the Safe Software support team to see if they already have a solution for your particular issue.
***Note from Migration:*** Original Title was: OBJ - Add parameter feature handler - to control quantity of flat surfaces used to represent curve surfaces We use FME to read DWG files and write OBJ files. When reading curved surfaces from the DWG mode, the OBJ writer decides how many flat facets will be used to represent that curved surface. We need more control over this to provide better fidelity for curved surfaces, cylinders and cones.
It was be really awesome if any metadata about my FME Server Backup (.fsconfig) would be displayed on the Restore page, after I've selected it, to confirm that I want to backup.Currently, the only "metadata" I can observe is the filename – which can be changed really easily!I'd like to see... - Date Backup Created- Hostname of FME Server- User that Created- Number / Count of Items (e.g. Workspaces, Connections, Publications, etc)
It would be nice to be able to select an existing parameter as a target dataset for Readers and Writers. Often I have to update the same dataset as I am reading. It would be convenient if I can select the existing dataset parameter from the Reader directly when I am adding the Writer or when I am adding the same dataset as a Reader for whatever purpose.
If there is not a spell checker transformer in FME (I couldn't find one), could you please create one?Have a large, free-form entry string field and want to flag words that don't match an English dictionary. Think of this as an ongoing tester w/ QC .CSV output (examples in attached image), rather than a "fail over point" in an ongoing automation.
That would be easier if we could sort attributes (like on a writer) inside an AttributeValueMapper
We can configure the S3Watch publisher to poll every x minutes/hours/etc., but we cannot specify at what time of day the poll occurs. It'd be great to set up the publisher to poll at specific times e.g. noon and midnight.
Currently the SQLExecutor acts in a 'blocky' or 'groupwise' mode, with features output all at once. This can cause problems, for example, in looping transformers. Replacements for the SQLExecutor in this situation (database readers or FeatureReader) are also 'blocky'. Allowing the SQLExecutor to output a feature immediately would provide more creative options for custom transformers.
Hi,It would be very handy if ChartGenerator supported datetime values as input for X axe for example.Using FME 2017.1 32-bit, when I try to use datetime values, ChartGenerator throws a warning saying that not numeric data received.Thanks,
Ok, these 2 articles explain nicely how FME chooses from the available ArcGIS products on the system and how to "force" which license level is used: https://knowledge.safe.com/questions/36948/can-i-specify-whether-fme-desktop-uses-my-arcgis-d.htmlhttps://knowledge.safe.com/articles/31613/setting-different-license-levels-for-arcgis-and-fm.html My proposal is to introduce FME specific environment variables (or FME options Settings) to allow the user exactly what to use at FME runtime, e.g.: FME_ARCGIS_PRODUCT_USE=Engine|Server|DesktopFME_ARCGIS_LEVEL_USE=Basic|Standard|Advanced This should override the internal FME logic and of course fail, if the user chooses a product which is not installed, licensed or if the combination violates either Esri or Safe usage agreements.
Wouldn't it be awesome to have a quick keyboard shortcut to publish to server?
This morning a colleague indicated to me that it would be useful if we could indicate how long a job is likely to run for on FME Server. Clearly there are a lot of moving parts including source data sizes, transformers used (blocking vs feature), number of transformers, readers/writers etc. going on which could make it hard to auto-forecast, but I wanted to throw the idea out there.Of course a simpler solution is a private parameter that the author of the workspace supplies, to give an indication once they have run the workspace enough times to know how long it should take.If this was done it could appear on the workspace summary window after submission, and/or be emailed to the user who wanted to know.
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.
