-
I've been trying to figure out if iTwin is a good fit for out purposes, and have started by just outlining what everything does. From my understanding, iTwin.js and iModel.js are essentially the same thing (though different than an iModel), and it can be used to display a static state of an iModel. iTwin should allow us to look around and see real time sensor data (?) as well information about physical properties. I can't really tell if it does much more than that, I've seen other features advertised on Bentley's website relating to Digital Twins, but I can't tell if that is separate. Then it seems like there are two separate services offered by Bentley? One to host the iTwin (which it seems like we could do entirely locally if we want?) and another to store all the iModel information on the cloud? Also, how much can we accomplish purely locally? If you could let me know if what I said is correct, that would be wonderful. Thanks in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
You are largely correct. iModel.js was renamed to iTwin.js (though some npm package names remained the same). The "Capabilities" section on http://www.itwinjs.org is a good summary of the library's features. Our GitHub repositories and YouTube channel also have good examples of projects implemented using iTwin.js.
iTwin Platform is our service offering that hosts your iModel and its information in the Bentley cloud, along with managing its timeline of change. The provided link describes the APIs that make up iTwin Platform. You can also host iModels in your own cloud environment or use them locally on desktop or mobile. iTwin.js is a common library used for both strategies. These options are one of the unique strengths of iTwin. You can use the iModel as your common persistence format while picking the appropriate tech stack for each part of your application (for example, mixing the Bentley-hosted web stack with Unity-based VR applications). |
Beta Was this translation helpful? Give feedback.
You are largely correct. iModel.js was renamed to iTwin.js (though some npm package names remained the same). The "Capabilities" section on http://www.itwinjs.org is a good summary of the library's features.
Our GitHub repositories …