Repository navigation
Releases: kvandebeek/lunaratlas
Release list
LunarAtlas 1.0.1 – Langrenus
IAU feature names on your own photo of the Moon. Drop a photo on the window and the names appear — no
coordinates, no plate solving, no calibration.
Full manual · Your first photo · Troubleshooting
Which file
| Your computer | Download |
|---|---|
| macOS, Apple silicon (M1 and later) | LunarAtlas-1.0.1-macos-arm64.dmg |
| macOS, Intel | LunarAtlas-1.0.1-macos-x64.dmg |
| Windows, 64-bit | LunarAtlas-1.0.1-windows-setup.exe |
| Linux, 64-bit | LunarAtlas-1.0.1-linux-x64.tar.gz |
Not sure which Mac you have? Apple menu → About This Mac. "Apple M1" or later is arm64, "Intel" is x64.
macOS: the first start needs your permission
These builds are not signed with a paid Apple certificate, so macOS stops the first launch. It is the
standard warning for any unsigned app. You allow it once, and never again.
- Open the
.dmgand drag LunarAtlas to Applications. - Open Applications and double-click LunarAtlas. macOS refuses: "LunarAtlas cannot be opened
because it is from an unidentified developer". Press Done or Cancel. - Open the Apple menu → System Settings → Privacy & Security.
- Scroll down to the Security section. There is a line saying "LunarAtlas was blocked from use
because it is not from an identified developer", with an Open Anyway button. Press it. - Confirm with Open, and your password or Touch ID if asked.
LunarAtlas starts, and every later launch is normal.
A faster way, if you prefer the terminal:
xattr -dr com.apple.quarantine /Applications/LunarAtlas.app
On macOS 15 Sequoia and later the Open Anyway button appears only after you have tried to open the
app and been refused, so do step 2 first.
Windows: SmartScreen
"Windows protected your PC", naming the publisher as unknown and advising you not to run it. Press
More info, then Run anyway. Once, on the installer. Same reason: no paid certificate.
Neither warning says anything about whether the app is safe — only that nobody has paid a certificate
authority to vouch for the publisher. If you would rather not take that on trust, check the download
against SHA256SUMS.txt below, or build it yourself: the whole thing is on GitHub.
Checking your download
Put SHA256SUMS.txt next to the file you downloaded:
shasum -a 256 --ignore-missing -c SHA256SUMS.txt # macOS
sha256sum --ignore-missing -c SHA256SUMS.txt # LinuxGet-FileHash LunarAtlas-1.0.1-windows-setup.exe # Windows; compare with the line in SHA256SUMS.txtYou want to see OK for your file. --ignore-missing matters: the file lists all four downloads, and
without it the three you did not download are reported as FAILED, which looks alarming and is not.
What is new in 1.0.1
macOS builds can be opened at all. 1.0.0's macOS builds shipped with an invalid code signature:
the build wrote the third-party licence notices into the app bundle after it had been sealed, which
broke the seal. macOS refused those builds outright with "LunarAtlas is damaged and can't be opened",
and no Open Anyway could get past it. The bundle is now sealed again after the build is complete, and
the build verifies it, so this cannot ship unnoticed again. 1.0.0 has been withdrawn.
Windows and Linux were unaffected. The Windows installer now also carries its own version and publisher
metadata, and the build is ready to be code-signed once a certificate exists.
First run
The first photo downloads about 145 MB of Moon maps, once; the first close-up about 530 MB more. After
that LunarAtlas works offline. Exports go to Pictures/LunarAtlas.