Found myself wondering what kind of data structure you'd need for representing fine geometry on the scale of a world-sized "metaverse." Naively, assuming you want micrometer scale… 1° ~ 1e5m => precision to 1e-11°; i.e. lat/long must distinguish ~1e13 values. A double suffices!
Conversation
Replying to
(Of course, in practice, I'd guess geometry positions would be represented at runtime with cartesian coordinates relative to some local "sector" reference frame, so you could probably just use a float)
4
6
Replying to
tangentially related, Uber developed a system of nested hexagons to represent space:
5
2
52
Replying to
USD has emerged as the primary standard. Pixar invented it but it’s now been adopted in many places, including .
1
1
I tried looking up USD and only saw spatial audio references...?
1
Show replies
Replying to
Kerbal Space Program 2 has to address this problem from mm scale to interstellar distances; see for example kerbalspaceprogram.com/dev-diaries/de
1
3
Ah, very interesting! And I see they use a hierarchical reference!
Replying to
Just for background, Parasolid (and before that the FORTRAN era Romulus) has used these numbers since the early 80s:
linear-precision: 1e-8m
size-box: 1000m X 1000m x 1000m
⇒
angular-precision: 1e-11 radians
Some info here:
1
1
Obviously, not a solution at all, and IIRC, even though the size-box sounds large enough, it caused problems for the Super Collider.
I think about this question too, and its fascinating to read the other replies about Uber, the Kerbal Space Program, ...
1
