I need to use IFC for Revit library SourceForge link.
Can i override the version that is built in?
I mean using Document.Export(path,IFCExportOptions).
How can i use it in DA4R app ?
That's an interesting question, can I know why do you want to override the built in version? is there any limitation? Maybe that is also a good request for us to improve or fix in Revit. And Revit Design Automation engine currently supports Revit 2018.3, 2019.2 and 2020.2, are they all not working for you?
Revit Design Automation includes the support for IFC last April at https://forge.autodesk.com/en/docs/design-automation/v3/change_history/revit_release_notes/, I am not an IFC expert but I don't think there is a way for developer to specify the version in DA4R. But to override the current behavior to export IFC, in theory, you can achieve that within your Revit plugin on DA4R, but you need to customize all the export to IFC functionality within your Revit AppBundle(make sure no namespace conflict with current Ifc export library), you may also need to package all the dependent DLLs within the package to make it work, then upload as AppBundle, define an activity then post a workitem.
Please also notice that the limitation of Revit AppBundle size is 100M by default at https://forge.autodesk.com/en/docs/design-automation/v3/developers_guide/quotas/, you may need to override the size by checking https://forge.autodesk.com/en/docs/design-automation/v3/reference/http/servicelimits-owner-PUT/
Related
I have running Autodesk Forge Viewer and I was wondering if there is a know feature to add custom Lighting and Environments from an HDRI file since I was unable to find any helpful information in the Documentation. Does the Viewer support this feature or how would one go about adding a custom environment.
Customizing the environment maps is not an officially supported feature, but it can be done with a bit of hacking. The viewer uses DDS files for environment maps. Check out https://github.com/wallabyway/adding-shadows#sharper-ibl-reflections-image-based-light-ie-skybox for more info.
I have found a plug-in to manually export schedules (rebar, production bom, material lists) from Revit models. However, our company is looking to automate this and take out the human required element of exporting these schedules.
I have not, so far, found a way in the Forge API (Revit Design Automation API) to access these schedules like a can with a custom plug in.
Is this support coming or is there a place to vote on this capability?
Thanks,
Chris
The Forge Design Automation API for Revit enables you to run the same .NET Revit API code as the Revit.exe executable on the Windows desktop. Therefore, you can probably convert the existing desktop add-in to run within the Forge environment. There is no missing capability, not additional support needed, and no need to vote for anything. The Building Coder has explored and documented how to migrate and convert existing desktop Revit API add-in code to run in the Forge design automation environment in the topic group on DA4R – Design Automation for Revit.
Actually, I want to find a way to work with .rvt file without starting Revit Application. I want to create monitoring plugin to track changes in Revit Document Model. I suppose it can be made with Application events DocumentChanged. But it may slow the work with model for users. So I'm trying to find a way to work with .rvt file without starting Revit. So, does command that implements IExternalDBApplication need working instance of Revit application?
Your question is confusing.
I assume you are confused.
There are two ways (and two ways only) to access Revit API functionality:
Install Revit on the desktop and launch an interactive end user session. Within that session, you can set up a .NET Revit add-in to subscribe to certain events and make use of the Revit API functionality within those event handlers.
Make use of the Forge Design Automation API for Revit.
In the latter case, you do not have Revit installed locally.
Instead, you upload your application to the Forge system and make use of the Forge API via HTTP requests to launch a Revit engine in the cloud and process your Revit API functionality.
In both cases, however, there is a running instance of the Revit application somewhere providing the Revit API functionality you make use of. This cannot be avoided.
Some helpful links for you:
Getting started with the Revit desktop .NET API
Forge Design Automation for Revit
The Building Coder discussion on DA4R, Design Automation for Revit
I hope this clarifies.
We are working on an integration of an external software with Autodesk Forge. Following openBIM, we want to focus on model data in IFC format. Question is (and I was not able to find this answer online) which IFC versions are supported in the Forge ecosystem? Would one have to be careful with using e.g. only IFC 2x3 or is IFC 4 Add4 also supported? The documentation at https://forge.autodesk.com/en/docs/model-derivative/v2/developers_guide/supported-translations/ only generally mentions the IFC support, but no versions ... which would be a necessary information IMHO, as the format is still in active development.
(Just happened to see this thread)
As I know, there is no IFC 4 Add4, but IFC 4 Add2. See https://technical.buildingsmart.org/standards/ifc/ifc-schema-specifications/
Forge Model Derivative API currently has three IFC conversion methods: legacy, modern, and v3, which are the same as Navisworks IFC readers.
The legacy conversion method is under maintenance mode and doesn't fully support IFC4. So, it won't get updates anymore. For better IFC4 support, please use modern or v3 instead.
The modern conversion method is based on Revit technics. Currently, Revit supports IFC4 and IFC2x3. Its main features of exporting/importing IFC are provided by our open-source project Autodesk/revit-ifc. Model Derivative API uses Revit to export IFC from RVT files so that the supported IFC version will be the same as Autodesk/revit-ifc provided.
The v3 conversion method is based on the modern one but has some improvements (e.g. using file native distance units, not always feet)
Note. IFC4.x is not yet supported. For more details, please check out:
https://blogs.autodesk.com/revit/2022/02/09/now-available-revit-ifc-manual-version-2-0/ (Point Releases (4.x) already in the pipeline, including enhancements and new classes for infrastructure including bridges, railways, roads, ports, and waterways.)
https://technical.buildingsmart.org/standards/ifc/ifc-schema-specifications/ (BuildingSmart withdrew IFC4x1 and IFC4x2, and they are developing IFC4x3)
https://github.com/Autodesk/revit-ifc/releases/tag/IFC_v22.3.0.0 (Added additional generic support for IFC4.x files for 2022.1)
ref: https://forge.autodesk.com/blog/export-ifc-rvt-using-model-derivative-api
I am an App developer with no experience with AutoCAD at all, and for my current project I need to convert DWG files into Spatial Data - ESRI Shapefile / GeoJSON, etc.
Given that DWG is a proprietary format owned by Autodesk, the Autodesk Forge API becomes my only option to interpret such file. I have been evaluating the Model Derivative API for a week now, and what I found is that it won't work for my purposes. It has only 3 output formats (f2d, f3d, rvt) for DWG files and none of them fits my purpose.
For this reason, I started to look at others API's in the platform and ended up finding the Design Automation API which might be helpful, however it lacks documentation.
One of the examples in the API is the PlotToPdf activity that exports a DWG into a PDF. I wonder if there is a way to export other formats other than PDF.
I tried to find the possible "commands" in the interface by listing all the activities, workItems and AppPackages but none of these end-points returned me any useful information.
So here are my questions?
How can I can convert a DWG into a non Autodesk format? Being more specifically, the output must be an open format that I can interpret without using proprietary tools.
If the answer for the first question is Autodesk Forge API, which one should I use?
In case I should be using Design Automation API for that, where can I find complementary documentation once the one provided is lacking details?
I would say that Design Automation API is the best option if you don't have (or don't want) AutoCAD running (or any other DWG compatible desktop app).
To be complete: Design Automation includes an instance of AutoCAD running on the cloud, where you can upload a .DWG with a sequence of commands (script) and a .NET custom app to execute more advanced routines. Then download the results. By default, neither AutoCAD nor Design Automation can export to GIS formats (like those you mentioned), only some verticals, like Civil 3D or Map 3D, but these are not available on Design Automation. As you mentioned, Model Derivative API (via REST calls) don't have what you need, it's focused on metadata, not the specifications of the geometry.
Design Automation API supports the same commands AutoCAD Console does. For DXF creation, you can use DXFOUT command, your script would be something like (not tested):
FILEDIA
0
DXFOUT
outputfilename.dxf
QUIT
As per comment, it's a huge effort to just convert to .DXF. I'm not familiar with other libraries do perform the same task.
Now I'm not an expert on GIS data formats, but you may consider move from .DWG to .DXF then an approach like described here.
I don't quite understand this point that you are making in the comments:
I would only use the API to convert DWG to DXF, which means a huge waste of resources considering the monthly cost of the API and the time to develop and maintain the interface.
Can you clarify? Are you saying that transaction cost for Design Automation is too high? Or are you saying that development cost associated with deploying the script that Augusto gave you is too high?
Thanks
Right now the derivativeApi is the way to go for this: You can convert any input format from this list (https://developer.autodesk.com/en/docs/model-derivative/v2/overview/supported-translations/) to the "intermediate format" svf and the convert the svf file to obj for example. This will also create a material file which can be downloaded seperately. I am evaluation the forge api right now and can produce obj from dwg files right now.