Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Similar to how the Slack integration works, it would be nice to automate the push notification of x,y,and z to a channel within Microsoft Teams.
I'd like to see a mechanism to filter the advanced value handling in the AttributeCreator. If I'm reading in hundreds of features from different files, I would only want "feature[+1]" to read from the next row IF the filename matches too. I'm currently fixing this by saving feature[+1].fme_basename and running through a Tester, but a "Group By" or something on the AttributeCreator might be cleaner?
Hello,I'm wondering about data showing in the Visual Preview.Below an example. Two flows of data going to two Inspectors.When I select the SRC_RAW Inspector the Visual Preview shows the SRC_NORMALIZED data.I will have to use the drop down menu in the Visual Preview to retrieve the SRC_RAW data.That has annoyed me for quite some time now - why can't I just select the Inspector and see the proper data straight away?Cheers,Ed
Could you get a supplier first function similar to the feature merger for the spatial relator as this would help improve performance.
It would be nice to be able to lock the position of objects in workspaces, e.g. transformers, readers, writers. Sometimes when I am selecting and/or moving objects in large workspaces I move something unintentionally. It would be nice to be able to lock the layout of completed areas. It would be cool if this could be done at the bookmark level.
Currently after creating a Resource Connection on FME Server, in order to work with the FME Server macros $() when authoring workspaces I must create a Private Parameter or else transformers will display as red when I reference these. I would like the option to instead create an FME Server Parameter. This would be helpful as it means I can create a parameter for my new resource once only and it will then be available across all my workspaces, instead of having to create a private parameter every time I want to work with this.
It would be nice to see a drop down for version (required) and build (optional) for new questions added on the forum and displayed just below the topic in a small font. This would be beneficial for researching/answering questions in the correct context.
Has anyone considered providing a gridding algorithm other than TIN in the FME workbench? I would love to be able to grid using IDW or kriging or some other method. There is open source code available, see below. It would be great it this code or other gridding code could be included. Workbench already has grid math for 1 or more grids, so it would be great to be able to make grids which you can then combine together in a formula, or add, or subtract to create a new information product/grid.https://richdem.readthedocs.io/en/latest/index.html
Writing in Excel files, Like the HYPERLINK (see https://knowledge.safe.com/comments/35259/view.html )It would be nice to define a commentary over a value fieldE.g. value -> measurement / value.comment -> remark about measurement.It would avoid too large sections between the lines for big comments when they are shown as a column.
Would love an easy way to show processing time PER transformer to quickly identify transformers that a performance bottle necks.The number would be the processing time of features being processed by that transformer.Either by a report, log or visually on the workbench when running in the feature caching mode.This would be of great help to prioritize work on performance/workbench timings to schedule data processes on time.
Try and make resource browsing experience closer to what you would expect from a file browser. - Altered UI/UX to a more familiar file navigation experience for users (similar to file navigation on the computer)- File tree to allow quickly dive deep into folders- Bookmarking folders for quick access from the file tree- Quickly create new folders in directories without the need of filling several fields- Right-click to quickly copy and paste files/folders
It would be great if the MeshSimplifier had an option to preserve edges.This would be very handy for example when you have multiple terrain tiles that you need to optimize but you want to make sure that the edges between the tiles meet up without gaps.
***Note from Migration:*** Original Title was: SchemaMapper - Change icon color to Red icon for invalid entries, and highlight the part is invalid It happened that the SchemaMapper is no longer working for me.After I thoroughly investigated, I found out that one of the Filter Features part of the Schema Mapper parameters is no longer valid (in fact the attributes got renamed in the source Schema Mapping file). If it visually has changed the SchemaMapper transformer icon toRed to indicate error, and highlighted which entry I should spot and validate, I wouldn't spent that much time to figure out what happened to cause the failure of the workspace.At least, I'd suggest something like what shown in the snapshot.
***Note from Migration:*** Original Title was: Restore: Enable to link Point Cloud XYZ Reader Component Mapping to a User Parameter In FME 2019 and earlier, we were able to create user parameters to allow users to specify component mapping for a Point Cloud XYZ reader appropriately according to their data schema. For example:Definition of the COMPONENT_MAPPING parameter (Python scripted):import fmexcol = fme.macroValues['X_COL']ycol = fme.macroValues['Y_COL']zcol = fme.macroValues['Z_COL']return 'x,col%s,Real64,y,col%s,Real64,z,col%s,Real64' % (xcol,ycol,zcol)However, I found this disabled in FME 2020.0 and 2020.1 beta, so some existing workspaces cannot be updated with FME 2020.I cannot understand why you did that. Strongly hope this will be restores.
The RasterDemGenerator produces a raster with an interpretation of REAL64. It would be nice if we could specify the interpretation in the transformer rather than needing a rasterBandInterpretationCoercer immediately thereafter.
Currently, FME Engines must be located in the same network as the FME Server install. Remote Engines would enable you to deploy the FME Engine in a different network to the FME Server core. The Remote Engines would communicate securely with the FME Server Core over the internet. This would enable the following workflows:Hybrid Deployments - Spread your FME Engines across multiple clouds, on-premises and the cloud, or within a cloud in different networks (e.g. public, private clouds)Regional Offices - Deploy the FME Server in one office region, and then deploy Remote FME Engines into other office regions next to their data.IoT Workflows - Deploy the Remote FME Engines on the edge directly next to the sensor.In short, it will enable you to move FME closer to the data without having to manage multiple FME Servers.
The GoogleDriveConnector transformer fails when attempting to download a file if the file with the same name exists already in the directory.I have seen this post: https://knowledge.safe.com/questions/100344/overwrite-option-in-google-drive-connector-in-down.html and that's a solution, however, it adds additional transformers to the workspace.It would be nice if the 'overwrite' option was available within the transformer.
Being able to run Windows containers with FME Engines on them in a Kubernetes cluster would enable users to read/write to Windows only formats in a K8S cluster.
Create a transformer that can be used to simplify complex meshes, so it would be nice if we had a transformer that could be used to create smooth meshes from simpler ones.
Hi.I'm trying to utilize the Workspace Reader to handle my almost 200+ repository of workspaces.I stumbled over a few issues with the Workspace Reader, that I want to propose as improvements."PublishedParameters" include both published and private parameters + parameters to embedded custom transformers. But it doesn't include any way of distinguishing between them. Please add an extra attribute for this."WriterParameters" does not include e.g. the MSSQL_SPATIAL parameters for executing statements before and after translation. Are they available elsewhere ? If not, please add.This is what I've found sofar.Cheers
Hello,When generating with the numericrasterizer, it uses the altitude values to define the raster pixel values. But an essentiel point is not configurable and understandable: how this transformer chooses the pixel value when several points are located at the same XY but nut at the same Z. (easy examples : a tree, a power line, a building, any vertical things or thing above another one).We don't know if the value taken by the raster is linked to the average of the points in the area (pixel size) or with the min, the max, randomly ...?I have noticed twice that points above the ground are not always taken into account and therefore do not appear on the raster, which makes it wrong because not all the elements are included. This is a bit of a pity for a transformer that is supposed to make a representation according to the elevation...It would be extremely useful (see indispensable) to be able to choose which value of z is used. Because this transformer works perfectly, it gives really nice results but it does not allow to have something reliable and rigorous.I hope that it would be possible for you to add a parameter something like "z value dertermination" with -lowest, -average and '-highest choices :)Regards,Arnaud
WebVR allows developers to publish interactive VR content on the web, which can then be accessed from any VR device with a web browser (including mobile VR, like Gear VR, Google Cardboard, Oculus Go & Oculus Quest). Introduce a WebVR / WebXR Writer.
Add the functionality to Read and Write MIDI FIles in FME.
Is it possible to try to reduce the memory footprint used when FME Server / Cloud is running idle? Ie have no jobs?The starter instance of FME Cloud seems to use 2,7GB RAM when "no work is done" - is it possible to squeeze this down by 10%? 40%? Might be a good internal hackathon.The reason for doing so would be to make more memory available for the tasks themselves and avoid these frequent issues when you hit the roof on the lower-memory computers:2020-04-22 17:02:43| 16.4| 0.0|INFORM|ResourceManager: Optimizing Memory Usage. Please wait... 2020-04-22 17:02:43| 16.5| 0.0|WARN |ResourceManager: Freed 683495 bytes of vector data (memory decreased by 1256384 bytes) 2020-04-22 17:02:43| 16.5| 0.0|WARN |ResourceManager: Freed 42565632 bytes of raster data (memory decreased by 42566352 bytes) 2020-04-22 17:02:43| 16.5| 0.0|WARN |After freeing memory: tcmalloc GetStats 2020-04-22 17:02:43| 16.5| 0.0|WARN |------------------------------------------------ MALLOC: 834246680 ( 795.6 MiB) Bytes in use by application MALLOC: + 0 ( 0.0 MiB) Bytes in page heap freelist MALLOC: + 28814680 ( 27.5 MiB) Bytes in central cache freelist MALLOC: + 10370640 ( 9.9 MiB) Bytes in transfer cache freelist MALLOC: + 18742336 ( 17.9 MiB) Bytes in thread cache freelists MALLOC: + 4796608 ( 4.6 MiB) Bytes in malloc metadata MALLOC: ------------ MALLOC: = 896970944 ( 855.4 MiB) Actual memory used (physical + swap) MALLOC: + 971071488 ( 926.1 MiB) Bytes released to OS (aka unmapped) MALLOC: ------------ MALLOC: = 1868042432 ( 1781.5 MiB) Virtual address space used MALLOC: MALLOC: 17172 Spans in use MALLOC: 3 Thread heaps in use MALLOC: 8192 Tcmalloc page size ------------------------------------------------ Call ReleaseFreeMemory() to release freelist memory to the OS (via madvise()).
Please add 3D Oriented Bounding Cube to BoundingBoxReplacer
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.
