Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Add new alias for Terminator transform IllBeBack.
Quite commonly I read in a zipped fGDB and would like to suggest that the auto-recognition of this format be improved. FME (2017.1) recognises a zipped fGDB as being of format "EDIGéO". fGDB is surely a much more common format and defaulting to "Esri Geodatabase (File Geodb)" would probably help many of us.
I think it would be really helpful to be able to set default styling for user annotations in FME Workbench. This could be done via a new dialog within FME Options, or there could be an option to right-click on an annotation and "Set As Default Style". If you went with a dialog within FME Options, you could include checkbox options to "Auto-color annotations by enclosing bookmark color" as suggested by @FMELizard and to "Make Word Wrap as Default" as suggested by @dorgin.
When lines are snapped to a single Point or Areas are snapped to a line, then this dropped Features should be ouput in a "rejected" or "dropped" port.Now this Features can only be found in the logfile.
When working with lots of PATH readers I find it a little hard to know which is which sometimes. While I know I can add an Annotation I think it would be great to be able just to rename it.
I have a workspace in which I would like to overwrite an existing Excel spreadsheet if it exists - it might or it might not depending on other things. If I leave 'overwrite existing file' set to 'yes', the workspace will fail when it doesn't find an existing spreadsheet. This also happens with file geodatabases.Perhaps a setting of 'yes - if existing' could be added?
It would be useful to be able to reference mapbox styles from within the HTMLReportGenerator. This would enable a user-defined style/background map from MapBox to be used. See knowledge centre question https://knowledge.safe.com/questions/50354/htmlreportgenerator-and-mapbox.html
Improve mobile UIEasier to view logs (hard to scroll all the way down)Easier to enable/disable schedules
***Note from Migration:*** Original Title was: Add more support for seismic data and make the SEGY and P190 readers more flexible I think that there is a lot more which can be done with FME in this space. There are a lot of users in the Oil and Gas community who use FME. Support for seismic data formats in FME is pretty limited at present. As a user I would love to be able to quickly create workflows to pull out the Navigation from my SEGY and stick it into a GIS. I love the CAT reader and think that this is something which could be integrated into reading the EBCDIC header. The SEGY reader should also support reading 3D Seismic.
Recently have an example where an attribute for a feature in an Esri Geodatabase where the GDB could be read by FME 2014 SP3 but with FME 2015, 2016 and 2017 the Reader dropped features with no warning message. Opening the GDB in FME 2014 Data Inspector shows some unusual characters in an attribute value.Tried the File Geodb ArcObjects reader and it writes a useful warning into the log:2017-08-10 17:30:45| 1.5| 0.0|WARN |Unable to retrieve feature from table/feature class 'IC_POINT'. This feature, and any other feature from 'IC_POINT' that cannot be read, will be skipped. The error number from ArcObjects is: '-2147418113'. The error message from ArcObjects is: {Unexpected operation [IC_POINT]}Requesting better messages/error detection when reading the GDB with the File Geodb API reader similar to the File Geodb ArcObjects or stop reading the file. It would be then possible to manage rather than losing data.
***Note from Migration:*** Original Title was: In the user attributes section of the excel-writer add the option to specify a hyperlink type. In the user attributes section of the excel-writer add the option to specify a hyperlink type.
Have the ability to show who uploaded (owner) of the workspace within a repository (much like how you can now see who owns each repository).
There already is a getAttributeType() method on the FMEFeature class, but it would also be nice to be able to set (=convert!) it, if this is feasible. This is useful if we want to enforce/maintain a certain character encoding (as discussed here), or if we want to convert an integer to a boolean, a numeric string to a real etc. etc.The method could look like this:setAttributeType(attrName, attrType, [attrEncoding])Sets/converts an attribute into another type. Attribute type must be one of FME_ATTR_UNDEFINED, FME_ATTR_BOOLEAN, FME_ATTR_INT8, FME_ATTR_UINT8, FME_ATTR_INT16, FME_ATTR_UINT16, FME_ATTR_INT32, FME_ATTR_UINT32, FME_ATTR_REAL32, FME_ATTR_REAL64, FME_ATTR_REAL80, FME_ATTR_STRING, FME_ATTR_ENCODED_STRING, FME_ATTR_INT64, FME_ATTR_UINT64.For FME_ATTR_ENCODED_STRING only, the user can specify a character encoding (e.g. 'iso-8895-1'). Otherwise, the encoding argument is ignored.Parameters: attrName (string)attrType (int)attrEncoding (string, optional) - defaults to 'utf-8' if attrType is FME_ATTR_ENCODED_STRING and attrEncoding is not set Returns: NoneRaises: FMEException - An exception is raised if an error occurred, e.g. when the conversion failed.
Currently, importing attribute data from CSV results in all attribute fields being of type 'string'. The GeoCSV-specs (http://giswiki.hsr.ch/GeoCSV) describes and ogr2ogr in version 2 and newer implements the use of a .csvt-file that denominates the data type of a column. To quote from the gdal docs: Limited type recognition can be done for Integer, Real, String, Date (YYYY-MM-DD), Time (HH:MM:SS+nn), DateTime (YYYY-MM-DD HH:MM:SS+nn) columns through a descriptive file with the same name as the CSV file, but a .csvt extension. This mechanism would make the possibility to import data in CSV-format much more useful.
I think it could be useful to have either a notification triggered when an FME Server or Cloud (re)starts or to be able to set that in a schedule.Especially for FME Cloud instances that are not on 24/7 or on a regular schedule this would make it possible to make sure certain workspaces do get run.
***Note from Migration:*** Original Title was: It would be ideal if there was a field within Arithmetic editor that would display a snap shot of the results of the expression you were building.
To easily dump all readers to FFS, add "Connect Recorder" - similar to "Connect Inspector" or "Connect Logger" - and name the FFS files with the feature type names
The FME DotNet SDK provides a library to develop FME transformers for the FME platform using .NET code.With this SDK you can easily develop any .NET assembly in order to implement your own specific funcionality. These assemblies can be integrated in FME Workbench workflows as usual, and by using any combination of them.If you need to use the Microsoft .NET platform, or develop fast FME Transformers (The .NET assemblies run much faster than equivalent python-based FME Transformers), this is your SDK!This software was funded by EEA-EIONET and Tracasa and shared with MIT license.See news in Linkedin
It would be nice to send a feature into a transformer that would tell you what coordinates systems are valid for that point. ie. State plane North, UTM 15, etc ... and possibly be able to do a reproject on that.
***Note from Migration:*** Original Title was: It is possible to read viewports from Autocad paperspace by selecting their names on the reader.
In FME 2017.1 Build 17539, the Salesforce format (Reader/Writer) only allows username / password or token authentication. With the availability of the Salesforce Web Connection, it would be great to allow this to be used as the preferred auth method.
It would be really useful if the SQL Server Reader formats had the same "SQL Statement to Execute" options that other formats like Oracle have:
The FME training material comes with a number of sample workspaces with hardcoded paths. If you place the .zip file in C: and unzip it there all the paths in those workspaces will be correct. However, depending on where you are doing a training course you may not have access to the C: drive due to IT policies or it simpy not existing (Mac and Linux). That means the workspaces won't work right away, any paths in there have to be fixed first. This is a bit annoying and it can be confusing for novice users.So with that in mind I have uploaded a workspace to the Hub to fix this. When placed in the FMEData2017 folder and run from there it will look for all the other .fmw files and fix the paths in there.I would like to suggest this (or a workspace with similar purpose) to be added to the standard training material.(Anybody who wants to use this workspace for their training feel free to do so but do note that I haven't tested it against all workspaces in the training material)
It's possible to read almost every property of a feature from a dwg/dxf, and from these to reconstruct a property filter, but FME doesn't seem to be able to read in group filters. These can also be extremely useful and preserving a nested filtering hierarchy for complex models would be extremely useful.
Over at https://knowledge.safe.com/questions/49325/is-there-a-way-to-trick-or-configure-the-affinewar.html , @whit requested the ability for the AffineWarper to have an option that could be set to indicate that the Control Vectors are coming in first. If set, then once the first non-control vector input arrived, we could compute the affine transformation and send all non-control-vectors on their way, warped as can be. The RubberSheeter would presumably get the same treatment. Vote early. Vote often.
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.
