Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Geosoft software products and formats are widely used in geology and geophysical fields including Exploration Geology, Geophysical Modelling such as Gravity and Geomagnetics, Geochemistry and UXO. The USGS has a webpage describing two of the Grid formats (binary & ascii): https://pubs.usgs.gov/of/2004/1258/Data/grid_facts.txt. Geosoft also has server technology called DAP (Data Access Protocol) for publishing, distributing and discovering exploration data: http://dap.geosoft.com/flamingo/
***Note from Migration:*** Original Title was: Use an external file with table for any transformers with attribute parameters table like in SchemaMapper.
***Note from Migration:*** Original Title was: The new geocoder in FME 2017 is missing output attributes from the old google geocoder that were important for us. Most notably, the attribute "Location Type".
A request to add some sort of schema version identification tag to the FME Server System Database. ex. a new metadata table.This would serve as a way to confirm the schema version and if it matches the FME Server Core connecting to it.Currently there is no way to determine the schema version. This can be troublesome when working in distributed environments where one needs to ensure the correct sql scripts were used to create the FME Server System Database. An example where this might manifest is during a restore where a new Core could try to insert a record that has a new attribute, however, fails because the table doesn't have the new column. It can take time to sort out the issue and learn that it is caused by an older schema being created.Often, we are not aware that a different database script must be run for new versions of FME Server. Other benefitsCould be exposed via the Rest API. Then exposed in the Web UI.Allow System Admins to confirm quickly via Database Admin tools the versionThe core could check the version and produce warnings/errors in the log and Web UI when an Admin user logs in.Distributed installs of FME Server continue to grow and this could help system admins and support staff in the long run.
Add support for the Riegl sdf format.SDF is the full waveform data format used by Riegl airborne laser scanners. This would be useful for analysing and processing data from this format.
Often when I drag-drop an FFS file into DataInspector to view it I would like to be able to split the data into layers by an attribute. It is what the Group By does for a viewer in workbench.Countless times I had to create a workspace only to be able to do this ...
Idea from FMWT 2017 at Lyon, France :FeatureReader & FeatureWriter work like datasets but are blue like normal transformers.A specific color could be great to distinguish them in the workspace. Maybe the features type color or a new specific color.@KenAtSafe
Create an entry in the navigator window for annotations in the workspace to easly navigate beteween them.
Add rejected port to all transformers and never crash the fme run because of bad feature.
This transformer would operate similar to the XMLValidator, but specific to HTML.
Right now, the 'Values That Must Differ' section of the Matcher transformer concatenates all attributes to 1 string and checks if the values are different. It would be nifty if AND/OR logic could be added. By this, I mean that the user could specify if all attributes must be different (AND) or that only 1 attribute out of 2,3,4,... must be different (OR).The same could be applied to 'Attribute Matching Strategy': all attributes must match (AND) or just one of the attributes must match (OR).
Either a new transformer (DateTimeSorter) or an extra option in the regular Sorter to sort on date/time attributes as depending on the notation the alphabetic/numeric options don't always give the right results.
Let's say that before an Oracle writer, I have a Counter and Stats Calculator. I use the total count of features as a condition in my Oracle writer to commit or rollback my transaction. If the right number of features were inserted, commit. Else rollback. Recplicating this with SQLExecutors is possible but involves a lot of hardcoding.
Please add PTS reader as native LiDAR format, because reading it as a CSV is veeeeeery slow.
It would be cool to have a "canvas cleaner" in the toolbar where when clicked remove all your inspector, logger & unconnected transformer. Also you could add parameters in order to let the user choose default options such as : keep logger
Rasterising Open Street Map should be much easier by allowing a stylesheet to be loaded into the transformer since manually entering 250 or so style lines is not practical.
There might be a certain mark or notification that shows the user that advanced settings are set (changed from default settings that come along with every writer/reader). I think that could prevent getting surprising results for users who are going to use another user's workspace straight forward without doing a deep inspection. A visible hint in the navigator near the corresponding reader / writer / feature would catch the attention and encourages user to investigate the special setting before running the workspace.
Simple python scripts as a drop-down in a transformer or easy (easy search, single click away) access beginner documentation. Starting with a blank python screen is intimidating for beginners or novice users.
***Note from Migration:*** Original Title was: AttributeManager - apply same action to multiple attributes by highlighting in list If AttributeManager is intended to replace AttributeKeeper/AttributeRemover, then it needs something to be able to remove a whole bunch of attributes easily. One way of doing this would be to be able to select (highlight) several attributes, then choose the action from the drop-down list and it would apply to all the attributes you selected. Ditto setting a value, etc.
Hi, I was trying to start following some of the topics, but there was no way for me to search the list without paging through them. Can you add a search there? Is there one that I didn't see?
***Note from Migration:*** Original Title was: Feature Connection Window Improvement: i think it would be great to have a visual cue such to indicate whether a source feature has been connected to a transformer or destination feature.
It would be helpful to have a job history summary page that groups by job name and gives average run time for that job and number of times it ran. Having the capability to change the date range would be an added bonus (e.g. show me a summary of all jobs in the last 24hours). Currently I am achieving this by directly querying the FME Server POSTGRES fme_job_history table and sending the info via email. A cleaner approach would be the ability to do so in the FME Server interface and even drill down to specific jobs to find failures and view logs.
Hi,I am creating maps in PDF format, using among others the pdfpageformatter. That works nice, I manage to create various layers in each map. I also manage to define tooltips.What I would additionally like to do is:- By clicking on a text or symbol in the mapframe, certain layers should be switched on/off (Action button)- The tooltip text is displayed horizontally, e.g. : "field1: value1; field2: value2" etc. Is it possibleto arrange the tooltip text vertically,e.g.field1: value1field2: value2etc.?
Add the ability to borrow a floating license for less than 1 day. This is useful when you have some people working in the evening or different time-zone, generally the come onto the network to check the license out but then want to disconnect for speed. You only want the license for your shift say 8 or 12 hours.
NOSQL Databases like amazon simpledb, apache cassandra, apache hbase -- indicate which in the comments. Note that MongoDB has its own card above. Note that FME currently supports Apache CouchDB, Amazon DynamoDB and Google Big Query.
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.
