Forums

Hi @Asher thanks for the quick reaction -and the good idea! The tool needs PyQt6, Pillow, numpy, scipy, and pyqtgraph/PyOpenGL. Your script is great,  but there are actually two tools in the package (Mercator and post-Atlas) and they need to have their specific environment. My intention was to keep it open as editable python code so anyone can inspect and modify it as needed. But you are certainly right - not everyone has python installed or would like to look into the code. Here are the two pyinstaller spec files  Mercator.spec and post-Atlas.spec .  A plain pyinstaller --onefile Mercator.py only follows Python imports. It misses non-code resources that get loaded relative to the installed files — docs/ (Help, User Manual, Design notes, Credits), CREDITS.md/LICENSE, and most of all  mercator/world/*.json.gz (the real-elevation-data feature).  Attached are pyinstaller spec files that can be called by pyinstaller Mercator.spec pyinstaller PostAtlas.spec This would work as a standalone double-click exe, however:  The hand-over between the two tools will not work as built:  Check or convert in post-Atlas... and Convert > Edit in Mercator launch the sibling tool via sys.executable -m <module> (atlas_ui/other_tool.py). Inside a frozen exe, sys.executable is that exe, which doesn’t understand -m — and worse, the check for “is the other tool installed” (importlib.util.find_spec) will always say no, since each exe only bundles its own tool. So the button offering the hand-over won’t even appear. That’s a significant regression for frozen builds specifically. I ask my coding buddy (Claude) to find a solution for this as I believe the linking o fhte two tools is an important aspect. @lilypoppy suggested to create a single tool but that would make the GUI even more complex than it is today, I am afraid. But he does have point here. Size: Mercator.exe is ~140 MB, Post-Atlas.exe ~116 MB  on windows. They are bundling PyQt6 + NumPy + SciPy + Pillow + pyqtgraph/PyOpenGL for the 3D views). Versus the ~6 MB release zip, this is a very different distribution. This would clearly call for a single exe only.     Claude just implemented a fix 0.23.0, will release that shortly after testing. So the only remaining issue is size.   PostAtlas.spec Mercator.spec

@Grautvornix @Asher

build.sh Just made a build script to make this into an executable. (Should work across systems). Maybe you'd want to add this @Grautvornix? Also, does it just need pyqt6 and scipy to also be installed, or are there more?

OK, so now I had no choice (more or less): I am now terminating the single packages of mercator and post-atlas in favor of a common single package "Atlas Tools". The new package is  available on https://wildfiregames.com/forum/topic/170271-atlas-tools-a-package-combining-mercator-and-post-atlas/ Unfortunately, every user of the previous tools wanting to upgrade will have to de-install the previous versions as they will not be compatible with the Atlas Tools package anymore.   @Stan` could you please freeze this thread?

OK, so now I had no choice (more or less): I am now terminating the single packages of mercator and post-atlas in favor of a common single package "Atlas Tools". The new package is  available on https://wildfiregames.com/forum/topic/170271-atlas-tools-a-package-combining-mercator-and-post-atlas/ Unfortunately, every user of the previous tools wanting to upgrade will have to de-install the previsous versions as they will not be compatible with the Atlas Tools package anymore. @Stan` could you please freeze this thread?