.jt to .sas7bdat conversion

[cousineddie]

Has anyone worked through converting a .jt file to a SAS data set? I need to transfer the metadata stored on the .jt file into SAS, or into some format (txt, xml, csv, etc.) that can be easily read in by SAS. 

If you have experience with this, please share, as I'm looking to implement it as well. 

I have both Base SAS and EG. Version 9.4_M5 from proc product_status output. Thanks.

[LinusH]

Is this CAD metadata?
Don't think that there exist any standard way of importing this to SAS. I would look for a way to export this from your source in a readable format.

[cousineddie]

Yes, very similar to CAD. The .jt file allows you to view a 3D image of an engineered part, and the metadata within the file used to construct that 3D image is what I need to extract and get into SAS. 

There's got to be a way to extract it into something SAS can read in via DATA step (or special procedure). My hunch is XML, which is straightforward enough with SAS's XML Mapper tool, but getting from .jt to .xml, or, more generally, .jt to <X> is where I'm currently at. 

Appreciate the feedback. 

[Reeza]

Things to try then, you may already have done some of these:

1. change extension to text and see what shows up in a text editor. 

If it's plain text readable it's likely parseable with some elbow grease. 

2. Try a viewer and see if it has an export option:

https://www.plm.automation.siemens.com/en/products/teamcenter/plm-platform-capabilities/visualizatio...

3.Go back to source application and export in a different format

4. Determine file structure and reverse engineer it, which is probably a lot of work. 

---

@cousineddie wrote:

Yes, very similar to CAD. The .jt file allows you to view a 3D image of an engineered part, and the metadata within the file used to construct that 3D image is what I need to extract and get into SAS. 

There's got to be a way to extract it into something SAS can read in via DATA step (or special procedure). My hunch is XML, which is straightforward enough with SAS's XML Mapper tool, but getting from .jt to .xml, or, more generally, .jt to <X> is where I'm currently at. 

Appreciate the feedback. 

---