topic Re: Revit Addin Database selection, data storing format and import-export coding in Revit API Forum

Revit Addin Database selection, data storing format and import-export coding

Anonymous — Tue, 24 Dec 2019 15:03:41 GMT

Hi all,

We are at the very beginnig of a project on development of a database and its connection to Revit with an addin. The database will be a collection of system families like walls, floors, facade and roof. We have three questions in mind to find answers.

1. Which database is most useful to keep the data? We have began with MS SQL but if it is not the right choise we can change it as we are at the beginning.

2. Should we save the data in XML format or do we have another option as we will show the appearance of the building elements in the addin interface, too?

3. If XML is the right choise, we can find some information exporting the data but we could not find any information about importing the data to Revit if anyone can give us information we will be grateful.

Thank you in advance.

Re: Revit Addin Database selection, data storing format and import-export coding

Anonymous — Wed, 25 Dec 2019 07:58:39 GMT

1. In my opinion the best choise would be MognoDB. See Jeremy Tammik example https://github.com/jeremytammik/FireRatingCloud

2.3. JSON format is more easy to use with JavaScript, so if you plan to make some web services it would be better choice.

Re: Revit Addin Database selection, data storing format and import-export coding

Anonymous — Thu, 26 Dec 2019 08:52:36 GMT

Thank you for your suggestions. 🙂 We will go trhrough MagnoDB database and JSON format and discuss as an alternative.

Re: Revit Addin Database selection, data storing format and import-export coding

jeremytammik — Thu, 26 Dec 2019 12:20:11 GMT

The suggestion intends to recommend Mongo DB:

https://www.mongodb.com/

Welcome to the Revit API and good luck getting started!

Re: Revit Addin Database selection, data storing format and import-export coding

Anonymous — Fri, 27 Dec 2019 14:12:48 GMT

my choise mssql database and select xml format. Because xml format read and write very easy. if you save all project Ifc format convert xml but element in project ( for example wall) I don't know how to save

Re: Revit Addin Database selection, data storing format and import-export coding

Anonymous — Fri, 27 Dec 2019 16:55:36 GMT

We have the same problem. We do not need to save whole project. We want to save the building elements in database. We want to connect the revit to database with an addin and import the building element we need for the project. As far as I understand system families do not have a file extention. We just add to project or export them to databases with some codes. One of the issues that we are looking for is how to import the building element information from the database.

Re: Revit Addin Database selection, data storing format and import-export coding

jeremytammik — Fri, 27 Dec 2019 21:46:17 GMT

The database and format you use for storing data is pretty irrelevant.

More important is: what do you wish to store exactly, and why?

You say you also want to read data back in from the external storage to create or modify BIM elements.

What data? What elements? Above all, why?

Re: Revit Addin Database selection, data storing format and import-export coding

Anonymous — Sat, 28 Dec 2019 07:49:42 GMT

We want to understand the right way to do the job. We are very new and trying to find out how things going on. We want to store sound insulation ratings of building elements and make things easier for architects when designing a project. Use the right details in terms of acoustics. This not only for acoustic data we think that architect should be able to know some parameters like sustainability, fire rating an so on. We want to store the information on a database and give access to architects and select the right building elements according to requirement.

Re: Revit Addin Database selection, data storing format and import-export coding

jeremytammik — Sat, 28 Dec 2019 12:15:43 GMT

The FireRatingCloud sample pointed out above shows a very minimalistic and modern approach using a locally or cloud-based modern NoSQL database, mongoDB:

https://github.com/jeremytammik/FireRatingCloud

If you prefer something really antiquated and desktop bound, you can look at the original FireRating sample in the Revit SDK:

SDK/Samples/FireRating

It is in VB.NET (also obsolete!).

A C# version is provided by the Lab4_3_1_CreateAndBindSharedParam, Lab4_3_2_ExportSharedParamToExcel and Lab4_3_3_ImportSharedParamFromExcel commands in the XtraCs project in the Revit API ADN Xtra Labs:

https://github.com/jeremytammik/AdnRevitApiLabsXtra/blob/master/XtraCs/Labs4.cs

Re: Revit Addin Database selection, data storing format and import-export coding

Anonymous — Sat, 28 Dec 2019 20:33:15 GMT

both example are very nice. no sql (mongo db) example only store element id but no save element json or xml format. this point very important becouse The drawing should be saved to a different wall and opened on another computer. if I save element Id I can't reach it again.

Re: Revit Addin Database selection, data storing format and import-export coding

Anonymous — Sun, 29 Dec 2019 09:24:51 GMT

hi jeremy; it might be a tiring experience for you 🙂

Actually, we are trying to develop a similar application to knauf add in but we will have a variety of building elements in database.

https://www.youtube.com/watch?v=Lm_xIkmgbtw

1.how this button call the information from store as an element(not as id it must be element)
2.how the selected data(ex: wall system family) is imported to the revit project under wall system family tab

Re: Revit Addin Database selection, data storing format and import-export coding

jeremytammik — Sun, 29 Dec 2019 12:58:55 GMT

Yes, it is indeed tiring to repeat myself.

All these questions are discussed and answered dozens of times for many different scenarios here in the forum and by The Building Coder.

I suggest you study the articles on importing and exporting data:

Data access -- https://thebuildingcoder.typepad.com/blog/data-access/
Export -- https://thebuildingcoder.typepad.com/blog/export/
Element creation -- https://thebuildingcoder.typepad.com/blog/element-creation/
https://thebuildingcoder.typepad.com/blog/2012/09/exporting-parameter-data-to-excel.html

Good luck and happy new year!