there is nothing wrong with ending up in Cetus because you looked up Abell 2, a galaxy cluster. So what's wrong is what you entered for the USNO A2.0 catagluge.
One of the major problems is, that Microsoft Product users don't get it that a space is used to devide a command from it's options. And this is, because on Windows systems you just click with your mouse and don't see what will happen behind the button. This leads to missusage of file names, too, because the users use spaces to separate words, which then are interpreted as command options.
If the users would start using underscores instead of spaces, many errors won't come up.
Concerning USNO A2.0...
For those who do not habe downloaded the whole A2.0 (8.8GB not 6.3 as written in the Guide User Manual), the navy closed down the service with a firewall policy not allowing anyone anonymously fetching data. I tried it, the last two hours, now, by any means. VIZIER doesn't get them, too, because they face the same problem.
I'm trying to get a local copy to my hard drive, since ftp services are provided. I'm going to test how to get USNO A2.0 data since A2.0 entered at "Go to object name" looks up Abell objects.
Maybe renaming the look-up to USNOA2 plus number would be a great idea. In the same turn a little parse-update could be done dealing with white spaces like space etc.
Till this is done, using the .tdf's will be a solution.
cheers and clear skies,
-- "A little learning never caused anyone's head to explode!" "Ein wenig Lernen hat noch niemandens Kopf zum Explodieren gebracht!"
On Monday, February 15, 2016 4:07 PM, "Ewald_Schauer@... [guide-user]" <email@example.com> wrote:
it's not possible to find a star from USNO A2.0 catalogue with
the updated Guide9. The version 19 Apr 2012 is the last that works well.
Now "Go to object name A2 1425 07813092" for example leads always
to a point in CETUS.Perhaps you can take a look ?