@Mike_S , This is not officially announced yet, but it potentially looks like H3 resolution 5.
This is what I’m seeing from our test lab Starlink account.
I suppose it should be similar to what we’ll find in the Starlink account.
I should have included this information in my previous reply so everyone has better context on the H3 resolution. I think this helps make the use case more understandable from the engineering perspective.
I think it’s still useful, but it should be display as h3cellid, shown on the map with a h3 hex drawn around it, and an optional google maps link to the coordinates. (H3 cellid approximant , lat/lon) as an example.
Further is the h3cellid available via GRPC or only via v2 starlink api?
It’s important that it’s not relied on and look at like accurate gps.
@Jonathan_Pitts , The location information is only available via the Starlink API. Could you share more details about your use case and how this information would help with your deployment?
