Autodesk
IfcStairFlight doesn't export the IfcSlab.FLOOR it should be connected to
I'm currently testing REVIT capabilities to export in IFC and it's pretty convenient to use. But I think there is one important feature missing when exporting an IfcStair.
The exporting of an IfcStair as an aggregation of components that describe the stair is perfect and follow what's described inside this document MVC-696.
But if you look at the description of an IfcStairFlight.
An IfcStairFlight normally connects the floor slab of zero to two different storeys (or partial storeys) within a building. The connection relationship between the IfcStairFlight and the IfcSlab is expressed using the IfcRelConnectsElements relationship.
In fact this information allow the user to know from which IfcSlab the stair is starting and to which slab it leads. Without this information you can't navigate inside the building properly.
Is that the kind of feature you are planning to implement or is it something out of the scope of the Revit-Ifc plugin ? (My understanding of IfcStairFlight might also be wrong)
There is multiple way you can handle this connection outside of REVIT. Like 3D proximity between the IfcStair representation and the IfcSlab.FLOOR representation. But it would be perfect if REVIT was able to handle this kind of situation by himself
I'm trying to do the same thing. I set: IfcExportAs = 'IfcStairflight' IfcExportType = 'WINDER'.
In IFC I get Ifc Entity = IfcStairFlight Ifc Type = IfcStairFlightType But no predfined Type. Instead it is exported as NOTDEFINED:
#77538= IFCSTAIRFLIGHTTYPE('33Q6LdtALDQOHj$rhuoklS',#41,'24_dubbelkwart_220x187,5x1300',$,$,(#77617,#77619,#77628,#77632),(#77536),'2750402',$,.NOTDEFINED.);
Those seem like two separate issues. @MennoMekes can you provide a simple Revit file that shows your issue? The first one has an internal improvement.
Hi Angel,
Here’s the link with a revit file and the exported IFC: https://we.tl/t-hrKtl0ksbr
So we don’t use the Revit-stairs but model them as Generic Models. We build out stairs detailled and the way the manufacturer can build them. Also we design stairs that can have 3 to 4 threads on a winder. I would very much like to be able to export them correctly. And create an element assembly out of a StairFlight.STRAIGHT and a IfcSlab.LANDING the way the built-in revit funciotnality works.
Exporting a Revit assembly to an IfcStair is also not possible?
Met vriendelijke groet,
Menno Mekes
[AG_logo_email] arons en gelauff architecten gedempt hamerkanaal 92 1021 kr amsterdam nl t. +31 20 423 55 30 www.aronsengelauff.nlhttp://www.aronsengelauff.nl/ We zijn trots dat de Pontsteiger in de categorie woningbouw is genomineerd voor de Nationale Staalbouwprijs 2020. Het hooggelegen brugdeel van ons 92 meter hoge woonikoon is een meesterproef van engineering (van Rossum) en uitvoering (Buiting Staalbouw, Dura Vermeer en MJ de Nijs). De stalen brugconstructie rust op twee woontorens van 60 meter hoogte en overspant bijna 50 meter. De staalconstructie gaf ons de indelingsvrijheid om met de kopers hun appartementen naar eigen inzicht in te delen. Geen van de 66 appartementen in de brug is gelijk! De winnaars van de tweejaarlijkse Staalbouwprijs worden bekend gemaakt op 13 oktober. https://aronsengelauff.nl/news?lang=nl
dit e-mailbericht is uitsluitend bestemd voor de geadresseerde(n) en kan informatie bevatten die persoonlijk of vertrouwelijk is en niet openbaar mag worden gemaakt - indien dit bericht niet voor u is bestemd, wilt u dan zo spoedig mogelijk arons en gelauff architecten hiervan berichten - arons en gelauff architecten staat niet in voor de juiste en volledige overbrenging van de inhoud van een verzonden e-mailbericht, noch voor tijdige ontvangst.
Van: AngelVelezSosa [email protected] Verzonden: dinsdag 25 augustus 2020 14:36 Aan: Autodesk/revit-ifc [email protected] CC: Menno Mekes | Arons en Gelauff [email protected]; Mention [email protected] Onderwerp: Re: [Autodesk/revit-ifc] IfcStairFlight doesn't export the IfcSlab.FLOOR it should be connected to (#146)
Those seem like two separate issues. @MennoMekeshttps://github.com/MennoMekes can you provide a simple Revit file that shows your issue? The first one has an internal improvement.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/Autodesk/revit-ifc/issues/146#issuecomment-679997707, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AP4XCUL54GS4P4A5ISNXYZ3SCOV37ANCNFSM4JVMIX7Q.
This issue is also reported in Jira as "REVIT-240244" and is currently in the "Open" status.
