ApplicationID and GUID missing for LEVELS in Revit and Archicad connectors Version 3

Hi,
Thanks for the help :grinning_face:

  • Objective: Find ApplicationID and GUID in Speckle.

  • Issue: I expect these properties to be here, but I can’t find them in neither Revit models or ArchiCAD

I’m unsure if miss a section in Dev mode or something else. Could you advise on where I should look for these properties, or if these properties are not yet available?
I see that there are several IDs in dev, but I´m interested on tracking the “main” ID, that I belive its ApplicationID in Speckle

Alternatively the GUID should be used too, which is classified into IFC Parameters --IFCGUID for other elements if I´m not mistaken

  • Example LEVELS:



In both places the applicationID or GUID is not available

Thanks for the help,

Marco

Hey @MGark ,

In v3 connectors, we haven’t scoped Level objects yet. So they only exist as a property on an elements (e.g. Revit wall has a level property and it’s value is the level name).

Regardless, may I ask why you need those attributes? What’s your workflow?

cc @clrkng @oguzhan

A wip proposal would be to attach to the root commit object a list of level objects (which we can scope/port). This would be valid also for Archicad, and would enable a bunch of nice navigation aids in the viewer too. Could be crossreferenced with the collection (root commit object structure) levels. I’m hesitant to call them proxies, but it’s probably that.

To be discussed with @oguzhan and @clrkng :slight_smile:

@MGark we can temporarily fix this by adding the level applicationId to the properties dictionary on the Level Collection (which currently contains elevation), or alternatively to the applicationId of the Level Collection

But yes, @dimitrie I’m inclined to add Levels as proxies, this will also help in Revit/Archicad → Sketchup where levels are created.

2 Likes