Catenda hosted the BCF Hackaton in Bergen

Earlier this year yet another successful BCF hackaton took place. This time it was hosted by Catenda at the Vil vite center in Bergen, Norway.

The main focus for the meeting was to resolve the remaining issues for the upcoming BCF API 2.0 specification as well as the corresponding BCF API. Quite a few test-cases was prepared and tested during the meeting:

  1. openings and spaces, and space groups and nothing visible or invisible -> Should show openings and spaces as invisible. (Yoram)
  2. multiple viewpoints without comments -> ordering (Rahul)
  3. comments without viewpoints (Yoram)
  4. lines (Rahul)
  5. bitmap (Rahul)
  6. clipping planes (Rahul)
  7. extension schema (Georg)
  8. minimum information (no optional data) (Georg)
  9. maximum information (all optional data) (Georg)
  10. perspective camera (Pieter)
  11. orthogonal camera (Pieter)
  12. multiple topics (Rune)
  13. visible space and the rest of the model visible (Rahul)
  14. single visible space and nothing else (Yoram)
  15. single visible wall (Rune)
  16. single invisible wall (all other components visible) (Jon)
  17. visible opening (Rahul)
  18. visible space boundary (Rahul)
  19. one component visible from a decomposed object (e.g. curtain wall) (Pasi)
  20. all components except one visible of a decomposed object (Pasi)
  21. document reference to external url (Pieter)
  22. document reference to internal url (Pieter)
  23. component selection (Pieter)
  24. component coloring (Rahul)
  25. header with no files (Yoram)
  26. header with one file (Yoram)
  27. header with multiple files (Yoram)
  28. related topics with both topics in the same file (Jon)
  29. related topics with the other topic missing (Jon)
  30. internal BIMsnippet (Georg)
  31. external BIMsnippet (Georg)
  32. a pdf file (Georg)
  33. user assignment (Jon)

During the meeting DDS and Tekla successfully carried out a complex mixed BCF scenario using both BCF files and the BCF API for the exchange. First a few request for HCAC openings in structural elements (provision for void) was sent by DDS to bimsync using the newly implemented BCF API. From bimsync the Tekla Structures representative made an BCF file export (BCF 2.0) which was then imported to Tekla. The requested modifications where made and an updated BCF and the modified IFC file was uploaded to bimsync. DDS then updated the issue through the API confirmed that the problem was resolved and closed the issue in bimsync where the Tekla representative was informed by email that the changes was accepted. If both parties would have used the BCF API the whole exchange scenario would have been resolved on a fraction of the time.

We can´t wait to see more programs implementing support for the BCF API as it will be a key factor to bring down the costly latency from a request is sent to someone to a resolution is found.

Comments are closed.

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