Follow
May I just take a moment to point out that RFC 7946 the GeoJSON Format spec
https://tools.ietf.org/html/rfc7946
fundamentally encodes a bad "definition" cause "that's the way it's always been done".
Point and Position. A Point is defined as the x and y, a Position is defined as X, Y, & Z... BUT the Z is optional, and Time is explicitly disallowed.
If I tell you to meet me In New York at Times Square but I don't tell you "when" I'll be there, then I'm not giving you a position.