Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Could be useful for readers as well.
In Google Maps Directions API it is possible to get the waypoints from one coordinate to another coordinate as polyline: https://developers.google.com/maps/documentation/directions/Request example:https://maps.googleapis.com/maps/api/directions/json?origin=46.9745777,15.6211898&destination=46.9752438,15.6144307Google returns a JSON (because I have requested a JSON) with several information - including waypoints in an encoded format (see line 63, 87 and 101):{ "geocoded_waypoints" : [ { "geocoder_status" : "OK", "place_id" : "EipLaXJjaGJhY2hlciBTdHIuIDk5LTEyMiwgODA4MSwgw5ZzdGVycmVpY2g", "types" : [ "street_address" ] }, { "geocoder_status" : "OK", "place_id" : "Ej1HdWdnaXR6IEJlcmd3ZWcgNTQsIDgwODEgUGlyY2hpbmcgYW0gVHJhdWJlbmJlcmcsIMOWc3RlcnJlaWNo", "types" : [ "street_address" ] } ], "routes" : [ { "bounds" : { "northeast" : { "lat" : 46.9774785, "lng" : 15.6212531 }, "southwest" : { "lat" : 46.9746073, "lng" : 15.6144114 } }, "copyrights" : "Kartendaten © 2018 Google", "legs" : [ { "distance" : { "text" : "0,8 km", "value" : 811 }, "duration" : { "text" : "1 Minute", "value" : 81 }, "end_address" : "Guggitz Bergweg 54, 8081 Pirching am Traubenberg, Österreich", "end_location" : { "lat" : 46.9752518, "lng" : 15.6144114 }, "start_address" : "Kirchbacher Str. 99-122, 8081, Österreich", "start_location" : { "lat" : 46.9746073, "lng" : 15.6212531 }, "steps" : [ { "distance" : { "text" : "0,4 km", "value" : 361 }, "duration" : { "text" : "1 Minute", "value" : 20 }, "end_location" : { "lat" : 46.9774785, "lng" : 15.61923 }, "html_instructions" : "Auf u003cbu003eKirchbacher Str.u003c/bu003e/u003cbu003eB73u003c/bu003e nach u003cbu003eNordwestenu003c/bu003e Richtung u003cbu003eGuggitz Bergwegu003c/bu003e starten", "polyline" : { "points" : "ivu}Gy_j~ASR]RuBh@{@Rg@PGBc@Ra@TUN_@V{AlAY^MPMRQ\\IR" }, "start_location" : { "lat" : 46.9746073, "lng" : 15.6212531 }, "travel_mode" : "DRIVING" }, { "distance" : { "text" : "0,4 km", "value" : 450 }, "duration" : { "text" : "1 Minute", "value" : 61 }, "end_location" : { "lat" : 46.9752518, "lng" : 15.6144114 }, "html_instructions" : "u003cbu003eLinksu003c/bu003e abbiegen auf u003cbu003eGuggitz Bergwegu003c/bu003e", "maneuver" : "turn-left", "polyline" : { "points" : "ghv}Gesi~ALh@X`CzAfHp@hBfA|BJPnAzBr@fAPT\\Z" }, "start_location" : { "lat" : 46.9774785, "lng" : 15.61923 }, "travel_mode" : "DRIVING" } ], "traffic_speed_entry" : [], "via_waypoint" : [] } ], "overview_polyline" : { "points" : "ivu}Gy_j~ASR]RqD|@o@TeAh@u@f@{AlAY^[d@[p@Lh@X`CzAfHp@hBrAnCnAzBr@fAn@p@" }, "summary" : "Kirchbacher Str./B73 und Guggitz Bergweg", "warnings" : [], "waypoint_order" : [] } ], "status" : "OK" }See the algorithm of Google to encode this, so it should be possible to decode the string when dooing the step in the other direction:https://developers.google.com/maps/documentation/utilities/polylinealgorithmOn this page is an example of a JavaScript code to decode the polyline string: https://stackoverflow.com/questions/40877840/google-maps-api-draw-a-route-using-points-of-a-polylineBut unfortunately it's not possible to include the JavaScript library in the JavaScriptCaller:https://maps.googleapis.com/maps/api/js?libraries=geometryBecause JavaScript seems not to be fully supported by the JavaScriptCaller, it would be great to do the decoding via GeometryExtractor or GeometryReplacer.There are already a lot of encodings (GeometryExtractor > Parameters > Geometry Encoding):https://docs.safe.com/fme/2017.1/html/FME_Desktop_Documentation/FME_Transformers/Transformers/geometryextractor.htmThe "Google Maps Polyline Decoder" should be added.
Since 2018.0 it is not possible to select multiple objects within a bookmark without moving the bookmark itself. Especially with bigger workspaces this can be really frustrating. It would be great if this can be possible again.
***Note from Migration:*** Original Title was: improve the generation of 3DTiles. Tiles generated with FME are less performant than tiles generated by AGI/Cesium.
Hi!Could you facilitate to select a list element from the back? For example, when accessing a particular list element in a Tester, I can input a number > 0 in the list element selection dialog. But why not from the back like -1 or -2.Sure I can use a ListElementCounter before, subtract -1 of the result in the following transformer of my choice and submit a _list{@Value(_element_count)} (what I have to type manually, as it's not possible in the list element selection to chose an attribute as value). Or I can use the ListIndexer before (where actually it is possible to choose the elements from the back), and create additional attributes, I don't really need. Why making life harder than necassary? Wouldn't it be better to do this things just in one step using only the list element selelction dialog?Of course this refers to all Transformers where I may need to input list elements as a parameter value.
During the FME WT (Seattle) we were shown that sensitive information/credentials could be removed from a workspace uploaded to FME Server. It would be helpful to have this sort of capability when sharing a .fmw or a .fmwt so credentials are not accidentally stored in an otherwise freely accessible workspace.
Using FME Cloud to run a lot of short jobs can be very expensive for the amount time the server is run for. For instance, if you need to run a translation that takes 5 minutes to run every day, you'd be billed for a lot of server time that isn't used. AWS recently allowed billing on newer linux in intervals less than an hour. It would make some workflows very affordable on FME Cloud if billing was less than an hour. Based on this knowledge base question: https://knowledge.safe.com/questions/37275/fme-cloud-pricing.html
Hi there, is it a good idea to keep the formatting of the SELECT statement in the MSSQL reader? For example, once I created the adjusted query, like this one:After pressing the OK button and reopening the query field, it looks totally scrambled up like this:An sich this would be acceptable for simple queries like the one above, but if one uses complex queries that are under construction and therefore change quite often, this becomes VERY annoying. Using SQLCreator I loose the processing order of SQL statements, so not really an alternative. And of course one could use a textfile reader and have the contents fired by an SQLExecuter, but hey, what for do we have the MSSQL reader then?
I use the LineCombiner a lot, a nice option to have is able to set start of the line consist of a certain attribute we can select from the list of available attributes =; like; <>; < or > etc. I had to workaround by using Snipper to shorten the beginning of the line so that it's not connecting to the prior line, then use Snapper to snap to prior line without connecting to it.
Quite often we test spatial location by setting one coordinate equals the other but forget to make sure the number of decimal places match since source can come from different databases. It would be nice to have a global variable in the workbench that all the numbers are automatically round to nearest xx decimal.
Currently the VertexCreator in Insert Point at Index Mode will reject point features as invalid. These features would benefit from Insert point at index 0 in cases where the orientation of the line matters.
***Note from Migration:*** Original Title was: Allow users to pick measures from one dataset in LineOnLineOverlayer when multiple measures exist Currently when multiple sets of data enter the LineOnLineOverlayer transformer, the first set, if has measures, will be used for the segments in the output. If the first set does not have measures, the segments in output will not have measures. The order of the data going in is by the reader and then alphabetically if all the datasets are from the same reader. So if you want measures from a specific dataset, you will have to add an additional reader to host that dataset and make sure it is read in first.My idea proposal is for a new parameter on the transformer to allow the users to pick the measures from one of the datasets.
Would be nice to have an option to preserve a schedule even if you set an end (expiry) date instead of deleting it.
It is very beneficial to be able to store all custom FME work between versions and installations. FME has "FME Shared Folders". However, while this works for connections, transformers et.al., it apparently doesn't include custom formats developed with e.g. Python. My suggestion is to add this possibility to the "FME Shared Folder" functionality. Basically it would just require FME to scan a few additional folders during startup, so it's not that big change, I think. Cheers.
Right now, there is no ideal configuration to store a Custom Transformer exactly one time and use it within FME Desktop and FME Server as a Linked Custom Transformer. There are several workarounds:1. Create Shared FME Folder --> use the folder within the Workbench --> upload Custom Transformers to FME ServerThis works, but in fact it duplicates the Custom Transformer on each FME Server (Development, Staging, Production). When creating a new version of the Custom Transformer, it has to be uploaded to all FME Servers again.2. Create network share and reference it as a Custom Resource within FME ServerUnfortunately, the FME Server Engine doesn't scan Custom Resources, so a Workspace with a Linked Custom Transformer from the network share will crash in FME Server.3. Share the Engine Resource Folder of FME ServerThis would also work, but I don't like the idea of exposing some server internal folder by sharing it to the network. Furthermore, it doesn't solve the problem of sharing a Custom Transformer across different FME Servers (Development, Staging, Production), because each instance would have its own Engine Resource Folder which would lead to multiple Shared FME Folders within Workbench.4. Use Embedded Custom TransformersNot really an option because it is impossible to use exactly the same Custom Transformer per definition.Thus, FME Server and Desktop should be able to reference any arbitrary network folder as a source for Custom Transformers.
I am looking for a transformer to generate circular histograms/polar coordinate plots/rose diagrams.
Right now, selecting Segment Snapping while using the AnchoredSnapper means that candidate features will also be snapped to line segments within the specified tolerance. However, candidates will also still be snapped to vertices, and the AnchoredSnapper even prefers vertices to segments, even in Segment Snapping-mode. My use case is that I need to snap certain features to the closest point on a line. However, in some cases there is a vertex nearby that is not the closest point, but still within tolerance, and the AnchoredSnapper prefers these points. I can probably find some workaround, but a simple checkbox to force the AnchoredSnapper not to snap to vertices but only segments would be a cleaner solution.
Could there be an option/setting/toggle that would analyze workspace at start of run for the optimal place to "kill" or drop any attributes which are not ultimately get written or used to derive some other value beyond a certain point? That way they are still shown as available at every stage in the workspace so that the author has full access to them. This would increase run performance because those attributes don't get (cached/processed) beyond where they are needed while also sparing the author from having to add/configure the attribute keeper transformer, which can cause additional headaches later as the workspace evolves and you suddenly need that attribute you dropped somewhere earlier. Could call it the Dynamic Orphaned Attribute Killer workspace parameter, jk.
Socrata has a metadata API for updating metadata within a socrata data. FME can handle the datasync API for updating actual values, but it would be helpful to be able to change the metadata as well, such as descriptions.
Do you have plans to include a Rocket.chat connector in the transformer list?
When working with Linked Transformers and editing, saving. It is cumbersome to always have to restart a new FME Workbench to reload the Custom Transformers after saving an edit. A button to "Force refresh" of initialization of Custom Transformers / formats etc would be great.
There is now an FMEAR app for iPhones and iPads. There is development planned for an Android version. Is there any interest in a Microsoft based version for Surface tablets?
Business case: downloading a folder from the share data folder in FME server is not an option in 2017. It forces the user to select all individual files to download.My Scenario:I have a project that needed to run 3 models with a Job submitter service as I was writing back to the Shared Data folder. The second model takes the out put from the first as input, then the 3rd takes the results form the second to run.-- for technical reasons I couldn't get everything in the same model. It would have been nice to be able to also download the zipped folder as each step ran so that the user can see the data transforming at each step.
Possiblity to cancel Jobs direclty from the "Job Submitting Page" would be nice
I am following the FME Server SSL Configuration steps as described online.First I had to move the tomcat.keystore file into te tomcat root folder. Later I was asked to set the keystoreFile path in the tomcat server.xml:keystoreFile="<FMEServerDir>Utilities omcat omcat.keystore"Wouldnt it be better to set the default value of this parameter to:keystoreFile="tomcat.keystore"In that case the user does not have to set te path anymore, as long as the tomcat.keystore file is placed in the tomcat root folder. Which is the case when the user follows the manual.
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.
