starlink-grpc-tools VS open-location-code

https://github.com/sparky8512/starlink-grpc-tools - Cant seem to get this to work with docker-compose and influxdb2.8

I'm guessing you've already looked at the debug in the SL app. This is a good reference on what the debug lines mean. https://github.com/sparky8512/starlink-grpc-tools/blob/main/starlink_grpc.py

If you want to get really detailed there's a gRPC endpoint in Dishy with a whole lot of debug data you can look at. See these dashboards for instance. I set all this up a long while back but stopped using it, partly because it's not easy and partly because a Ubiquiti bug makes it hard for me to get at the data.

BoresightAzimuth&Elevation in the debug data are not virtual. That's where your dish points physically. I was told in the beginning (2020 - early 2021) dish shared via grpc the serving satellite number and it showed if the connection was prescheduled or fallback but they hid that api from public access. The only way to see what satellites dish connects to is to observe obstruction map filling up after a cold start. The dish doesn't know about obstructions after a cold start though.

You can use Starlink's API to pull data and statistics, you can find some tools at https://github.com/sparky8512/starlink-grpc-tools/

I found a good one on GitHub. https://github.com/sparky8512/starlink-grpc-tools/blob/main/starlink_grpc.py

Have a look at https://github.com/sparky8512/starlink-grpc-tools

Pluscode is a trademark. The actual standard is called "open location code" and is unrestricted - https://github.com/google/open-location-code/

Yeah, that seems like a bad design choice. If you look at the spec [0], you can see that they only use "23456789CFGHJMPQRVWX" in the codes. They apparently scored the letters based on how well they can spell 10000 words in 30 languages, without thinking about character similarity. If they had involved actual humans instead of counting letter frequency, they might have noticed that the letter W looks similar to VV, and that its English name is "double U". And tried a letter like N or Y, which would be much harder to confuse.

[0] https://github.com/google/open-location-code/blob/main/docs/...

Lots of thoughts from the founders incl comparison with other systems here: https://github.com/google/open-location-code/wiki/Evaluation-of-Location-Encoding-Systems

It's licensed Apache 2.0 https://github.com/google/open-location-code

I wish https://plus.codes/ took off. The benefit compared to what 3 words is that you can use the closest city to give directions and cells next to each other share the bigger cell name.

And an additional shoutout for https://plus.codes/ from Google.

New to this so sorry if this is stupid. I've been trying to use https://plus.codes to try to check an address for availability at starlink. Whatever code I put in, it simply tells me afterwards "please enter an address or a plus code". That website seems to give me either a shorter or a longer plus code. Neither of them seems to make the starlink website happy. When I try putting in the address, it doesn't like that either. Confused on where to go from here.