Created attachment 52543 [details] DGML file for Titan. Version: unspecified (using Devel) OS: OS X I tried to use Marble with some of my research data on Titan. Unfortunatly, Titan is not known by Marble data base (see planet.cpp source code). I thus make my own dgml file using <target>Titan</target> keywords. Under OS X Marble crashed. On Fedora 13, marble is able to display my stuffs only if I use titan instead of Titan in the dgml keywords. Unfortunately, this is useless because scaling does not work. (of course, Marble does not know the size of Titan). I see two solutions: (1) Allowing the user to inter a new target body parameters (that could be really great because just for the Earth, scientists use several geoid, ellipsoids and so on. So let think about that. (2) more simple but less user-friendly. Define in planet.cpp all the Solar Systems body on which we do have data. Trust me this is huge! Reproducible: Always Steps to Reproduce: just by trying what I describe previously. Actual Results: it crash under QT version (e.g. OS X). And pretty weird behavior under Kde version (GNU/Linux). Expected Results: I expected that it could be taken into account in the next version of Marble.
Hi, I created this patch: https://git.reviewboard.kde.org/r/103653/ With this you can provide a custom radius for a celestial object in the dgml file. Usage: <target radius="15451548.14"> Object name </target>
Hey Lucas, I'm an amateur astronomer at heart, so I like the idea of having all spherical objects (moons, asteroids) covered as well. Now that we fixed the radius and crash issue (in current master) would you mind to finish your Titan map theme and contribute it so that we can offer it for download? :-) :-) :-) BTW: You can create multiple layers for a single theme (see the hike and bike map) that can be enabled and disabled via the UI inside the legend. So in theory it would be possible to display e.g. a cloud map on top the Huygens surface photos on top of the Cassini surface data ...
Cleaning up the Bug database .. and this one got fixed long ago already ... :-)