Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
In many occasions I use a FeatureMerger to verify the match of ID between two datasets.In this situation I really don't want to merge attributes at all. I use the Feature Merge Type "geometry" but then I need to restor the original geometry of the requestor (GeometryExtractor / Replacer).My life would be much easier with an option "None" which checks the match between two dataset but leave untouched both requestor and suppliers so I don't have to worry about attribute accumulation.
Hi,The AttributeManager works well for most purposes, but I've run into some problem (2016.1) when using it to handle cases of 50-100 attributes. In these cases the dialog box is essentially buggy, and one quickly loses ones overview, rendering it unstable. I have a few bug issues and a few suggestions for improvement.I've experienced the following bugs:- The whole transformer is very, very slow, taking many (e.g. 5) seconds to display itself. This also - When I'm using the "Filter" to limit the list, at any time the insertion cursor may jump from the filter entry textbox into the "Action" dropdown for any of the filtered attributes. A longer wait, or a mandatory press on Return, would be better.- Often when I'm clicking on the Action dropdown on an attribute in a filtered list, another attribute pops into the top, shifting the whole list, so I essentially end up changing a setting on a wrong attribute.- Often, when I'm updating e.g. "Remove" to "Rename", the display will not update, so I have to save and reload it.Here are some suggestions for improvement:- Color-code the lines wrt. the action chosen. This will enable a much better overview of the status of each attribute. E.g., I often mistake "Rename" for "Remove" when glancing thru the list.- Enable temporary sorting of the list using any of the 4 columns (Input Attribute, Output Attribute, Attribute Value, and Action). Again this will enhance the overview immensely.- Filter on Action may also be of great use.Hope this'll be of use, and hopefully my suggestion may be implemented soon :-)Cheers
Using the AttributeManager some users have reported that it is hard to tell the different Actions apart and colour coding or icons might help. If you agree please up-vote or if you have a better idea please comment.
The SQL transformers allow you to hardcode your SQL in the interface or select it from an attribute constructed earlier in the process. It would also be nice to be able to run SQL "from file" where the code is stored externally in a *.sql file. This could be a little like the flexibility offered in the FTPCaller "upload from a file" or "upload from an attribute".
It would be great to have a date/time rounder transformer that can round time to example nearest even hour, day, 5 minute etc. (inspired by this Q&A : https://knowledge.safe.com/questions/30353/rounding-time-to-5-minute-intervals.html )
***Note from Migration:*** Original Title was: Format support for HL7 - Personal health records, outbreak management, vaccinations There is broad consensus on exchange of health information for pharmacy, hospital records, personal health information, vaccination program delivery, and outbreak management through the Health Level 7 body of web services and data exchange formats listed at HL7.org. We are seeing more integrations of front-end CRM systems with back-end government systems supporting HL7 standards. And leveraging data stored in back-end systems for epidemiological analysis in GIS environments such as EpiInfo or statistical packages such as SPSS (or Tableau) is becoming more necessary for public health professionals.
For customers that run 'Production' and 'Disaster Recovery' environments the 3-server redundant failover licensing model is not appropriate. In this case the 3 servers must be able to see each other, so having them span the Prod and DR environments can't be done as typically these environments can't see each other. What would be great is if FME Desktop could allow you in the license assistant to point at a primary and a secondary (failover) license server so that it could failover between them automatically if the primary production license server goes down. This would mean that one license server could sit in the Prod environment and the other in DR. This is clearly supported by FlexLM as ArcFM and ESRI (desktop applications) licence servers are FlexLM based and function in exactly this manner. There are some basic details here: http://support.esri.com/technical-article/000010729 but this has been inherent functionality within the ESRI licence server for some time. I appreciate that FME Desktop is moving away from FlexLM but I'm informed that it may be far enough away to justify looking into the viability of this approach. I'd be interested to hear the thoughts of the community and how you manage FME Desktop license failover aside from the above. Thanks, Dave
I would like the AttributeManager this to work with multiple actions. For example, I would like to rename a field as well as Set Value in a single attribute action rather then doing it in two steps.
Have the ability to connect to SharePoint 2010 and have more integrated functionality with SharePoint Lists and Data
It would be helpful if FME could handle changes to file destinations on the fly. This way if a destination drive starts filling up faster than expected a user could re-path the rest of the files to a new resource. This obviously would not work for single file outputs but would be useful for multiple file outputs.
https://knowledge.safe.com/questions/38456/clip-las-at-feature-reader.html
My client uses SQLExecutor (FME 2016) to call a procedure inside SQL Server.This complex procedure sends back 10 tables : A Table, B Table, C Table, ... J Table.But some tables could have no data.SQLExecutor outputs only tables (as entities) with data (ok normal behaviour, FME dont create empty entities).But we dont have an index (the cursor ?) to know which table is outputting.By example :- The procedure sends : A Table with data, B Table wih data, C Table to I Table with no data and J Table with data.- SQLExecutor outputs 3 entitites : A Table, B Table and J Table.-> But we don't know in FME that first entity maps A Table, second maps B table and third maps J Table.If SQLExecutor could generate a cursor attribute, it would be fine :Fist entity : _cursor = 0 (means A Table)Second entity : _cursor = 1 (means B Table)Third entity : _cursor = 9 (means J Table)
Right now the Chopper doesn't keep track of which remnant was where in the original feature. E.g. if I use it to split a line into individual segments (max vertices 2) or points (max vertices 1) there's no way of telling what the original order was, other than that they're being output in that order. Fine if you manage to maintain that order, but that's not always the case.So I would like to argue for a _remnant_id attribute that keeps track of that.
It would make life a lot easier if there was an x,y search in the data inspector. I have to find a lot of features by their location and its awkward to try and pin point an area. The mark location is nice but if there was a zoom to location I would make use of that.
***Note from Migration:*** Original Title was: SpatialRelator / Spatialfilter: Add a note in the log when coordinate systems are different SpatialRelator / Spatialfilter: Add a note in the log when coordinate systems are different
Add an additional column to enter an error text or concatenated text in the AttributeValidator would be cool...
It would be nice if an existing FME Cloud instance could be copied or moved to another region that is supported by FME Cloud. Right now a new instance needs to be launched in the new region and a migration of FME Server has to be performed.
In the Mac version of Workbench the tabs are a much darker shade of gray than in Windows. This makes it difficult to read the text on the tab. Could the user be allowed to change the color of the tab like they can for annotation/bookmarks? This would make the text more readable and allow more customization within the workspace.
When trying to clip a raster to a polygon if the spatial extents don't match, no warning is given, no errors. Just no features are written out, but reports 'success'.
I would like some mechanism to dynamically add attributes to a writer – presumably linked to some transformer. Note that this is not a dynamic schema -- The attributes do not exist on the source data, and I don’t know ahead of time what the attributes will be so I can’t manually add them to the writer. An example is any key/value pair from a list (ListHistogrammer for instance) where I would like the attribute name (key) added to the writer.
It would be nice if there was a native fme transformer to intelligently join file path components, similar to python's os.path.join.ie concatenate all the parts with exactly one directory separator ( or /) unless already included in the part, ignore empty parts except the last.So something likeattr1: d:attr2: dir1attr3: dir2attr4: dir3dir4attr5: {missing}attr6: file.extwould become d:dir1dir2dir3dir4file.extEven better if it could work with either a series of attributes or a list
If that is even possible……Assuming you are reading in poitclouds and want to make hillshades - using the ArcGIS hillshade_3D function - out of them.So you read the poitclouds make the raster with a DEMGenerator.Now you want to call the ESRI hillshade function (and other functions) with a PythonCaller using arcpy.But first you have to save the raster on disk, so ESRI can access it by reading it in again.In Python arcpy you can use the ESRI in_memory workspace:env.workspace = r"in_memory"env.overwriteOutput = TrueinRaster = FME_MacroValues['inRaster']inRemapFile = FME_MacroValues['inRemapFile']arcpy.HillShade_3d(inRaster,"TMPRaster", azimuth, altitude, modelShadows, zFactor)OutRaster = ReclassByASCIIFile("TMPRaster",inRemapFile)OutRaster.save(FME_MacroValues['OutRaster'])arcpy.Delete_management("in_memory")The raster comes to the PythonCaller as an FME object.So instead of reading the raster from disk again, it wold be great,if you can write the raster (or any other point, line or polygon Feature)directly into the “memory workspace” of ESRI.With a parameter – lest say selfdistruction Yes, or No – you can copy the feature into the memory workspace,or move it there and delete the FME object from memory.After the ESRI functions you can read the object back from the ESRI memory into the FME memoryand the translation continues in FME with some tiling or reasampling the raster and writes the rasters finally to disk.
Please improve transformer documentation specifically on the Join On parameter. @takashi provided a good on his blog: http://fme-memorandum-takashi.blogspot.com/2013/10/join-on-parameter-of-featuremerger.html. It would be nice to include links to samples, if any.
It would be nice if tutorial web pages did not assume you knew certain steps by saying things like "Upload your data to your server instance", but could also be cumbersome for more experienced users to see all that. It would be better if this were handled similar to ESRI's online courses where the details of a task are hidden unless a user clicks to show them. This avoids opening a new web page with previous instructions on it where the user then has to read through and find the pertinent information. Instead the task would say "Upload your workspace to the server instance (show me how)" and clicking on "show me how" would expand, on the same page, a set of bullet point instructions on uploading data to a server instance. This keeps the user on a single page and does not make them find where they were in the text when they come back from another page. This way the experienced user does not need their hand held, but novices have direct access to what they need to know,
***Note from Migration:*** Original Title was: Add "Attributes that must differ" like in the MATCHER to some (or even all?) transformers that use "group by" e.g. in the commonsegmentfinder with that you could connect the same source-line-Features in Base and candidates and you could easily find common Segments in one source by Setting "Attributes that must differ" to the ID of the source
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.
