Thomas Beutlich
Thomas Beutlich
Using v3.6.3, I noticed that the generated SBOM is just a single-line file, thus not diff-friendly. Is there any reason to not have a pretty-printed output file generated?
Please check if the references from IfcStyledItem etc. to deprecated `IfcStyleAssignmentSelect` still hold. > IFC4 CHANGE The data type has been changed to IfcStyleAssignmentSelect with upward compatibility for file based...
**Describe the bug** ==1989==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x602000004b58 at pc 0x000000bdf5f9 bp 0x7fffd47546d0 sp 0x7fffd47546c8 READ of size 1 at 0x602000004b58 thread T0 # 0 0xbdf5f8 in H5T__bit_find [hdf5/src/H5Tbit.c:0](https://github.com/HDFGroup/hdf5/blob/c5c4713a9a0c940a6d20daad1152a3fc80b4fec5/src/H5Tbit.c#L0):20...
See https://github.com/thbeu/IFC/actions/runs/8493164593/job/23266945144 for a test run. It also reveals that there is some issue with the UTF-8 BOM as already reported,
From what I have checked it's the only example.
Some example files have a note to update the schema version, but this seems to be no longer necessary. For example https://github.com/buildingSMART/IFC/blob/fedaf6da480e86ee725693dd88a4c87e89fd5826/Examples/Basic%20geometric%20shape/Examples/Extruded%20solid/File.ifc#L18-L19
Neither necessary nor desired.
Now that gdal 3.8.5 is released and bundles the latest shapelib fixes, it would be appreciated to also have a new stand-alone release of shapelib containing theses fixes. Thanks. By...