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, FME has the ability to interface with the R Project through the RCaller transformer. This requires knowledge of the R Project language.It might be useful if FME had transformers that made it easy to harness specific functionality/algorithms possible in the R Project. One example of just such an algorithm is the Minimum Spanning Tree. My question for you is what R Project functionality/algorithms would you like to be easily accessible in FME? Another way to think about this is what statistical or analytical problems do you want to solve as part of an FME workflow?
I'm really excited about the RasterConvolver transformer in the 2018.1 beta. However it applies the convolution filter to all bands. It would be nice if this transformer supports band selection and only applies the convolution filter to the selected bands.
For a long time, most major OGC WFS servers have supported stored queries: ArcGIS, Degree, GeoServer, MapServer. In many cases, for performance reasons, WFS servers will not let you query more than one feature type at a time unless you define how the 2 are to be joined. Because these joins are hard to define, one of the easiest approaches is to define the join within a stored query. For example - give me all the parcels and roads in the town of Spuzzum. The only way to execute a stored query from FME's WFS reader now is to include the stored query parameters on the initial dataset getCapabilities request url, for example: http://gisserver.domain.com:6080/arcgis/services/SampleWorldCities/MapServer/WFSServer?service=WFS&version=2.0.0&REQUEST=getFeature&TypeName=cities?tIndex=0&count=5&STOREDQUERY_ID=urn:StoredQueries:AttributeDemo&myrank=3 Any parameters you add to the wfs request url eventually get passed to the getFeature request. But this isnt very intuitive so it would be nice to have this added to the WFS parameters user interface. Heres a good link describing most basic types of stored queries that it would be good to be able to support: https://enterprise.arcgis.com/en/server/10.3/publish-services/linux/communicating-with-a-wfs-service-in-a-web-browser.htm
MapInfo has a new format called the MapInfo Extended format supported from MapInfo Professional version 15.2. The format enables a few new capabilities but most notably the ability to break the 2GB file size barrier and store multiple character sets in the same file:http://web.pb.com/mapinfopro-oct-2015/MapInfo-Pro-v15.2-Breaking-Down-BarriersIt appears that the latest Beta of FME 2017.0 b17215 now includes a Reader for this new format, but this is a vote for a Writer for the same format please!
**I'm still using 2017.1, apologies if this has been resolved in a later version**Currently when you use AttributeValueMapper, the import allows you to import duplicate values rather than check if you've already got the value and mapped it in the transformer. Can this be enhanced to recognise the values already mapped rather than keep adding the same value again? Or even better, to enable you to sort on the 'Source Value' field?For Example, I'm consolidating a few datasets in FME hence might use the import feature twice once for a shapefile, another for a KML. I have High=1, Medium=2, Low=3 imported and mapped from the shp, then import the values from KML and get High (already exists), Very Low (new), Medium (already exists).
I think it would be great if the featurewriter could support multiple formats and coordinate systems simultaneously so we don't have to have several featurewriters for the same data.e.g. If each of the feature types added to the writer below could maintain their own format and coordinate system that would be awesome.
The layer name is available in fme_feature_type but the feature service that contains the layer isn't available.
Lots of municipalities are managing assets and property data through the use of flat files with extension .tps (Keystone software). Currently, ArcCatalog is able to access the data using a paying ODBC connector from Softvelocity, but we're not able to to use this in FME.Being able to read/access the data directly in FME would greatly improve current workflows.
The excellent Workspace Viewer (FME Server) should be released as a mobile app. That would allow us to view and share FMW(T) files.
Currently, using DWGStyler to rotate text and output to DWG, you will find that the angle of the text is not changed in the output DWG. But if you use FME Data Inspector to view the text before the output, you will find that the text has been rotated. I tried a lot of methods, including using Rotator, setting autocad_rotation, autocad_text_rotation, but all got the same result.Finally, the comment of mark2catsafe in the following QA was inspired. I gave autocad_original_rotation the value of autocad_rotation output from the Rotator, and finally got the desired result.How to define the rotation angle of annotation? (SHP to CAD)If the user have to set autocad_original_rotation to be able to change the angle of the output DWG's text, it will be confusing to the user. Because it is a property unique to the DWG format, I think that the setting of autocad_original_rotation should be implemented inside DWGStyler or inside the DWG Writer, rather than having the user manually set it.
In case if someone would like to take a look at a workspace which is stored in FME Server without having to download it on FME Desktop; forinitial debuggin purposes for example.
Hello,I propose adding the following options to FME Inspector transformer :Visibility order (an integer value ranging from 0 to x) ;Visibilty default value (On/Off) (I often want some details to be present in the Data Inspector but not toogled visible until I need to visualise them for some special operations, to do this I have always to toogle them Off after each translation and On lately in case of need)
I find my workspace looks a lot cleaner when the majority of the bookmarks are set to 1 colour. It also allows me to highlight specific areas e.g. 'needs updating', 'testing', 'external source'. Credit to @adrianp1spatial
Being able to adjust my call and quickly verify the result would cut out a lot of the time for using this transformer. It would also help for using things like the XML/JSON transformers down the line. I imagine this to be in the form of a collapsible window at the base of the Transformer. I think this would also help in addressing parts of this idea: https://knowledge.safe.com/idea/55826/make-it-easier-to-work-with-jsonxml-result-from-re.html
Give the AttributeValueMapper the ability to map more than 1 field at a time... go on... you know you want to! It'll save having to do this kind of thing:https://knowledge.safe.com/questions/71480/attributevaluemapper-equivalent-to-lookup-and-repl.htmlThank you...
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.