Georeferencing metadata missmatch - PCERT examples for IFC4.3.2.0

# State

Looking at

https://github.com/buildingSMART/Sample-Test-Files/blob/5016207e14159f2fcf60d6f4dddfedfb7d2e0994/IFC%204.3.2.0%20(IFC4X3_ADD2)/PCERT-Sample-Scene/Infra-Bridge.ifc#L25

with

https://github.com/buildingSMART/Sample-Test-Files/blob/5016207e14159f2fcf60d6f4dddfedfb7d2e0994/IFC%204.3.2.0%20(IFC4X3_ADD2)/PCERT-Sample-Scene/Infra-Bridge.ifc#L22


while considering the definition of the referenced CRS [32760](https://epsg.io/32760):


I wonder:

# Question

Shouldn't the unit of the `IfcProjectedCRS.MapUnit` be a metre, and not a millimetre?

This applies to all example files [here](https://github.com/buildingSMART/Sample-Test-Files/blob/5016207e14159f2fcf60d6f4dddfedfb7d2e0994/IFC%204.3.2.0%20(IFC4X3_ADD2)/PCERT-Sample-Scene/).

Start with the linked Infra-Bridge.ifc lines 22 and 25 in the PCERT-Sample-Scene directory, compare the MapUnit with EPSG:32760, and inspect the other example files linked in the issue. Confirm the expected unit and update every affected PCERT example, then verify that their georeferencing metadata is consistent.

Written by the indexing model from the issue text.