0

We've had good luck importing, converting, and extracting meta data from .rvt files using the following steps:

  1. Uploading files in chunks to an OSS bucket using resumable endpoint
    • PUT buckets/:bucketKey/objects/:objectName/resumable
  2. Kicking off a new job to convert the file to SVF
  3. Validating the job completed successfully completed
  4. Get the GUID for the 3D view
  5. Check that the metadata call doesn't returns 200 not 202

When running a .dgn (Bentley) file through this process, it gets through steps 1-4 OK, and even loads and displays metadata in the viewer. But, the call in step 5 will never return 200OK or and metadata.

Anyone had any luck working with non Autodesk file types?

Ben
  • 21
  • 2
  • Hi @Ben, can I know you are testing with 2D or 3D DGN? if 2D, sorry getting metadata is not yet doable for 2D documents. This has been logged as a wish and will be implemented by the development team. the other post tells in detail: https://stackoverflow.com/questions/42956703/how-do-i-get-metadata-from-a-2d-dwg-file-using-forge-autodesk-apis – Xiaodong Liang Dec 22 '17 at 07:47
  • I tested with a 3D DGN, the metadata works well. This is a snapshot in Navisworks and Postman (with Forge endpoint) . https://ibb.co/iLsKfR – Xiaodong Liang Dec 22 '17 at 08:02
  • Thanks! I am working with a 3D dgn, it's actually just an sample I downloaded to test. http://www.q-cad.com/samples/microstation-3d/microstation-3d-samples/ . I suppose it's possible there isn't data to extract, but I find that hard to believe because I get properties in the viewer. And if there was an error, I would expect the metadata call to fail rather than return 202 forever – Ben Dec 22 '17 at 12:38
  • I can reproduce the issue with this specific DGN file. I agreed with you that if there is any error to extract the metadata, the model structure or property should not work well in Forge Viewer. I logged the issue as internal ticket : DERI-4718 . Please make a note for inquiry in the future. Sorry for the inconvenience. – Xiaodong Liang Dec 23 '17 at 14:34
  • just an update: the root issue has been addressed by our engineer team. – Xiaodong Liang Jan 02 '18 at 06:36
  • Thanks Xiaodong! Any update on when this will be released? – Ben Jan 08 '18 at 14:43
  • Hi @Ben, sorry I missed your comments. We have not an exact time table when the fix would be available. While we will inform when it is released. Thank you for your patience! – Xiaodong Liang Jan 19 '18 at 05:57

0 Answers0