Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
The ability to connect to the Azurite emulator for the Azure Storage. This would allow for users to use the local emulator to development and testing purposes.
Currently FME can read 12dxml file format (.12dxml), but cannot directly read the zipped version of this file (.12dxmlz).This is similar to the difference between a Google Earth KML file and a KMZ file. A current work around is the routine can have a user parameter for file name, it starts with a creator, uses the "ZipExtractorAnyExtension" from FME hub to extract the file, then the file path can be used in a feature reader with the format set to 12dxml. There are two issues with the workaround - it requires a user parameter to be setup within the routine, and it requires unzipping the file contents to a folder prior to being usable in the routine. 12dxml files can be large compared to 12dxmlz (7mb vs 206kb) so file size is significant, especially when 12dxmlz files get into 100mb's+.That is why a dedicated 12dxmlz reader would be great.
The SurfaceFootprintReplacer is an excellent tool, it produces nice clean results and is a nice clean result especially when compared to the 2DForcer. But it would be really nice to have the option to keep the holes instead of producing more of a dissolved result.
Python support for point clouds.
In the AEC industry the use of RTEXT in AutoCAD is widely used to print information on the drawings. You can read more about the command and entity here: https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2021/ENU/AutoCAD-Core/files/GUID-28585C1C-65B8-41E0-90A3-7C043123EF7A-htm.htmlThe RTEXT command in AutoCAD creates a RTEXT entitiy that can:Show the content in a external txt fileShow the file name and path to the current DWG-fileShow the current date and timeShow the list of the external references (xrefs) linked in the current DWG-fileRight now, FME doesn't support the RTEXT entities. The "Autodesk AutoCAD DWG/DXF" reader just inform that the AutoCAD Reader: Entity type of 'RText' found, but not supported. Skipping entityThe "Autodesk Autodesk AutoCAD RealDWG DWG/DXF" reader reads the RTEXT entities as proxy entities but with no attribute information that these entities are RTEXT entities. (if you have the parameter "Read Proxy Entity Graphics" turned on you get a bounding box and two crossing lines as geometries for each RTEXT entity)As FME is widely used to make the quality control for these DWG-files we really need support for reading RTEXT entities.
There are ways to determine if a job is being run on FME Desktop or FME Server, however, many of them simple, however, they tend to feel hacky and are not always obvious. It would be great if there was an FME specific variable (one of these) that we can use to distinguish between FME Server and FME desktop. There are a lot of reasons why you might want to have this kind of parameter available. Perhaps on FME desktop you want to use a configured emailer transformer to send and email but on FME Server you have the workspace configured to send out on success and dont need/want the emailer. Perhaps on FME Server you want the job to trigger an FMEServerJobSubmitter to kick of the next part of a worksapce chain, but on Desktop you don't - or instead want to route it to a WorkspaceRunner.Perhaps on Desktop you want data to be read from one database and on server from another
It would be nice if we could apply varying 3d affine transformation and not just 2d. Like the 3DAffiner but with parameters from a set of vectors, if possible with rubbersheeting approach.
You can set a default job queue for each repository in FME-Server.Before version v2021 there was a choice list in every row of the repository listing to manage that.This was removed for some reason with v2021. Now you need to change this setting by selecting a repository and use the "edit" button.Downside of this solution is: you have no overview.I suggest to add (at least) a read-only column "Job Queue" to the repository listing.
It seems that XYZ Tiles cannot be read by FME Desktop or be added as a background to the FME Data Inspector. URL example of such service: https://tile.openstreetmap.org/{z}/{x}/{y}.pngThe url works fine in QGIS: Thanks in advance!Olivier
With a workspace that includes many transformers, the ability to remember the map's current zoom and centre coordinates.The current behaviour is unpredictable. Clicking a magnifying glass displays the map and the current selection. Clicking on a different magnifying glass in the same transformer moves the map to a new location. The user is forced to pan and zoom back to the area of interest.The desire is to see the current status of any geometry at any point in the workspace.Background info via: https://community.safe.com/s/question/0D54Q00009q8A6dSAE/how-do-i-lock-the-bounding-box-of-the-graphics-view
For christmas next year I want a PublishWorkspace transformer. I think this would be really neat feature.I do believe this would make it smooth to CI/CD gitOps deployment.
Beginning in Tableau version v10.5 (January 2018), extracts use the .hyper format instead of the .tde format. Extracts in the .hyper format take advantage of an improved data engine, which supports the same fast analytical and query performance as the data engine before it, but for even larger extracts.Suggest creating a writer for Tableau's new extract file format ".hyper".
I am working on a support case where a client is trying to convert a mapinfo TAB file to a shapefile (easy enough) but wishes to also retain the symbology information. It appears that the functionality to create a Esri .lyr file to pair with a shapefile/feature class does not currently exist. A "EsriStyler" transformer/Layer File writer would be an excellent addition.
Apache Ignite is a distributed database management system for high-performance computing with in-memory speed. Posting this idea to gauge interest in the development of a formal format. Note: FME can likely connect to this database already via the JDBC Reader/Writer as Ignite has a driver that you can download here: https://ignite.apache.org/docs/latest/SQL/JDBC/jdbc-driverFME's JDBC Reader/Writer documentation: https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_ReadersWriters/jdbc/jdbc.htm
Because the default CRC-32 algorithm occasionally returns duplicates I use MD5. I noticed that MD5 does not uses geometry.
When using two CRCCalculators, one with CRC-32 and a second one with MD5 algorithm the first CRCCalculator uses also MD5 for the calculation of the second feature.As a work-around a FeatureHolder in between solves the problem
Hi,I really like the FeatureWriter Transformer but I think there are two important features that are currently missing:Update the feature types (as it is possible for normal writers)Allow to expand the attribute list of the feature types to check the attribute mappingKind regards,Dennis
If I want to chain several AttributeFilters together to drill down, shouldn't it filter out attributes in the output so that I can only select from the previously filtered attributes? Instead when importing a second AttributeFilter, it gives me everything again. To me, that's a bug, but maybe you intend to have access to everything? What about having a "Local" setting to only show attributes not filtered? Otherwise you have to pick through the import of attributes again. Thanks!
A job submit by the FMEServerJobSubmitter will never post to a topic on success or failure, even if it was registered with it at publishing time. Nor is there a way to set a topic to post to within the FMEServerJobSubmitter. It would be great to be able to chain and control jobs with the FMEServerJobSubmitter, and still make use of the power of FME Server notifications/automations.
Currently it is possible to set a network based resource connection on FME Server with a name using forbidden characters for an equivalent user parameter in FME Desktop. For example, you can set a resource connection with the following name (not the display name), 05-700-FMESERVER, which will give $(05-700-FMESERVER) when browsing it for a folder connection in a workspace on FME Server. You can use this key to call the connection. However, setting a user parameter in FME Desktop is impossible with the name 05-700-FMESERVER... Which is bothering when you want to test your workbench locally before to publish it. Harmonizing the naming convention and constraints would be really great.
Hello,Can you add the possibility to read .SBET file in FME ?PDAL can open SBET (https://pdal.io/en/stable/stages/readers.sbet.html)The SBET format is use used for exchange data from inertial measurement units (IMUs). This format is an almost universal format for describing trajectory of IMU system. SBET mean Smothed Best Estimate of Trajectory. Generally it's output from Applanix product but can be read easily by free viewer/converter.The file is mainly composed of text like, each line is new record who descibe position, time and attitude of the IMU.Regards
***Note from Migration:*** Original Title was: HTTPCaller transformer - adjustable Query String Parameter & Multipart Upload grids/tables Parameters for some Rest API can be a few (maybe 4 or more) and it would be nice to be able to adjust the grids to see more rows. Looks like it's locked to two right now but you can scroll up or down.
It might be interesting if FME could support Full Motion Video. There are a number of ways that FME could be involved, such as: clip by time, clip by location, sample / extract frames as rasters, combine, split, resize, georeference, extract georeferencing, embed georeferencing, sync video and audio.Then there may be standards emerging that FME could utilize. How would you like to use FME with Full Motion Video?
An option like 'Run command' in the Transfer type dropdown with a 'Comand(s) to run' text box which runs the commands in the URL directory and returns the server responses would be great.It would save Python/WinSCP calls to run mv, chmod, cp, (mkdir, rmdir ;) ), etc commands.
As someone who relies heavily on the emailer transformer, seeing Microsoft move away from SMTP AUTH is a little scary. They're strongly encouraging customers to move away from basic authentication with SMTP AUTH when possible. It sounds like SMTP will be around for a while longer, but it would be nice to have OAuth support in the emailer as security continues to become a major priority. What do you think the future holds for SMTP AUTH? Let's get some discussion going.
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.
