Issue: IFC Door Parsing via JuPedSim Checkpoint Polygons

[ProfRino]

Dear team

I have a suggestion on the door tool.
My advice is to have a door as a line where the line length represents the opening length. The line can be inserted online on the edges of boundaries or obstacles.

Here is an example of how doors can be moved to perfect positions in Blender BIM (Bonsai). The strategy is to locate the door in a rough position, then grab it and locate it in the exact location as shown here at the time: 10:48
https://www.youtube.com/watch?v=fxpIg-su-00

The door should also allow some parameter to define constraints on the floor rate.

Finally, the door can also be automatically created when importing BIM as there are ifcDoors in IFC files

Please let me know if I am not clear :)

Thanks for your work!
Rino

[chraibi]

Doors in JuPedSim do not exist. But we can work with "Checkpoints" as thin Polygons instead. This is already implemented.
Just the parsing is missing yet.
Can you upload a simple example ifc with Door?

[chraibi]

Description

To support architectural workflows and BIM integration, we need to implement a parser that converts ifcDoor entities from IFC files into JuPedSim Checkpoints. Since Checkpoints are already implemented as thin Polygons, the task is to automate their placement and configuration based on BIM data.

Current Behavior

• Checkpoints (thin Polygons) are functional in the engine but must be created manually.
• IFC imports do not currently recognize or translate door entities into simulation objects.

Expected Behavior

• Automated Extraction: Upon IFC import, the system identifies all ifcDoor elements.
• Geometry Translation: Each door is converted into a "thin Polygon" Checkpoint aligned with the wall's opening.
• Line-Based Logic: The Checkpoint's primary axis should match the door’s "Line" representation, where the length equals the opening width.
• Parametric Sync: Attributes like flow rate or door name should be mapped from IFC property sets to the Checkpoint metadata.

Technical Implementation

• IFC Parser Update:

• Filter for ifcDoor classes.

• Extract the Location and OverallWidth parameters.

• Generate a thin Polygon (Checkpoint) centered on the door's insertion point.

• Coordinate Alignment:

• Use the wall's normal vector to ensure the Checkpoint polygon is perpendicular to the flow direction.

• Align the Checkpoint precisely with the boundary edges of the wall opening.

• Parameter Mapping:

• Map ifcDoor properties to JuPedSim-specific attributes.

• Implement a field for Flow Rate Constraints within the Checkpoint properties panel.

BIM-to-Sim Workflow (Reference)

The strategy for precise positioning should mimic the "Grab and Slide" workflow from Blender BIM (Bonsai), allowing users to fine-tune the Checkpoint's location along the boundary.

Acceptance Criteria

1. Importing a BIM file automatically generates Checkpoints at every door location.
2. The generated Checkpoints are correctly sized based on the ifcDoor width.
3. Users can manually adjust these Checkpoints using a "line-based" slide tool on wall edges.
4. The simulation successfully records egress data (agent counts/times) passing through these imported Checkpoints.

[ProfRino]

Apologies, I meant Exit and its drawing tools.
At the moment, the existing tool allows for drawing a rectangle. As it is challenging to use the tool, I am suggesting to have only a line instead of a rectangle.

Here is a simple IFC example with ifcdoor(s)
https://masseyuni-my.sharepoint.com/:f:/g/personal/rlovregl_massey_ac_nz/IgAsLme7zLhSQ5CQe8e3_CAzAZTeLvgN_vCwGbs-6L4YiFc?e=SuHpMO

Thanks
Rino

[ProfRino]

Here an examples on how the exit/door tool in Pathfinder
It would be great to have something like it
https://www.youtube.com/watch?v=93YVpSvlJOs

Thanks team
Rino

[chraibi]

@ProfRino Let me think about this. I'm not sure if we should mimic Pathfinder, Bonsai or CAD-tools in terms of editing capabilities. This would defy the purpose of jupedsim.
Best, is always to use one of these sophisticated tools to edit the scenario and just import it to the app.
Editing capabilities should only be helpful but won't be complete.

Will reflect on this some more..