Skip to main content
Question

What causes a workspace fmw to be saved in JSON format?

  • September 19, 2022
  • 4 replies
  • 58 views
chk1
Contributor
Forum|alt.badge.img+7
  • chk1Contributor
  • Contributor

While looking through a folder of workspaces with a text editor, I noticed that one workspace fmw file was not in the usual XML-like format. It was instead a JSON file with a leading header line:

# application/x-fme-json-workspace

The last build/saved metadata states "FME(R) 2020.0.2.1 (20200511 - Build 20238 - WIN64)" - however when I create a new workspace with this version, it is saved in the XML format. I tried a variety of FME Desktop versions from 2019 to the most recent 2022, none save to JSON, but all are able to open the JSON fmw.

 

This question is in part simply out of curiosity, and also because I have made a small Python script that iterates over a folder to gather some metadata that the WorkspaceReader does not publish (luckily the attributes I'm looking for are in the same "path" in both formats).

4 replies

david_r
Evangelist
  • david_rEvangelist
  • September 20, 2022

That's an interesting observation, I've never seen this myself. I just searched through some 1400 workspace files (going back 10+ years) and was not able to find any such JSON variants.

I suspect you'll have to contact Safe support for this one.

chk1
Contributor
Forum|alt.badge.img+7
  • chk1Contributor
  • Author
  • Contributor
  • September 20, 2022

Today I found another format which roughly looks as follows:

FMW0001
#
# bunch of metadata here
#
 
**********
<binary data here until end of file>

File is not encrypted, I can't tell if it's just compressed in some way. 

 

 

JennaKAtSafe
Safer
Forum|alt.badge.img+6

Hi @chk1​, thank you for brining up this interesting observation. Here are some thoughts on the origin of this json workspace.

Webbench in FME Server converts xml workspaces to json for the gui. This is the only place where we suspect the json workspace originated from. This however should have only been a temporary file on FME Server, and your instance "escaped". Hope this can answer a part of this mystery.

david_r
Evangelist
  • david_rEvangelist
  • December 5, 2024
chk1 wrote:

Today I found another format which roughly looks as follows:

FMW0001
#
# bunch of metadata here
#
 
**********
<binary data here until end of file>

File is not encrypted, I can't tell if it's just compressed in some way.

Recently stumbled upon one of these. In our case, there was a password set on the workspace. Removing the password and saving the fmw reverted the file contents back to normal.

Reply


Most helpful members this week

Community Stats

30,845
Posts
116,930
Replies
38,666
Members
Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.