-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to read some NED VOTables with astropy.table.Table #1266
Comments
Strictly speaking, the file is violating the spec, so this should be reported to the maintainer of the tool that is producing the file. I've sent an e-mail to That said, we do have a history of adding workarounds for this sort of thing to |
Yeah, don't really want VOTable to become more like FITS than it needs to be 😝 |
Just a heads up, still no reply from |
I did ask, but only got pointed to the director of the place, which didn't seem that useful. I'll see if I can drill down a bit. On Jul 31, 2013, at 2:41 PM, Michael Droettboom wrote:
|
I dug up a contact and just sent an email. |
@perrygreenfield @mdboom - Any updates? |
I was told on the 01-08-2013 that the NED developers are looking into it. |
Has this issue been fixed in the meantime?
|
It looks like the NED developers have fixed this, I just never got notification of that. I'm closing this bug as "fixed upstream". |
The errors specifically happen while retrieving VOTables for the NED References by Object Name queries. A sample VOTable that causes errors from this search is here.
For instance on doing this:
The problem apparently seems to be caused by the fact that the entries in the column
ref_col1
are of the form1.
rather than simply1
. So trying to parse1.
like entries throws the exception. Would there be any simple workaround to this?The text was updated successfully, but these errors were encountered: