It's kind of funny, because exploration is an act of exploring unknown area. Meanwhile OP wants a map of that area first.
Exactly. We can see the stars, we know what's been explored. [known] - [explored] = [unexplored]. This would seem to be possible.
That is literally what was done to generate the exploration "saturation" map linked in the second post in this thread.
First, that site is f***ing awesome. I'm not saying it's not.
However, I think my intent is being completely misinterpreted.
The sat map appears to show % explored/density. That means that there is a reasonable expectation that the number of stars in that region is (roughly) known.
[# explored/total # stars] / [total # stars/size of region] = [# explored * size of region] / [total # stars]^2. The units would be volume / # of stars, so m^3 / # stars. This uses the actual number of stars.
In order to determine the total # of stars, as the sat map does, the database has to know the # of explored stars and the total # of stars. Therefore, it should be possible to show [total - explored] to get # of unexplored stars.
What I'm looking for is {[total # stars] - [# explored]} / size of region. The units would be # stars / volume. The units are inverted, so the sat map is clearly not the map I am looking for.
I'm not looking for a % saturation. I'm looking for actual unexplored star density. The purpose is obvious. What areas have the highest density of unexplored stars, so that we can focus there for exploration?
I just want a reverse map so that we can look at the bright areas and target those. Aiming for dark areas is counterintuitive and
inaccurate on a black site background.
I'm not sure what the disconnect is. I kinda feel like this would be broadly beneficial.