This looks pretty cool.
What most caught my attention was the automated creation of clipping volumes per type. That got me wondering if something like this could be the start to eventually have automated quantity schedules with reference views, like the door quantity schedules as illustrated by Prince_01 in https://community.osarch.org/discussion/comment/25533/#Comment_25533
If they could be axis aligned to some pre-determined local axis, that seems to solve at least part of the problem of creating views of each occurrence.
@duarteframos said:
This looks pretty cool.
What most caught my attention was the automated creation of clipping volumes per type. That got me wondering if something like this could be the start to eventually have automated quantity schedules with reference views, like the door quantity schedules as illustrated by Prince_01 in https://community.osarch.org/discussion/comment/25533/#Comment_25533
If they could be axis aligned to some pre-determined local axis, that seems to solve at least part of the problem of creating views of each occurrence.
Interesting. I'm not sure this feature should be integrated with the clip box system though but I think we can rather easily extract any representation (3D, plan view, elevation view) for specific models. Bonsai already uses a system to generate icons for types on the fly using the type manager, maybe it's a matter of streamlining this part of the app and extracting relevant rendering capabilites to generate some kind of type-representation atlas, and dimension lines can be inferred from the bounding box, types should be axis-aligned anyways. We may want to split this thread to be able to follow it more easily (IDK how to ?), or would you mind creating an issue on github so we can track it there ?
You are probably right. I was thinking in terms quantity schedules for products that aren't necessarily a single element or type (aggregates, etc), or maybe having them rendered "in context" in the building, rather than isolated. Either way the icons system sounds more adequate indeed.
Sorry for the offtopic, I think only moderators can split threads. Do you mean to have me open an issue on Github for automatic graphic representations for schedules? Is this the correct repository? https://github.com/IfcOpenShell/IfcOpenShell/issues
I think it's alright to keep it here, before jumping into implementation we need to have a consensus on how it should work. I am certain we can work something out, but since this is not something I'm familiar with I do need some real world concrete examples of target deliverables on real world projects, as I feel what you have in mind is a bit more complicated than just rendering an occurrence from top and side view. Cheers
@Gorgious said:
I feel what you have in mind is a bit more complicated than just rendering an occurrence from top and side view. Cheers
Indeed it is, and it is way above my head.
From the top of my head I'd imagine a system like this would ideally start with some sort of "filtering system", where one would define some sort of scope for the elements to present in the schedule. Something like "All doors from the 3rd floor", or "all concrete beams from building 3", or maybe something more complex like "aggregates which contain certain material and are not inside some zone". The current querying systems would probably suffice for this.
After gathering those we'd probably define which types of data to present in the table-like view, like dimensions, descriptions, materials, or other arbitrary properties. Also which graphical representations to include, like separate front view, elevations, sections, a 2 or 3 way projection group.
Then somehow generate the table layout and fit it into pages of specified size.
Seems like quite an involved thing to accomplish, maybe start simple and break it down into phases.
I'll let some experienced stakeholder establish these basics, I'm way out of my depth here.
Comments
This looks pretty cool.
What most caught my attention was the automated creation of clipping volumes per type. That got me wondering if something like this could be the start to eventually have automated quantity schedules with reference views, like the door quantity schedules as illustrated by Prince_01 in https://community.osarch.org/discussion/comment/25533/#Comment_25533
If they could be axis aligned to some pre-determined local axis, that seems to solve at least part of the problem of creating views of each occurrence.
Interesting. I'm not sure this feature should be integrated with the clip box system though but I think we can rather easily extract any representation (3D, plan view, elevation view) for specific models. Bonsai already uses a system to generate icons for types on the fly using the type manager, maybe it's a matter of streamlining this part of the app and extracting relevant rendering capabilites to generate some kind of type-representation atlas, and dimension lines can be inferred from the bounding box, types should be axis-aligned anyways. We may want to split this thread to be able to follow it more easily (IDK how to ?), or would you mind creating an issue on github so we can track it there ?
Cheers.
You are probably right. I was thinking in terms quantity schedules for products that aren't necessarily a single element or type (aggregates, etc), or maybe having them rendered "in context" in the building, rather than isolated. Either way the icons system sounds more adequate indeed.
Sorry for the offtopic, I think only moderators can split threads. Do you mean to have me open an issue on Github for automatic graphic representations for schedules? Is this the correct repository? https://github.com/IfcOpenShell/IfcOpenShell/issues
I think it's alright to keep it here, before jumping into implementation we need to have a consensus on how it should work. I am certain we can work something out, but since this is not something I'm familiar with I do need some real world concrete examples of target deliverables on real world projects, as I feel what you have in mind is a bit more complicated than just rendering an occurrence from top and side view. Cheers
Indeed it is, and it is way above my head.
From the top of my head I'd imagine a system like this would ideally start with some sort of "filtering system", where one would define some sort of scope for the elements to present in the schedule. Something like "All doors from the 3rd floor", or "all concrete beams from building 3", or maybe something more complex like "aggregates which contain certain material and are not inside some zone". The current querying systems would probably suffice for this.
After gathering those we'd probably define which types of data to present in the table-like view, like dimensions, descriptions, materials, or other arbitrary properties. Also which graphical representations to include, like separate front view, elevations, sections, a 2 or 3 way projection group.
Then somehow generate the table layout and fit it into pages of specified size.
Seems like quite an involved thing to accomplish, maybe start simple and break it down into phases.
I'll let some experienced stakeholder establish these basics, I'm way out of my depth here.