Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
FME Server can be configured in a distributed install to use an external database (e.g. SQL Server) and for high availability installs this is actually a mandatory requirement. It is not possible to use the embedded FME Server database in a high availability installation.The current FME Server configuration requires that the connection to the database specifies the port number that the database is communicating on. If the port number is left blank, then (for SQL Server databases) it defaults to 1433.Independent of FME, as a security measure, SQL Server can be configured to run using dynamic port allocation. So the SQL Server connection port changes over time.All online references that I have found state that simply removing the port number from the JDBC connection string should be adequate to make use of dynamic port allocation, however, when the port number is removed from the JDBC connection string in the FME Server configuration it is being replaced with 1433. I believe that this is being done by the FME Server code.My request is to allow FME Server to be configured to make use of dynamic port allocation with SQL Server backend databases.
Not sure if it is possible, but also import email adress from Active Directory-user using FME Server web-gui.
Use case: I convert dates to UNIX seconds (%s) to calculate differences, and then I may need to restore original format of the date attribute.
In order to save the space when resizing/adding more windows to the interface, please add a check box to enable the Logger window's word wrap option in Tools> FME Options >Appearance, to permanently save this effect.
Similar to the 'Group By' functionality of the Inspector in FME Workbench.
Particularly relating to licensing, what is the default version, and managing python interpreters/packages/etc.
***Note from Migration:*** Original Title was: Add common date/time formats such as FME Date/Time (%Y%m%d%H%M%S) to Source Date Format in DateFormatter Add date/time formats such as FME Date/Time (%Y%m%d%H%M%S), Locale Date (%) to unknown - Automatic Detection in Source Date Format drop down list in the DateFormatter. As well as being handy, it would help to avoid confusion - see https://knowledge.safe.com/questions/42603/warning-tip-ymdhms-datetime-values-in-csvs-are-not.html
The DateFormatter doesn't recognise <date>T<time>Z format for example which is valid as of ISO 8601. Removing the ending Z is a workaround but it would be nice if the transformer accepts any valid ISO date/time as web services tend to produce all spectrum of valid ISO date/time strings.
Include some helpful hints in the spatial filter parameters for those of us who struggle to remember which way round the tests are performed
FME Server needs a 2nd log button that gives just the end result counts of read/write in a nice table. In most cases we have no need to see the full log and reading the end of the current can be confusing, because the end of the log may say 0 features written but above that are the actual counts of the features written.
***Note from Migration:*** Original Title was: Automation of python script zipping files using FME Server allowing user parameters Just an alternative to using zipArchiver transformer and Data Download Service===========================================================================import osimport zipfiledef zipdir(path, ziph): # ziph is zipfile handle for root, dirs, files in os.walk(path): for file in files: ziph.write(os.path.join(root, file))if __name__ == '__main__': zipf = zipfile.ZipFile ('$(FME_SHAREDRESOURCE_DATA)Upload/$(nameUploadedFiles)', 'w', zipfile.ZIP_DEFLATED) zipdir ('$(FME_SHAREDRESOURCE_DATA)Upload/', zipf)zipf.close()===========================================================================Initially I was to use zipArchiver transformer in my workbench, but our IT Security did not allow me to download and use it. So I chose to create user parameter(nameUploadedFiles) and add the lines of simply Python code for Job Submitter service to be published. So, Data Download Service is not required to be published at all. Users can login into FME Server, upload files in the folder, specify the name and run the workspace to get the zipped file.
Add 32 and 64-bit on the ICON of all exe-files. Makes it easy for me with all versions installed (32-64bit, 2013,2014,2015) to distinguish them :) https://fmecommunity-ideas.s3-us-west-2.amazonaws.com/4036.png
It would be fantastic if you had the option, when feeding in two polygons, to have a spatial relationship of requestor contains CENTER POINT of supplier. That way you could ensure a 1:1 relationship when doing a select.
Due to the annual drift of the continents, there is a growing shift between coordinate systems with the reference Systems ITRF2000 and ETRF89. The annual shift is about 2,5 cm each year which results in a gap to WGS84 in FME, as this coordinate system seems to have a reference to the epoche of 1989. This gap is now about 75 centimeters. Comlexe formulas will have to be implemented to solve this problem, an idividual grid-shift file will not result in the desired accuracy. The integration of this annual shift for every year is important for many clients, especially airports.
See Title.
Really just promoting this question to an "idea". External attributes which are exposed on a custom transformer input port get applied to all input ports in that custom transformer. It would be nice if the exposed attributes could be tied to specific input ports.As was noted in the original question, if different features are coming into different input ports, then they will not all necessarily contain all of the attributes being exposed and this can lead to confusion within the custom transformer as to what is really available on a feature.Similarly for output ports. If features exiting a specific output port only contain certain attributes, then invalid attributes should not be made available to the caller.
Would be nice if the Geocoder transformer have the precision result as an output field With Here API or Bing API, we can get the precision of any geocoded addresses (Address, Street, Postal Code, Country, etc.)
It would be nice to have the option of selecting all or caret insert when selecting/editing transformer names.As a side note when opening the "Workspace Search", the Find box should have the focus and it would be nice if the contents of the 'Find:' are all selected (similar to what I am complaining about above).
For our projects we have a series of tests we run on FME Server to check over data. The tests are separated by utility pipe network and live in their own repositories. At the end of the project, when all networks are completed, there is a final process to run which is uploaded to all 3 repositories - when updating this workspace it is obviously necessary to upload the workspace 3 times. Hence it would be good to have the ability to shortcut to one location of a workspace, so that it can be uploaded just once but run from any number of locations.
From the reader gallery you can create a custom format reader and use it, however, from the writer gallery it seems you can create a custom format writer, but that can not be used.
If I have a user that needs to interactively do a Road-Name search then road names containing diacritics will fail the search. The workaround is to have 2 road name attributes, one for searching, and one for publishing. For my Road-Name search attribute, I need to be able to strip out the diacritics. PostgreSQL offers a "unaccent" function to do this - can we have this same capability inside FME StringReplacer or similar? Refer https://www.postgresql.org/docs/9.1/static/unaccent.html
Hello, I request this functionality as a result of the question discussed here: https://knowledge.safe.com/questions/42506/readingwriting-microstation-properties.html The information seen via File->Properties in Microstation can currently not be read from / written to DGN-Files with FME. It would be nice to have FME attributes corresponding to the various text fields found therein. Regards
Create a new interface which allows users to graphically view the entire FME Server system architecture, all the key components and their interconnections. It could be a web based Workbench like interface, but would need nodes that represent individual services, notification subscriptions, topics, publications, file and web resources etc. This way it would be a lot easier to trace the dependencies through the services and notifications.
Working with large (GB) of JPEG files - reading and writing with FME takes a long time. There is an open source implementation (beta) that uses GPU to compress/decompress JPEG if you have an NVIDIA - possible to implement this in FME? Cutting edge! https://github.com/CESNET/GPUJPEG
It would be nice to have an option on the FeatureReader to allow for case insensitivite feature types and corresponding ports, particularly using folder based formats where the feature type comes from the filename. So that FileX.shp, and filex.shp are treated as the same feature type.
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.
