Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Currently in the FME 2018 for Mac, you have to lay out the transformers in order to use the grids or guides to make a nice layout. Then you have to add in a bookmark, if you want to change the layout or add in more transformers, you have to move the bookmark off the transformers.
Similar to disable transformer, option to make the transformer inactive so that features can pass through without the effect of transformers being applied on the features passing through them in disabled mode
IFC specifications are detailed in an EXPRESS file. A customer would like to be able to validate his IFC to ensure that it conforms to the schema in the EXPRESS file. The output and interface should be similar to the XMLValidator. It should allow the user to pick the EXPRESS files presently shipped with FME, or choose their own from a custom location.
***Note from Migration:*** Original Title was: Add Parallel processing level and Input is Ordered by Group parameters to Clipper
In the WebTiler, it would be nice if we can specify a parameter to skip creating tiles that only contain NoData. See https://knowledge.safe.com/questions/69315/how-to-filter-out-raster-tiles-that-contain-only-n.html
In the inspector when using table view it'd be great to be able to change the zoom, like you can in Excel. Typically there's lots of values and can be small to see. It'd also make presenting the DI easier.
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.
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.
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.
Would be nice to have an option to preserve a schedule even if you set an end (expiry) date instead of deleting it.
***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.
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.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.