[APBeta] Not sure this is a bug??

[Victor van Wulfen]

More cataloguess have this. Or to put it better, they don't always have a
value for position angle. To the best of my knowledge the catalogue that
most often has a value is the HYPERLEDA Galaxy Catalogue. Perhaps you could
write it so that, whenever a catalogue has no value for PA, the value of the
HYPERLEDA catalogue is used? Still, even in that catalogue there sometimes
is no value. Well, there is, but it's 0 (zero).

 Victor van Wulfen


 www.clearskies.eu

> -----Oorspronkelijk bericht-----
> Van: apbeta-bounces at lists.astroplanner.net [mailto:apbeta-
> bounces at lists.astroplanner.net] Namens Paul Rodman
> Verzonden: zondag 9 augustus 2009 4:32
> Aan: AstroPlanner Beta Testers
> Onderwerp: Re: [APBeta] Not sure this is a bug??
> 
> 
> On Aug 8, 2009, at 6:52 PM, David Crum wrote:
> 
> > This "behavior" has been happening for a while, never really noticed
> > it until tonight.
> >
> > I like to have the NGC catalog displayed and the label box checked,
> so
> > I can ID the other NGC objects in the FOV display.
> >
> > For this example I am using NGC 4691 (Herschel II galaxy) in my plan
> > and I have it centered in the FOV.  However, it is at an angle (90
> > degs??) to the NGC object which is also ID.  I have included a
> > screenshot.
> >
> >
> > http://img.photobucket.com/albums/v700/davidthebear/0136.jpg
> 
> I'm guessing that your plan object came from the Herschel Catalogue,
> which doesn't include position angle info. The NGC Catalogue does.
> Hence the apparent discrepancy. So it's not a bug in the app, just a
> shortcoming of the Herschel catalogue.
> 
> I can look at rewiring the Herschel catalogues to include that info.
> 
> Paul R.
> 
> _______________________________________________
> APBeta mailing list
> APBeta at lists.astroplanner.net
> http://lists.astroplanner.net/listinfo.cgi/apbeta-astroplanner.net