How can we maintain multiple versions of the same DWG or other 2d file while uploading and translating the file. What are the preferred options.
I need to maintain the versioning of the files in Private OSS Bucket with Autodesk Forge and not using BIM360 in this case.
Thanks a lot.
OSS is just a simple blob storage service and as such it does not provide any versioning capability. You can introduce your own versioning schema, though, for example by appending a version suffix to the object key of every uploaded file (and then removing the suffixes when listing the objects), or by maintaining the document-version relationships (and then perhaps even folder-document relationships) in a relational database, with version records pointing to OSS objects.
Related
I`m quite new at using saleforce but I have been able to use Cloud Data Fusion recently to transfer information from a Data Extention to a table in Big Query.
Know I would like to do the same thing but with a Shared Data Extension, meaning that (possibly) features like the external key of the D.E would not exist because the D.E is shared by different Business Units (B.U) and also, I think I would have a problem by dealing with the authentication (Client ID – Client Secret - ) because again, is a Shared Data Extension.
Thank you very much for any insight on this matter.
I need to get the Versions of file which is uploaded to a specific bucket. if not possible can you please suggest a way to achieve the versing using forge
Buckets and objects are part of the low-level Object Storage Service that does not provide versioning (see https://forge.autodesk.com/en/docs/data/v2/developers_guide/basics for more details). You can either provide your own versioning logic on top of the storage service, or perhaps use the Items.
I am new to Autodesk services. We are having 1200+ 3D-models of size average 40MB. These models are built in .fbx format using Autodesk products. I have few doubts regarding how to proceed further. Please let me know. Thank you in advance.
Can we put our models on BOX. So that we can convert them into svf using Model Derivative API and save the output back in BOX Account. And viewer will be fetching the model file from BOX itself?
If yes can you give some references for how to proceed further?
If no, what is the costing of Autodesk server? I am aware that the free trial provides 5 GB free. But for further storage what is the cost?
My client is in US and customers are from US only, but later on we may move it to worldwide. So if needed can we change the region later on?
For now as I am from India, can I select the region to India, because the cost is like 0.6?
As we are giving access to models only to authenticated users, is Autodesk fully secure? What storage method/place will be safe?
From my forge account how can I see storage usage?
For performance wise which is the best solution for storing 3D Models.
In order to use Model Derivative APIs, your models must be uploaded to Forge using the Data Management APIs. After that, you could download the generated viewable files to your own storage, however this is not an officially supported workflow.
If you still want to serve Forge models from your own storage, this blog post shows how to obtain a list of all files that must be downloaded for a specific model.
With a non-trial Forge subscription, which costs $100 a year, there's no storage limit.
The data in Forge can be accessed from anywhere. In case you need to control the actual data center where your data shoud live, when creating a bucket for your data, you can choose between US and EMEA regions.
At this point the two available geos are US and EMEA.
Forge is secured; you can control access to content stored with Data Management APIs using 2-legged or 3-legged OAuth.
While in the trial, this information is not available. And as I mentioned above, with an active Forge subscription there's no storage limit.
I would recommend storing your CAD data in Forge. It's performant, safe, and again, the Model Derivative APIs can translate models from the Forge storage directly.
I'm trying to access files in my amazon S3 and do some operations on it. Currently evaluating the options.
Since I will be doing some operations on the S3 files, I would prefer using some language to access the files in S3 (I have already tried copy command).
My S3 contains JSON files which range between 2MB to 4 MB and I would need to parse these JSON and load them into a database (thinking about using JQuery here, but any other suggestions are welcome)
Given these requirements which is most efficient language/platform to be used here.
You options are pretty broad here. AWS has a list of SDKs for you to choose from. https://aws.amazon.com/tools/#sdk
So your comfort level with a particular language should be your largest influencer. Given that you mentioned JSON and JQuery perhaps you should look at Node.js SDK and AWS Lambda.
Trying to understand this help doc. It says:
The Realtime API provides a persistent document for the data that
users are collaborating on.
What is this "persistent document"? Is this a file in Google Drive? I'm not planning to store data in Google Drive and most likely will be using shortcut files. So how does that relate to my situation?
Applications that provide collaborative
editing features, but need to work with files in various formats, must
adopt one or more strategies for converting data between the Realtime
API document and other file formats.
I'm storing my data as XML in database. Does this qualify for "files in various formats"? How does that effect my situation?
Each file on Drive has content as itself and a permanent storage for Realtime API. In your case, your shortcut files will have Realtime structures even though your files wont have any content all.