In revit project, my plugin add custom parameters in some of the sheets
Now, I convert the rvt file to svf2 format with derivative api and display the svf2 with the forge viewer.
I should read my custom parameters and there values (only read, not display) and use them in my viewer extension, but I do not find them in the model.
so question:
are the parameters exported ?
if yes, how can I retrieve them ?
thanks in advance
regards
Luc
Related
I was trying some hands on with forge services, I want to fetch few object's properties inside of a revit model uploaded on bim360/ACC, for which I am calling two API's 'https://developer.api.autodesk.com/modelderivative/v2/designdata/job' for translating the job to svf and then calling API "https://developer.api.autodesk.com/modelderivative/v2/designdata/" + urn + "/metadata/" (with urn of the translated job) (failed when passed urn of revit file directly)
Can we not directly get the metadata/properties without converting the file to svf? Since translating to svf is taking a lot of time for large files, my motive is to decrease the time to fetch the properties, can you share any solutions if you think of any please?
Yes, you are correct in assuming that you need to translate to SVF in order to access any BIM element properties at all. It's either that, or open it in desktop Revit and access the data there. Also discussed in the Revit API discussion forum thread on fetching metadata of a model using Forge model derivative API.
I would like to use Autodesk Forge to extract the log of activities (named "File Activities") for models stored in Autodesk Construction Cloud Docs. An example of the information is attached as an image below. I have so far been unable to find anything in the Forge Documentation, other than extracting the file attributes and last modified information.
Is it possible to extract the file activities? If so, what is the best way for me to proceed?
File Activities
Unfortunately, no API exposed for the activities functionality. I will log a wish.
We have a 2D DWG file that is georeferenced with coordinates and translate the file using forge API.
We load the file on the forge viewer and load Autodesk georeference Extension. (checked on AutoCad 2021 tool as well)
I am trying to retrieve these properties but get
hasgeoreference false,
globaloffset undefined
Because of this, I am unable to use the LMV LAT functions in the georeference Extension.
could someone tell me if I have missed something...?
What application is your georeferenced DWG coming from? The Forge Model Derivative service supports georeference data coming from Revit 2D sheets but I'm not sure about other applications. Also, if you could privately share one of the DWGs with us via forge (dot) help (at) autodesk (dot) com, we'd be happy to pass it on to the engineering team and investigate further on our end.
I have a Revit file. In this file, there are multiple objects. These objects have metadata.
We have a Forge Viewer based application where we show translated Revit files. The translation is done by Forge Model Derivative.
I recently noticed that in the Forge Viewer, an object is missing a property value.
I confirmed that this object has the property when I opened the original file in Autodesk Revit application.
I also have separated the Revit object for more investigation. Property missing Forge and Revit I will share the file when asked.
This issue has been reported as RVTLMV-1294 [Missing OmniClass Title value after translating] to our engineering team to allocate time to do further investigations.
Therefore, please make a note of this number for future reference. You are welcome to request an update on the status of this issue at any time via sending an email to Forge Help email quoting this issue list item number. Thanks!
the customer data can be either of dwg file level or object level(such as XRecord), is it possible that Viewer reads it like reading metadata from Revit? Thanks.
You can extract custom data using the approach described in this sample. As of now, the sample runs on Design Automation v2, we're migrating it to v3.