buildingSMART / buildingSMART/IFC4.x-development
BINARY data is not optimal
Open
ifc-update-out
- Dominant language
- Python
- Stars
- 234
- Forks
- 123
- Avg merge
- 15h 4m
- Merged PRs (30d)
- 5
Description
I am working with user request to support texture and was surprised (if I understood correct)
EXPRESS ISO 10303-11-2000 and SDAI ISO 10303-24-2001
define to store BINARY data as text string like "%0101001100" - character per bit
136 binary_literal = '% ' bit { bit } .
119 bit = '0' | '1'
Is it really good way to store textures? -:)
Can we change to base 64 like we have for GUIDs?
Contributor guide
Assessment
This issue has not been assessed yet.