If I recall correctly, the tower will report channel information to the higher up controller system which will then decide which next tower should be notified of a phone that’s entering its range.

So while explicit positioning isn’t required when dealing with one tower, the system overall does need to determine a users position and velocity to handle tower to tower transfers.

In other words my opinion is that the difference between a towers channel information and a users position is almost one and the same. It’s a handful of math equations away.

If anyone wants to look at the future of 5G (well ORAN) here it is: https://gitlab.eurecom.fr/oai/openairinterface5g

When talking about the 5G system, cell towers can request a users estimated velocity which when combined with the towers own location combined with the physical radio (that is communicating with the phone (UE)) you can get a pretty good position estimation.

What is new is that network providers are trying to sell this tower/5G data to other companies.

I could be wrong but from my understanding 5G has always required precise tracking of every device connected.

From my understanding Embassy and RTIC are two different models of concurrency so I’m not sure of any benefit of using both at the same time.

I’ve been thinking of making a native map and globe program similar to Google earth to embed inside a dashboard (visually similar to kerbal space program).

So far I was thinking about just using ArcGIS (or something else) and taking in free Lidar data and imposing the depth to satellite or OSM tiles then rendering them as OBJs in OpenGL (or maybe a full 3d engine like unity). This unfortunately wouldn’t be an automatic process as lidar data is taxing to process in real time, especially for a SBC.

I do see that there are some 3D tiles sets out there but I don’t see where I can pull them from nor how it compares to the lidar data.

However, the main goal is a 3D terrain viewer in an offline native program.