New Feature : Light Pollution / Sky Brightness Measurement

All the latest news about new features and improvements to SharpCap
Post Reply
User avatar
admin
Site Admin
Posts: 17571
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

New Feature : Light Pollution / Sky Brightness Measurement

#1

Post by admin »

Hi folks,

I hadn't really planned this feature for 4.2, but I started thinking about light pollution measurement, Bortle numbers, etc, and realised that this could all be calculated based on captured images, sensor analysis data and three more things...

* A 'Quantum Efficiency' or QE value for the imaging sensor and
* The F-ratio of the telescope being used and
* The optical efficiency of the telescope system (what percentage of light makes it from the entry of the telescope to the imaging sensor)

Fortunately these figures are fairly easy to find out, or estimate. For instance the QE for modern sensors is probably about 80% (in the most sensitive green part of the spectrum anyway). Camera manufacturers often give a QE graph showing how it varies with wavelength which you can consult.

The f-ratio is just the focal length of your telescope divided by the aperture. Don't forget to include the effects of any barlow lenses/reducers/teleextenders in the calculation. It's probably a good idea to use plate solving to measure the effective focal length of your imaging system, since it doesn't always exactly match the published values!

Finally, the optical efficiency for modern telescopes is usually pretty high (95% or more), due to the use of multi-coated optics to reduce reflections from glass surfaces and highly efficient mirrors.

How to use it

So, how does this work in SharpCap? Well, you will find a new tool in the 'Tools' menu called 'Light Pollution Measurement'. You can activate this with any camera open, but to get readings you need to meet the following conditions...
  • The camera must be in a high bit depth mode (10/12/14/16 bit) - You can't use 8 bit modes for this feature
  • There must be sensor analysis data available for the camera, either installed by default as part of SharpCap's sensor library, or by running the separate sensor analysis tool.
  • Dark subtraction, flat correction and other image processing tools should be turned off, so the tool can process the image straight from the camera sensor. Activating the tool will disable image processing in SharpCap while the tool is active to try to enforce this.
  • The camera must provide information on the pixel size and accurate exposure length - most dedicated Astronomy cameras do this, but industrial cameras tend not to provide the pixel size (Basler, Point Grey, Imaging Source/Celestron). Additionally webcams do not provide pixel size, but they cannot meet the high bit depth requirement either.
For good results, you should also ensure that any colour balance controls for your camera (usually called WBR/WBB/WBG) are set to their 'neutral' positions where they are not changing the image data.

With all of these conditions satisfied, you will start to see sky brightness data shown both in the summary area at the bottom and overlaid on the image as a contour plot.
Screenshot 2026-08-24 154819.png
Screenshot 2026-08-24 154819.png (54.24 KiB) Viewed 1163 times
Screenshot 2026-08-24 154827.jpg
Screenshot 2026-08-24 154827.jpg (368.74 KiB) Viewed 1163 times
By default, the brightness is shown in units of electrons per pixel per second (e/pix/s). This is a measure of the rate at which the sensor is accumulating charge due to the background of the image. This doesn't depend on the information like focal length of QE percentage, so is valid even if you haven't tweaked the settings yet.

It's much more useful to show the information in proper sky brightness units - Magnitudes per square arc second (MPSAS - what SQM meters usually show) or as an estimated Bortle number. Switching to these modes is as simple as selecting the appropriate radio button in the work area at the bottom, although you will need a SharpCap Pro license and also need to adjust the f-ratio, QE and light transmission values appropriately. I'll just point out here that a SharpCap Pro license is a lot cheaper than a dedicated hardware SQM device...

Switching to Bortle for example changes the contour overlay to show Bortle values, and also the status area gives you min/max/average brightness values in the selected unit.
Screenshot 2026-08-24 155514.jpg
Screenshot 2026-08-24 155514.jpg (281.06 KiB) Viewed 1163 times
Screenshot 2026-08-24 155542.png
Screenshot 2026-08-24 155542.png (36.97 KiB) Viewed 1163 times
Obviously, the values you see will depend on how dark it is (astronomical darkness/twilight/etc), local light pollution and also transparency (last night wasn't fully clear - I was getting down much closer to 5 rather than about 5.5 the night before). You also want to avoid areas with large nebulae or galaxies when measuring to get a decent measure of the true background.

How accurate is it?


The biggest issue is going to be not having an exact value for the QE percentage of your sensor - the QE typically varies with wavelength, and obviously the light collected by the sensor is of a range of wavelengths. Probably best to eyeball the manufacturer provided QE graph and try to pick a mean value over the range of wavelengths being measured. That being said, an error of 10% in the QE - ie using 72% when it is really 80% - only leads to a 0.1 MPSAS change in the sky brightness reading.

How is Bortle calculated?

I have used the values for 'Approx SQM' from the Wikipedia page for the Bortle Scale and interpolated between them. It's more 'estimated' than the MPSAS value.

Why the trailed stars in the screenshots?

I spent the whole evening yesterday from sunset to astronomical darkness with the telescope pointing at the zenith (not tracking), taking images every 2 minutes - trying to capture the progression of sky brightness during the whole twilight period. When I have the chance I will process the MPSAS data out of the images and compare to the semi-empirical twilight model I am using in other parts of SharpCap :)

