Bug 115022 - Custom horizon line and cutoff
Summary: Custom horizon line and cutoff
Status: RESOLVED DUPLICATE of bug 338122
Alias: None
Product: kstars
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Fedora RPMs Linux
: NOR wishlist
Target Milestone: ---
Assignee: Jasem Mutlaq
URL:
Keywords:
: 119812 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-10-24 21:41 UTC by Danilo Câmara
Modified: 2015-01-27 19:58 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Danilo Câmara 2005-10-24 21:41:06 UTC
Version:           kdeedu-3.4.2-0.fc4.2 (using KDE KDE 3.4.2)
Installed from:    Fedora RPMs
OS:                Linux

One feature I miss in KStars is the ability to draw my custom horizon and cutoff line (I don't know if it's the right name). What I mean is to draw the line with the buildings and trees that block my view of the sky.

I guess it's not that hard to do. I could make a 360 degrees panorama of my observing site with my digital camera and a software like hugin http://hugin.sourceforge.net/ Then, easily select the day blue sky in a photo editing software like Gimp. With this selection, convert to a Black and White image (not grayscale). The B&W image could be used by KStars to draw my site cutoff line. Alternatively the B&W image could be converted to a vector graphics (approximately, by hand or in a trace software) to be better rendered in KStars.

Well, the process it's not trivial but the cutoff line is very useful. I think, with the data in a proper format, this feature is easy to implement in KStars.
Comment 1 Médéric Boquien 2008-08-19 06:09:47 UTC
*** Bug 119812 has been marked as a duplicate of this bug. ***
Comment 2 Jasem Mutlaq 2015-01-27 17:20:11 UTC
I am working on custom horizon support, it's on my TODO list.
Comment 3 Jasem Mutlaq 2015-01-27 19:58:01 UTC

*** This bug has been marked as a duplicate of bug 338122 ***