Invalid GeoJSON root structure with multiple feature types
| Problem | GeoJSON writer produces an invalid GeoJSON root structure if writing more than one feature type.The GeoJSON writer currently wraps the JSON feature collections with an array when multiple feature types are output.The GeoJSON standard mandates a FeatureCollection object as the root so this is incorrect (it is valid JSON but not valid GeoJSON). |
| Workaround | Write one feature type per GeoJSON output document.This can be done using one writer per feature type or dataset fanout on feature type name.In this case the root object is a FeatureCollection and our output is valid. |
| Status | We plan on making a major change to the GeoJSON writer for FME 2018.1 The current plan is to eliminate the array wrapper and properly support multiple feature types in a way that is consistent with the GeoJSON specification.We plan on adding a featureType property to the Feature object,instead of the array of named FeatureCollections that exists at the moment.If you have any comments or concerns on these planned changes please contact support. |
Known Issues between FME 2018.0 and 2018.1.1
Windows OS only: Enable system OpenGL for Web View
Problem |
Upon launching FME Workbench,FME displays the splash-screen and then crashes.
FME Workbench is likely crashing due to enabling system OpenGL for Web View inFME Options > Appearance > Rendering Options.The crash has occurred because the system's OpenGL is not compatible with what web view is expecting. |
Workaround |
A registry key edit can resolve this problem.
|
Status |
This option is no longer available via FME Options in the latest release of FME 2018.1.1.2.However,this registry key may still exist if it was set in a previous FME edition. |
Known Issues fixed with FME 2018.0.0.x
(32-bit only) Database/Web Connection Failure: Java Virtual Machine (JVM) memory issue
| Problem | A user may encounter an error inconsistently while retrieving database or web connections either via FME Options or within a Reader/Writer: Error message: "Error retrieving connections"Java Virtual Machine (JVM) memory issues on 32-bit Windows may prevent addition of certain readers/writers,or the correct application of web or database connections in FME 2018.0 Desktop x86. |
| Workaround | 64-bit FME 2018.0 does not exhibit this issue.Unless you require 32-bit FME for format support,we recommend using the 64-bit installer. If you do require 32-bit formats,setting the following FME environment variables should resolve the issue in 2018.0: SET FME_JVM_MAX_HEAP_SIZE=128M SET FME_JVM_MIN_HEAP_SIZE=128M If you are still experiencing intermittent connection issues,try altering the heap size:
|
| Status | This was addressed with the release of FME 2018.0.0.1 for 32-bit Windows.The JVM heap size will now default to 128M and will log a warning in the Translation Log after launching FME. It is possible that this value is not suitable for all cases - if you are still encountering an issue retrieving connections,please try using the workaround above by setting the heap size environment variables to a smaller or larger number.
Image Description: The Java Virtual Machine has customized initial heap size '128m' and The Java Virtual Machine has customized maximum heap size '128m' The issue has been permanently fixed inFME Desktop 2019,and can be seen in our latest FME 2019Beta releases. |
For reference,2017.x known issue documentation can beviewed here
I want to update Windows with the latest Security Patches but I want to make sure this won't change the behaviour of FME Desktop or FME Server.Is there anything that I should be aware of before applying the latest patches?
Known Issues with FME 2017.1.2.x
GML Writer writes invalid NaNs
| Problem | GML writer requires nans to be written as ‘NaN' to be considered valid geometry coordinate values.As of 2017.1 we began writing them as ‘nan' instead of ‘NaN'. |
| Workaround | Setting the GML writer advanced parameter Minimum Decimal Places to 1 or higher causes the correct value for ‘NaN' to be written. |
| Status | This will be fixed in FME 2018.0.1 and above. |
Invalid GeoJSON root structure with multiple feature types
| Problem | GeoJSON writer produces an invalid GeoJSON root structure if writing more than one feature type.The GeoJSON writer currently wraps the JSON feature collections with an array when multiple feature types are output.The GeoJSON standard mandates a FeatureCollection object as the root so this is incorrect (it is valid JSON but not valid GeoJSON). |
| Workaround | Write one feature type per GeoJSON output document.This can be done using one writer per feature type or dataset fanout on feature type name.In this case the root object is a FeatureCollection and our output is valid. |
| Status | We plan on making a major change to the GeoJSON writer for FME 2018.1 The current plan is to eliminate the array wrapper and properly support multiple feature types in a way that is consistent with the GeoJSON specification.We plan on adding a featureType property to the Feature object,instead of the array of named FeatureCollections that exists at the moment.If you have any comments or concerns on these planned changes please contact support. |
Issues fixed between FME 2017.1.1 and FME 2017.1.2
Database Connection Upload via Publish Wizard
| Problem | New database connections cannot be uploaded via the publish to server wizard.Existing connections are unaffected.This only affects the 2017.1.1 minor release. |
| Workaround | 1) Uncheck the database connection in the publish wizard
2) Manually create it via the FME Server Web UI
|
| Status | A fix has been completed and was made available with the release of FME 2017.1.2.FME 2018.0 betas more recent than b18188 also contain a fixed publish wizard. |
Issues fixed between FME 2017.1 and FME 2017.1.1
Twitter Transformer Authentication
| Problem | In July,changes occurred to the Twitter API authentication service which caused related Twitter transformers in FME to cease functioning. |
| Workaround | See:Knowledge Articlefor potential solution involving the HTTPCaller |
| Status | 2017.1 has updated logging to identify and report occurrences of this issue at run-time.The transformers themselves were fixed with the release of 2017.1.1 |
Data Inspector Crash on Read Error
| Problem | Inspector can crash when the reader returns an error,depending on the format.For example,an XML error report from a WFS server can cause the Inspector to crash. |
| Workaround | Use Workbench with an Inspector instead of Data Inspector. |
| Status | This was fixed with the release of 2017.1.1 |
Issues fixed between FME 2017.0.1.x and FME 2017.1
Ubuntu Kernel Upgrade crashing FME
| Problem | On June 19,2017 Ubuntu released a security update for both the 14.04 and 16.04 kernels that are incompatible with the Java subsystem used by FME. |
| Workaround | See:Knowledge Article |
| Status |
Can't Edit Web Service Properties in Publish Wizard
| Problem | When publishing a workspace to FME Server from FME Workbench,the "Edit..." button on the Register Services prompt of the Publish to FME Server Wizard is not accessible.This occurs when the "Change All Hosts" button on the Services page of the web interface is invoked. |
| Workaround | Running the addServices.bat file located in
|
| Status | Fixed inFME 2017.1 |
Issues fixed between FME 2017.0.1 and 2017.0.1.1
Sharepoint authorization
| Problem | Changes to the sharepoint.com login process have resulted in issues authenticating user accounts when connecting with FME. |
| Workaround | Update to latest FME official release. |
| Status | Fixed in 2017.1.1update(released May 17th).Also fixed in 2017.1 beta stream (b.17483 and aboveavailable here). |
Issues fixed between FME 2017.0.0.1 and 2017.0.0.2
High Data Volumes
| Problem | Individual large features (>~1MB) in conjunction with low memory can result in a crash |
| Workaround | Some 亚搏在线workflows will be able to avoid the crash by adjusting the memory "redline" to discourage stashing. Knowledge Center: How to control FME Server Engine Memory Usage |
| Detail | When FME detects a low memory situation it will attempt to store ("stash") features on disk.Stashing of features that require more than 1MB in serialized form will crash FME. |
| Status | Fixed in 2017.1.Mitigated in 2017.0.0.2 such that no crash will occur,but large features will not be stashed to disk,possibly resulting in virtually memory being exhausted sooner than would have occurred in FME 2016. FME 2017.1 betas areavailable here. FME 2017.0.0.2was released April 3rd. |
Issues fixed between FME 2017.0.0.0 and 2017.0.0.1
FME Desktop
Planet Data
| Problem | No Assets are visible |
| Workaround | Manually enter applicable Asset(s) for the selected Item Type. |
| Detail | To list Assets for a given Item Type,the Planet Data Reader queries for an arbitrary Item for the given Item Type,and presents its Assets in the GUI picker.On February 9,the Planet Data API changed to hide Assets that the user cannot download. |
| Status | Fixed inFME 2017.0.0.1 |
Buffering with group-by
| Problem | Buffering with a group-by can cause a crash with large enough parameters |
| Workaround | a.Do not use group-by OR b.Use custom transformer group-by instead,containing a Bufferer |
| Status | Fixed inFME 2017.0.0.1 |
@DateTimeNow() TimeZone Defaults
| Problem | @DateTimeNow() by default returns local zoned datetimes,but most users appear to have local unzoned datetimes.Zoned and unzoned datetimes cause a type mismatch in @DateTimeDiff() and this issue affects DateTimeCalculator as well. |
| Workaround | Execute @DateTimeNow(localUnzoned) instead,which returns unzoned local datetimes.Detail After calling @DateTimeNow(),use @DateTimeCast() or @DateTimeFormat() to reformat the timestamp value into other temporal types. Example 1: @DateTimeCast(@DateTimeNow(),date) returns today's date in local time. Example 2: @DateTimeFormat(@DateTimeNow(utc),%Y%m%d%H%M%S) returns an unzoned UTC datetime. |
| Status | Fixed inFME 2017.0.0.1 |
FME Server
Dashboard Migration
| Problem | As part of upgrading the Dashboards solution,migrating 2016 to 2017 does not import theDashboards_DailyTotalQueuedTimesubscription,but it still appears in the security page. |
| Workaround | The administrator can add the subscription and remove it to get rid of the subscription from the Security UI page |
| Status | Fixed inFME 2017.0.0.1 |