Can you check old image data?

If your old image data was saved in FITS format using a recent version of SharpCap, and you had sensor analysis data at the time you saved the data then you will find headers like 'BIASADU', 'EGAIN' and 'EGAINSAV' in the fits files. Those provide the information needed to process the image data correctly when loaded from file. Load these images via the 'Folder Monitor' camera and you should be able to work with them using this tool.


cheers,

Robin
Gfischer
Posts: 323
Joined: Thu Jun 22, 2023 4:20 pm

Re: New Feature : Light Pollution / Sky Brightness Measurement

#2

Post by Gfischer »

Hi Robin,
I tried the new feature last night. The bortle 6.8 it came up with matches the 6-7 shown on online light pollution maps of my area. A quick question, is there any compensation for moon glow? A great new addition to Sharpcap!
User avatar
admin
Site Admin
Posts: 17571
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: New Feature : Light Pollution / Sky Brightness Measurement

#3

Post by admin »

Hi,

the feature will measure the brightness including the moon glow, but will not attempt to compensate for it (subtract it away from the measurement). So, if you want to know your true light pollution level, hold on and test one time when the moon is well below the horizon.

Good to hear that the measurement is in decent agreement with other sources - I think the best way to think of this tool is that it will give good relative accuracy (for instance measuring different nights using the same setup), but the agreement with other sources/dedicated SQM devices will only be approximate.

cheers,

Robin
roelb
Posts: 282
Joined: Wed Mar 08, 2017 11:36 pm

Re: New Feature : Light Pollution / Sky Brightness Measurement

#4

Post by roelb »

Observing location: Bortle 4 according to the "ClearOutside" app.
I have tested it with fits from past sessions (Folder Monitor Camera). The results:
no moon: Bortle 4
with moon: Bortle 5
As expected: open clusters with a lot of stars give lower Bortle values.
The same for nebulae.
So, this short test result is very positive.
A welcome addition to this excellent software.
Roel
Celestron Nexstar Evolution 8 with Celestron StarSense & Celestron Focus Motor
Celestron Origin Mark II
ASI533MC-Pro - ASI533MM-Pro
ZWO Seestar S50
CPWI - Stellarium - AstroPlanner - SharpCap Pro - N.I.N.A. - Siril
User avatar
admin
Site Admin
Posts: 17571
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: New Feature : Light Pollution / Sky Brightness Measurement

#5

Post by admin »

Hi folks,

I decided to invest in a proper Sky Quality Meter (Unihedron SQM-L) in order to test this feature against an independent (and calibrated) method of measuring sky brightness.

Results seem to be very good - I was using a 70mm F/5 refractor with the light transmission left at default 95%. The camera was a colour IMX571 (Player One Poseidon Pro). The values from the SharpCap measurement were within 0.1 magnitudes of the SQM-L values in almost all measurements during my test over several hours. When I did spot larger differences (up to about 0.2 mag), with a bit of thought I could see why they might be happening...

1) Watch out for any local lights near the telescope (computer/monitor/keyboard LEDs or LEDs on devices/USB hubs/etc). I have a side-by-side setup and a solar scintillation monitor attached to the scope next to my deep-sky scope. That had a green LED which wasn't that bright but was only 6 inches from the aperture of the deep sky scope - unplugging that device helped close the discrepancy that opened as the sky got properly dark

2) The Unihedron measures across a field of view of about 18 degrees - with my setup, SharpCap is measuring across something like 2 or 3 degrees. That means that the SharpCap reading is more affected by local effects - a bright or a dark patch of sky - regardless of whether the brightness is from stars, nebulosity or just a little blob of thin cloud

I was mostly testing over the range from about 19 to 20 mag per square arc second, I will have to try to start earlier next time to catch a wider magnitude range (we don't get darker than about 20 MPSAS here, so I am stuck at that end of the scale). I'd also like to check out the values from a mono camera too - currently I am using colour and calculating from the green channel (scaling up by a factor of 3 to account for light in the other two channels). It would probably be better to estimate all 3 channels but that would really need to account for the typical lower sensitivity of cameras as you move out of the optimal green part of the spectrum.

Overall though, the readings are very promising :)

cheers,

