Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
In older FME Server versions there was an advanced section in the Run Workspace dialog that showed a little code sample for the web form that you could copy and implement in your own web page. Please bring that back!
When reading a CSV file with more than one line defining the attribute names, it would be useful to be able to indicate this in the CSV reader in FME. In addition, a mode of concatenating both in order to create one "field names line" would be useful. For example:idxyidxyinputinputinputoutputoutputoutput
The ability to create a SSL connection to a Google Cloud SQL database. Currently this not an option, you are not able to add/associate the three required files. Of course once we can do this on the desktop it would be great to be able to use this connection information on FME Cloud.A non-ssl connection works.Client KeyClient CertificateAuthority Certificate
It might be useful if FME could upload, list, download and delete files with Azure Blob Storage.Note: there are custom transformers for this available in the FME Hub.It might be good if this support was offered natively in FME, like other remote file systems - i.e Connector transformers and select file from web for readers.
Recently I worked with FTP account which by default connects to /username folder on FTP site, whereas the filename I needed to download was /customfolder/filename. When I put the direct link like ftp://ftp.example.com/customfolder/filename, FTPCaller couldn't download it - it looked for a customfolder inside /username folder. After a while I realized that desired filename could be downloaded by doubling the slash symbol after FTP site name, like this ftp://ftp.example.com//customfolder/filename.
The PhotoCoordinateExtractor on the FME hub works well, but wouldn't it be better if:The JPEG reader automatically converted and exposed the lat/long to decimal degreesYou could expose an optional feature type containing point features for the photo locationsFormats other than JPEG (i.e. TIFF) were also supportedFor the second one, I'm thinking it would maybe work as an option on the initial reader setup, where you could choose whether to bring in the photo, the points, or both. I guess they would have to carry a common identifier so you could join them back together if you needed to...
My understanding is that publishing vector tiles is coming very soon. Awesome--the world needs more beautiful vector maps emanating from FME.But this world is also a Fallen World, and end users want PDFs. PDFs they can print in large format paper sizes and still have crisp, beautiful vectors.I've been told by Twitter that Mapnik *ingests* vector tiles that can be emitted as a PDF.I dream of a world of seamless transition between the world we want--vector tiles--and the world as it is--PDFs.
The CommonSegmentFinder would benefit from the following improvements:Candidates Only Mode (like the neighborFinder)Attributes that Must Differ parameter (matcher, spatialRelator)List of features that share a common segment(neighborFinder, matcher, spatialRelator)CommonID (matcher match_id)
When using WorkspaceRunner transformers and passing parameters from the main workbench, we need a way to step into the workspace specified by the runner when using the debugger. Similar to other debuggers that step into or over a subroutine.
***Note from Migration:*** Original Title was: @round() expression evaluator function should have an argument to round to a specific number of decimals Currently the @round function takes one argument, the value to round, and rounds it to the nearest integer. It would be nice is there was an optional second argument to specify the number of decimal places to round to (like AttributeRounder transformer), if the second argument is not supplied, then it should round to the nearest integer.
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)
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.
