Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
***Note from Migration:*** Original Title was: Convert layer_styles table to FME style attributes when reading data from PostGIS, Geopackage and SpatialLite It would be nice if FME could read the layer_styles table from OS datasources like PostGIS, Geopackage and SpatialLite. With QGIS it is possilble to set (default) styles to tables in these formats. Styles are stored in layer_styles table as SLD and QML.
Update the FME AR android app to include compass and attribution (view or edit).
We have a need to create geoJSON files in the newline delimited format (ndJSON). It's possible using the GDAL driver https://gdal.org/drivers/vector/geojsonseq.html but I can't find any reference to that capability in FME. Is it possible? Cheers
***Note from Migration:*** Original Title was: Extend the HttpCaller with an option to create a secure connection with a certificate Please add an option to enable HttpCaller to create a secure SSL connection using a custom X.509 certificate.Preferably enable providing the certificate in multiple format formats, e.g. both certificate/key separated formats and the joined format of pkcs12.I can provide sample code that works in a PythonCaller (Python 3.7+).
It would be nice to have stencils for Visio for FME Desktop, FME Server, FME Cloud and Workbench for use in Visio diagrams.
Add a setting to allow the job to be retried on failure x number of times. We have some jobs that fail due to timeout, and running the job a second time doesn't experience the same timeout issue. It would be nice to set that on the schedule. I am assuming the future automation section of server could be able to address this type of request as well.Merged Ideas:Add Retry Times option to Schedules in FME Server by takashi on March 9, 2018Some kind of scheduled jobs could fail because of an external reason. e.g. a case where an external server which manages resources for the job is busy at the moment when FME Server access the resources.In order to be able to recover such a failure as soon as possible, it might be useful if the schedule setting would have an option to set the number of retries and their time interval in the case where the job failed.
Currently, the Revit native reader is fairly limited in regards to the parameters accessibility from the model. and it's missing the basics (ex.: area, length, etc.). It would be great to be able to access all parameters of all elements (objects, views, sheet, etc.) in order to be able to use it for quality controls, quantification, etc.. This seems to be possible by creating schedules in Revit in the first place but highly unreliable because schedules can be renamed.Also, attributes' naming vary from the native naming system.
Removes elements from a list which apply's to a condition. The ListElementFilter is a custom transformer with simular functionality but may be improved as standard transformer. E.g. remove element with id {_list_index}, output removed elements.Keep the Negate option as in ListElementFilter!
It would be really good if FME's GeometryValidator could validate composite solids.Currently it does not detect disjont or intersecting members. Here is what FME should be able to validate: http://en.wiki.quality.sig3d.org/index.php/Modeling_Guide_for_3D_Objects_-_Part_1:_Basics_(Rules_for_Validating_GML_Geometries_in_CityGML)#gml:CompositeSolidFor 3D validation workflow this is a critical test which currently can not easily be performed.
It may not be obvious if a TIFF/GeoTIFF a classic TIFF file or a BigTIFF file. It would be handy if the TIFF Reader and the GeoTIFF Reader could provide this information. Maybe the format attributes tiff_type and geotiff_type can be used, or add another attribute, like tiff_is_bigtiff.About BigTIFF files: https://en.wikipedia.org/wiki/TIFF#BigTIFFhttp://bigtiff.org/
It would be great if FME Workstation could support Powershell (Open Source runs on WIndows and Linux/Max) to extend itself similar to how Python is used to extend FME's capabilities.
Featurewriter truncating a key column should issue a error.When featurewriter is writing to ie Oracle, the columns are truncated to the length spesified of the featurewriter format, before the insert is done in the database.If you update features, you specify a key column for the update. If the featurewriter is truncating the data to match the feature definition, then the data entering the database is not what you feed into the featurewriter. This is difficult to detect and cause ie deletes and updates not to happen because the key is altered, and no match in database is found.So when data entering the featurewriter that exceed the length in the format definition, is a key, then a warning or error should be issued. Or, if the column is a key, it should give an error, or if not a key, it should give you a warning.
I would like to be able to expose attributes based on a list element. For instance, when extracting attributes and values from the "kml_description" attribute, the attributes are not exposed but exist in a list. Rather than manually typing the attributes to expose, I'd like to be able to reference list element 0 as the attribute name "td{0}".
Allow parameters to be used in the attributes to expose field in following transformers(Just to name the ones i use):RCallerPythonCallerAttribute ExposerSQL CreatorXMLFrafmenterXMLFlattenerXMLFeatureMapperJavaScriptCallerTclCaller
Rather than reading exif data from a specific image file format e.g. jpeg could a universal exif data reader be developed similar in functionality to the ExifTool by Phil Harvey. With the ExifTool you can point it at a directory, single file or a variety of file formats (supports approx. 186 formats) and it returns a table of image metadata. It works really well and I've created a FME custom transformer that makes a system call to the tool (https://hub.safe.com/transformers/exifreader). Other FME users might find this tool useful and it would be great as it's own reader.https://www.sno.phy.queensu.ca/~phil/exiftool/
If using Populate From SQL Query within the SQLExecutor or SQLTransformer the published parameters should be requested if the sql query references them. Or it should use the default values.
Would be nice to have a transformer for writing errors out within the Workbench, but also on the server side of writing logs to Seq.https://datalust.co/seq
Currently, a custom transformer can have numerous Inputs, but when the user is setting a parameter value with attribute assignment permitted (or of the "Attribute Name" type), all attributes from all inputs are listed. This makes it difficult to use any type of dynamic merger/joiner inside the transformer, and significantly limits the user's ability to control how the transformer operates on different data. It can also lead to issues when both datasets have an attribute by the same name... or when they don't! It would be ideal if, instead of "Default" and "Off" for "Attribute Assignment," we could select a specific input port and only that input's exposed attributes would be listed.
FME Cloud already has the ability to attach a Static I.P and open and close security ports which is fantastic functionality. With the addition of FME Server APPs having the ability add a new domain to our account would be really nice. For this we would need to be able to add a new certificate to the server. I would really love to have something like fme.<outcompany>.com/<myApp>where fme.<outcompany>.com is the fme cloud host?
At present, Microsoft Azure hosted virtual servers running FME Server do not read Azure hosted share paths when redirecting the FME Server System Share path
It would be great this functionality (import cached attributes) in the JSONFlattener and similar transformers:
Hi,There should be an transformer for scaling or evaluating measure values, The "MeasureExpressionEvaluator"If you (like me) have a line with measures in metres but them in kilometres, I need factor 0.001 to the existing measures.Currently the workaround is to extract to measure list, multiply each list element with factor 0.001, then a MeasureSetter to re-insert
Currently, Fme server job log is scattered, very difficult to trace thru. when we trace thru some transformer names, it jumps to another transformer's log or some other info is printed over there.(not like fme desktop log, fme desktop's log is very sequenced one compare to server's log) So We need to work on arranging fme server job log, so that user can trace / troubleshoot his error very easily.
***Note from Migration:*** Original Title was: Alternative URL field for Azure Blob Storage (and perhaps some more cloud-services) At the moment, the Azure Storage Connector is permanently fixed to the default url suffix 'blob.core.windows.net'. So is the Microsoft Azure Storage Webconnector-template.To me the usability would greatly improve when I would be able to enter an alternative URL.Please add a URL-override field to these functionalities.I currently work for a client which uses their own ip-adresses/subnet to access their Azure services, as part of security measures. So from the standpoint of FME Server, there is nothing interesting at blob.core.windows.net, but at some company-wide DNS-entry.There is nothing I can do about it, but override the Microsoft-URL to the IP-address locally in the hosts-file. Overriding Microsoft URL's is tricky and from a management perspective it does not feel the way to go.I can imagine more services / cloud infrastructure will have the same local subnet-treatment at companies, so perhaps the same can be true at companies for e.g. ArcGIS Online or the like.Kind Regards,Martin
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.
