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 this idea: https://knowledge.safe.com/content/idea/87500/process-started-by-the-systemcaller-should-end-if.html I think more should happen when a user has aborted a workspace (or at least it could be an option workspace parameter).In this case I think that a defined python/tcl shutdown script should run even if the user aborts the workspace.As mentioned in this Q/A https://knowledge.safe.com/questions/87933/python-shutdown-scrips-when-workspace-cancelled.html there is a limitation when it comes to live streams, the only workarounds being pretty ugly in nature.
***Note from Migration:*** Original Title was: Portal Reader Feature Service Parameter - allow portal items shared to the connected user to import the service's layer list In the reader's Parameters Constraints box, when a feature service list is displayed in the dialog, only the feature services owned by the connected user can display a Layer list pop up. If a selected feature service not owned by the connected user and the Layer ellipsis is clicked a Python Exception <KeyError>: u'items' appear.
It would be great if FME could support open location codes like Google's Plus Codes This would be a really useful alternative for places that aren't easily located otherwise. I'd like to see this functionality supported in the GeometryReplacer or GeometryExtractor.
Inspired by https://knowledge.safe.com/questions/74227/smooth-line-keeping-vertex-positions.html
Hyattached the dataset that I used to test center line replacer
Original Title: Extraer geometrías de las anotaciones de un PDFOriginal title translated to english for improved searchablityPara agilizar trabajos, con base cartográfica, sí se tienen que dibujar áreas sobre una cartografía existente. Usando las anotaciones del PDF, se podrían exportar también al igual que el resto de información.English translation: To expedite cartographic-based work, areas do have to be drawn on existing cartography. Using the PDF annotations, they could also be exported just like the rest of the information.
I've been experimenting with the System caller to run third party command line tools. It works great for the most part, however, when you stop the workspace the called process keeps running.It would be nice if the call could be killed/cancelled when the FME process is aborted. The problem is compounded when the sub process leverages the folder created by the TempPathNameCreator - If the FME process is aborted then these files do not get cleaned up.Idea comes from this QA: https://knowledge.safe.com/questions/87473/process-triggered-from-system-caller-does-not-end.html
Currently when writing an excel file with multiple sheets, the last feature written controls which sheet the file opens to by default. It would be nice if we could explicitly control which sheet it should open to.
It's baaaacccccckkkkkk. FME 2017 -- Build 17156 or later...
In the Data Inspector view filter, if you have many Feature Types and you filter by one attribute which only one FT has, all others are filtered out, since they don't have any value for that attribute. If you could specify which FT you are filtering this would be solved.
I'm generating files with my FME workspace for ingestion into another data management platform. In order to get the data ingested I need to also create a file containing a checksum (MD5 currently) for the data platform to check file integrity.As I'm already using the FeatureWriter to create files before pushing them to the platform I would like to see the option of being able to create a checksum for the written file and adding it as an output summary attribute, then I can easily use the same workspace to perform the complete upload process.
CGAL is an open source C++ library for powerfull geometry calculation. I would be nice to have some of it embeded in transformers. I'm thinking of something similar to the "TesseractCaller". info on https://www.cgal.org This could be very usefull to transform CAD-BIM-GIS data.
Reading large XML can be quite time consuming, even with FME! My idea is to upgrade the XML reader to use the feature tables technology to speed up things.(hopefully this is already on the roadmap...)
I would appreciate UPDATE button on Attributefilter transformer, similar to Featuretypefilter. It is really strong weapon to get attribute values when I use more than one data source...
Hello,as I work with customers, they still more and more use MS WORD writer, so there are still more requirements to develop functionality of this writer. Two of requirements are placing text and image next to each other - so there is necessary column divider functionality. Secd requirement is placing of watermark to .docx document. It would be great to use these functions! :-)Thank You so much!Lubo
OBJ Reader - add option ignore texture/materials to make it faster to load files when no texture is needed,
Huge LandXML files takes a long time to read. Is it possible to change the readaer for LandXLM to be read as Feature Tables to speed up reading? Would be great!
For those of us in other hemispheres, it is often difficult to catch your guys online (9-12 and 1-4 just doesn't cut it these days).Have you got any plans to increase the hours? - perhaps using global partners?Thanks
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.