Robin
User avatar
admin
Site Admin
Posts: 17571
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: New Feature : Light Pollution / Sky Brightness Measurement

#6

Post by admin »

I have made some updates to this which you will find in the latest SharpCap 4.2 beta build (4.2.15246).

* Statistics for all three measurement units are now visible at once, although the contour plot still only shows in the unit you have selected
Screenshot 2026-10-12 144017.png
Screenshot 2026-10-12 144017.png (22.5 KiB) Viewed 415 times
* For colour cameras, the code now measures and combines all three colour channels, producing a single measurement to cover the whole spectrum in the way a more traditional SQM meter would. In order to give good results, the QE% for colour cameras should be set a bit lower now - instead of 80% representing typical efficiency in the green part of the spectrum, maybe about 70% as some sort of average efficiency over a wider range is more appropriate.

Note that unfortunately I forgot to remove the 'channel' selection dropdown that let you previously choose R/G/B measurements - because the code now measures all 3 channels, this now does nothing. I will remove in the next update.

cheers,

Robin
User avatar
admin
Site Admin
Posts: 17571
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: New Feature : Light Pollution / Sky Brightness Measurement

#7

Post by admin »

Hi folks,

I have just uploaded a new 4.2 beta version (4.2.15384) with a significant enhancement to the light pollution measurement tool :)

We have partnered with DarkSkySites.com to allow you to automatically submit light pollution measurements made in SharpCap to their light pollution database. Uploaded measurements help refine modelled light pollution values, leading to more accurate predictions and a better understanding of the spread of light pollution. Having measurement data can also help support dark skies campaigns by showing the extent of the problem.

In SharpCap, you will see a new button appear to allow you to submit your light pollution measurement, as shown below
Screenshot 2026-11-16 141721.png
Screenshot 2026-11-16 141721.png (43.04 KiB) Viewed 24 times
This button will only be available to use if SharpCap has been able to generate a light pollution measurement for your setup *and* knows your location (latitude/longitude) *and* you have an internet connection. The most common way for SharpCap to know your location is if you are using a GOTO mount from within SharpCap, but if you don't do that, set up your location by entering your latitude and longitude in the 'Observing Location' tab of the SharpCap settings.

It's obviously important that the data that gets uploaded is accurate - incorrect readings or incorrect locations could risk spoiling the light pollution models rather than improving them. To try to help ensure this, SharpCap will run you through a series of checks when you first submit a measurement. Some of these checks are automated, others will require you to confirm things like the f-ratio of your telescope, your location, the fact that the sky is properly clear and your permission to share the data with DarkSkySites.
Screenshot 2026-11-16 142056.png
Screenshot 2026-11-16 142056.png (83.17 KiB) Viewed 24 times
The data sent to DarkSkySites.com by SharpCap includes the following data which have been carefully chosen to help facilitate use of the measurements without revealing personal information :

* The light pollution measurement in MPSAS
* A contributor ID - basically a random selection of letters and numbers. This will be the same for every measurement sent from the same install of SharpCap, allowing repeat measurements from the same site to be identified.
* Your location, but by default SharpCap will offset your location by between 50 and 125m to avoid revealing your precise position
* Whether the location is exact or offset as described above
* The time at which the image being measured was captured
* If available the altitude and azimuth that the telescope was pointing at when the image was captured
* The version of SharpCap being used and the version of the light pollution calculation algorithm that was used
* The fact that you have accepted the DarkSkiesSites data submission terms
* Details of the equipment used to make the measurement, including camera make/model, f-ratio and optical transmission of telescope and sensor QE value used
* The exposure and gain used when capturing the frame used to make the measurement
* Details of the current filter in use if you have a filter wheel set up in SharpCap (to try to confirm that the filter is 'Lum' or 'None').

Please follow these guidelines when making measurements to submit:

* Make sure you remove any filters (other than an IR/UV blocking filter). Any other filters, particularly narrowband or light pollution filters will significantly change the measurement values
* Measure the sky brightness when the sky is clear (no haze/thin cloud) and it is properly dark
* Measure when the telescope is pointing high up in the sky, so that the reading is for the sky overhead, not near the horizon
* Check that you have properly entered the f-ratio of your telescope - that's the focal length divided by the aperture. Include the effects of any focal reducers or barlow/tele-extenders in use.
* Leave the default values of 70% for sensor quantum efficiency and 95% for optical transmission unless you are sure they need changing. For most measurements the defaults are close enough.
* Make sure that your location is set correctly - to within 100m or so - it's no good having accurate measurements of light pollution that are tagged with the wrong location. I have included a 'distance from <nearby town>' in the location check to help flag incorrect positions before the submission is sent.

As always, feedback welcome (particularly if you break it).

cheers,

Robin
Post Reply