Dion Moult

If #323 is solved, here is a revised proposal for the property description: > NOTE If a geographic placement is provided using [IfcMapConversion](http://localhost:5000/IFC/RELEASE/IFC4x3/HTML/lexical/IfcMapConversion.htm) then the true north is for information...

@pjanck sure, that makes sense, but that means that we need to add lat/longs as described in #323 as attributes somewhere too (either on the context, or map conversion). It's...

@pjanck lat/longs are calculated at a particular easting / northing, just the same as true north (note, we are talking true north here, not grid north, which is given by...

> ... and not "I have this use case, where to find information required - add/amend the documentation". FYI @TLiebich summarises the history of lat longs [here](https://github.com/buildingSMART/IFC4.3.x-development/issues/323#issuecomment-1055718633) - this usecase...

@TLiebich maybe it is not decided. I only heard about it in #317 and assumed it was an infra addition.

Given that the whole IfcActor part of the schema is increasingly important in non-geometric usecases, and people are waking up to the fact that BIM isn't just geometry with properties,...

The issue is that for the most part MLS matches how architects and wall manufacturers design and specify things. They don't bother with the details of every single stud or...

Ok, note to self that I need to fix the auto linking code then :)

How urgent is this for the release? If we get an approach confirmed I'm happy to hack on it. I would personally not use the overhead of a Redis db,...

Hahaha yes that's me being lazy copy pasting text and Github being clever. That might work if it were extended, like outer / inner diameter and shape, and then potentially...