Skip to main content

Hi group.

A workspace that worked previously is suddenly failing on certain data since the last run half a year ago.

I'm running it in 2018.1, but originally it ran in 2016.1, so I tried to backport the workspace to 2017.1 and 2016.1 to see if that made any difference.

I'm utilizing a small dataset of buffered counties, and stored the buffered and thinned and otherwise manipulated dataset in an FFS file for convinience and performance. This file works nicely in 2018.1 and 2017.1, but 2016.1 claims that it has a wrong header or something ??

This error persisted even when I used 2016.1 to create a clone FFS from the original non-FFS dataset ?

Can anyone shed any light on the pitfalls of using FFS as intermediate storage ?

Cheers.

FFS files are versioned according to the version of FME that wrote it, this is due to new functionality etc. that is added in each new version of FME.

This means that FME can read FFS files written with older versions of FME (backwards compatible), but not necessarily with FFS files more recent than the FME version that's reading them.

If you need long-term storage that's independent of FME version, you may want to consider using a different format.


You can download the 2016 version here : https://www.safe.com/support/downloads/#past-versions

Added an idea here - feel free to vote and add your comments @lifalin2016 https://knowledge.safe.com/idea/104226/use-ffs-to-archive-spatial-data-for-storage-simila.html?


You can download the 2016 version here : https://www.safe.com/support/downloads/#past-versions

Added an idea here - feel free to vote and add your comments @lifalin2016 https://knowledge.safe.com/idea/104226/use-ffs-to-archive-spatial-data-for-storage-simila.html?

I already have 2016.1 installed.


I've got a similar request - created an idea here.


Reply