Dion Moult

I would love to get this one in and finally (or at least, much closer to finally) wrap up a lot of geolocation confusion - upgrading to proposal since it's...

One more reminder: we still haven't actually solved the initial issue of this bugreport ... what is the EPSG code of WGS84? Is it just EPSG 4326? This is the...

Thanks @pjanck ! Would be good to get another geoferencing expert to confirm the epoch choice. It seems there are quite a few out there.

@TLiebich in [another post](https://github.com/buildingSMART/IFC4.3.x-development/issues/315#issuecomment-1059933523), @pjanck makes an excellent point that a pset may not work very well because latlongs and north are sampled at a particular easting and northing, but...

@aothms unfortunately the placement is no longer enough. In the past, when the georeferencing user-guide only talked about one map conversion, life was simple: you just get follow all your...

@TLiebich it was news to me as well in #317 when @pjanck mentioned it. I thought I was simply not aware of the change. My view is that if we...

I 100% agree. I vote to fix existing behaviour with the assumption of one map conversion. With that assumption, all the existing proposals make sense. For IFC5 if things develop...

Oh, discovered it on IfcSlab too. So I propose to delete this too: > NOTE  An arbitrary planar element to which this semantic information is not applicable or irrelevant shall...

Ah right, so since there is a new vehicle subtype, I think these properties may not necessarily make sense anymore. For example there is `FireExit` which works for Fire Lifts,...

My preference in the short term and not a domain expert is to change the applicability to IfcTransportElement because 1) it used to be there, so to the best of...