Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Take a 2-point line and return the inverse Vincenty geographic (WGS84) distance between the end points.This is to eliminate distortion caused by any projection you might be using for points over a wide area.I know Vincenty doesn't resolve with near-antipodal points but I'll live with that, just tell people 'hey its roughly 20,000 km for this one'.
People often ask me if i have any posibility to read and display different formats - in most cases they only want to see the Data and have no suiting tool. I have the posibility thanks to fme. But my local authority can't provide fme licenses for every single coworker who just wants to take a look at different data. So often i read the data in and export it as pdf or some other format like shape. I could provide a workspace on FME Server that converts some formats to other formats, but that won't help at any case.Heres my Idea:FME Server should have the ability to offer end-users a lightweight interface to upload Data in different formats and feeds a simple web-mapping application with it. Kind of a browser-based Data Inspector with basic features like zoom, pan, measure, print.
Especially a "Dark" theme.
***Note from Migration:*** Original Title was: Enhance FME Server on Linux so PythonCaller scripts can use GDAL / OGR and associated libraries The PythonCaller transformer provides a powerful way of extending what can be done with FME, when there is no native transformer available. A key set of tools for working with geospatial data in Python are the GDAL libraries and Python bindings. However, at present PythonCaller transformers that use GDAL (or OGR, or various associated libraries) do not work in FME Server on Linux. This means that one of the main uses for the PythonCaller - to extend the capability of FME itself - breaks.ProblemMy scenario is that I am using a Python-based approach to calculating raster zonal statistics via an FME workflow. The FME processing creates or supplies the zone geometries and then the Python code loads the raster files directly from disk via the GDAL library, calculates the zonal statistics, and outputs them on FME features. This enables rapid calculation of zonal statistics on huge numbers (tens of thousands) of raster files, with FME helping to manage the results. This works very well in FME Desktop, but in Server on Linux it fails because the GDAL library in Python is not able to load the raster files. The issue can be demonstrated very simply. Running the following code in a Python interpreter on Windows, or on the system interpreter on the Linux machine, will return a number indicating how many formats GDAL can read: >>> from osgeo import gdal >>> print gdal.GetDriverCount() 207 The number will vary depending on what exactly is installed. However, running this code inside a PythonCaller or PythonCreator in a workbench published to FME Server on linux, outputs a value of 0, indicating that GDAL cannot read any data formats. I think this fails because FME has its own built-in copy of some parts of GDAL and this isn't meant to be used other than for FME itself, so it's probably been compiled without that stuff built in. However instead of removing the unnecessary symbols from the FME-supplied library, they're there but crippled. Because Python runs within the FME process, the Python code also gets presented with the FME copy of the GDAL library when it tries to load it, not the system one, and therefore can't read any GDAL data. Possible Solution I think there's at least two approaches that could be taken to fixing this:Customising the FME-internal version of GDAL a bit more so that the functions (symbols) it provides don't conflict with the original GDAL ones. So when the Python GDAL library tries to call the native GDAL functions, it gets the correct system-installed ones, and stuff that's internal to FME stays that way and doesn't "accidentally" get called by a user's code. I don't think that I as a user should be able to have my Python code accidentally call things that are supposed to be internal to the code of FME. (Note, the same issue I'm describing here used to also happen with the SQLite library, which also didn't work in Python code on Server, but that has now been fixed in recent versions of Server which no longer have an FME-specific version of that library. So change is possible here!)Increasing the separation of the Python environment that runs within a PythonCaller or PythonCreator. I don't know how or if this could be done. However since on linux FME uses the system Python interpreter, then I think it's reasonable to expect Python code that works at the command line, to also work when called via FME.
writing to elasticsearch
Currently, when exporting a Revit model to .RVZ file, the Revit "Mark" (Identity Data.Mark) parameter only gets exported for certain Revit family types, such as a door family. Generic Model families, however, does not export the "mark" parameter and therefore is not part of the translation to another source, which in our case, ESRI Shape Files.Being able to export the Mark parameter for all Revit types would be extremely helpful, especially here at the Denver International Airport where we work with big data.
I am analysing a series of our workspaces using the FMW reader and trying to ascertain which have templates. I have found the DEFLINE_TEMPLATE parameter in the 'workspace parameter' attribute and assumed that where this has a value there is a template, but I cannot find the location of the template file itself. If the reader does not pick this up it would be useful to add in future, thanks.
I am really happy with the new tunnel and junction functionality in 2016.1. I have been hiding a lot of lines in my workspaces already. So much tidier! However, I noticed that when I drag transformers around, they sometimes snap to the hidden lines, which can cause quite an unexpected mess.. :)As a temporary workaround, I have disabled the "Use Drag-and-Insert Transformers" option, but I really like this functionality. So maybe it's an idea to make hidden lines "unsnappable"?
Performing translation on Autocad DWGs and realized that there is no support for the viewport freeze in FME. The viewport freeze allows for a user to turn off certain layers in the viewport but keep them on in the model space.
It would be great if using the HTMLReportGenerator we could choose an option for Vertical table. It would be good for scenarios when I am using the group by option to create tables and I am creating a single table for each record like below. I always have one heading that contains a lot of text and it would just look better within a vertical table.Name:John Smith Location: StreetRef:123456Proposal:Insert your proposed changes into this section, this is free text and contains a lot of text!!!!!!!!!!!!!!!!Thanks
There are many API methods which don't accept 'unicode' instance as their string type arguments.e.g.1st argument (attribute name) of FMEFeature.setAttribute1st argument (message string) of FMELogFile.logMessageStringCurrently users who are working with Non-ASCII locale have to add codes to check the class of each string value and convert it to a 'string' instance if it was a 'unicode' instance, to avoid the UnicodeEncodeError.Hope every method will accept 'unicode' instances as string type arguments.
As help is now online, it would be great if Safe could show bugs and enhancements request against transformers. There is nothing worse than having a process not work, narrowing it down to a particular transformer and notify support, to be told that there is already a bug report in for it. Having the ability to see existing bugs against each transformer, would be useful at narrowing down issues quickly.
Could the Trimble JXL file reader be updated to read in the Features structure within the PointRecord element, exposing the Feature elements and their attributes contained within the Features? Currently it does not do this and it simply attaches the feature attributes to the PointRecord element.
EsriJSON Styler. Like KMLStyler etc. but for EsriJSON features. Adds a "symbol" property to the features based on: http://help.arcgis.com/en/arcgisserver/10.0/apis/rest/symbol.html
The choice to select our own source of mapping for the maps option of HTMLReportGenerator
I saw a question with the same title and a lot of good answers... I thought about why not just having a transformer for this.
By default FME will happily overwrite existing destination files but sometimes that's not what you want. In that case either terminating the process or halting and prompting for a new filename could save a lot of trouble.It could be a workspace parameter with 3 settings: always overwrite (the current behaviour)promptterminateI guess it'd be similar to a FileExistenceChecker with some additional processing, but wrapped up nicely.
Choose a column from the file used for the SchemaMapper to automatically expose all attributes created
It is painful when a process crash and you have to start it over again but you have to take input out of the list so it won't create them again
***Note from Migration:*** Original Title was: Use tree navigation for GML Feature Parts for reading GML with ignore schema mode It would be nice to have the tree navigation on the GML/WFS Reader Parameters for the GML Feature Parts parameter, when ignore schema is turned on.
From personal experience, it could potentially be useful to offer a transformer that can be used to solve for various mathematical functions (e.g. mathematical functions to degree 2, 3, 4, ..., to degree n).
Sometimes it is vary had to read the transformer help file & it’s even very painful when you did not understand nothing so along with help bouton if there is Video link it will help to understand what exactly the transformer does.
It would be nice to have a parameter type that can handle URLs and Files. Most Readers accept URLs and local Files for the input data set, but there is no user parameter that allows both.
There is zilion of settings in the generalizer, which is good, but on the other hand the typical problems such as generalizing the terrain contours or GPS track log data for sure have an optimum solution. For these typical cases a webinar would be appreciated which would make an overview of which algorithm is suitable for which particular case and what would be the good practice settings.
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.
