Andy Ward

It would be great if you can supply a test for this. I know you can't share the model, but if you know the element triggering the issue, you can...

Definitely worth checking out the v6 GE ([netcore branch](https://github.com/xBimTeam/XbimGeometry/tree/feature/netcore)) if you have problematic models - it has quite a few fixes around precision. As you noticed it's key to a...

@martin1cerny or @SteveLockley is probably a better authority on this than me - especially on WCS & geo-referencing. But having a precision of nanometers when dealing with large coordinates is...

Thanks for this detailed investigation! Any chance you can submit as a PR rather than a patch? Ideally you'll add a quick test using your stripped model (that'll help ensure...

> The 'Identifier' should be the place for that. Why do you find it 'not strictly machine readable' and how we could improve that in 1.1? In the schema annotations...

This sounds a bit similar to #331 - but we didn't get an authorative decision. I proposed a third possible solution: to permit some kind of alias. So IFCLABEL is...

Yes it's unclear if dataType is optional or not. I believe the schema now leaves it optional (As per last comment in 206) but the audit-tool still treats its omission...

>It seems reasonable that constraints on values come after the choice of the data to expect. Just as a counter argument, take a scenario that requires a length property to...

Agreed it gets complex when the datatype is specified we want to honour the IFC semantic in the tests. Clearly IFCLENGTHMEASURE(1.0) != IFCAREAMEASURE(1.0) despite both being backed by the same...

@ido-cu Do you want to send us the problem file (via a fileshare/sharepoint/dropbox/wetransfer etc)? My xbim email is on my GH profile. We're doing final regression on the V6 Geometry...