-
-
Notifications
You must be signed in to change notification settings - Fork 405
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
TapPlus parse simbad fail with non ascii char #2916
Comments
I'm afraid this is an upsteam issue, the returned VOtable seems to violate the votable linter. I'm inclined to close this issue as we can't do much about it in astroquery and as I detail it out below, it doesn't involve any of the functionalities from here. Some other issues: Please not the big red warning at the top of the documentation, we do not support direct usage of TapPlus, please use PyVO instead. (but this doesn't effect the problem, the cc @ManonMarchand for the upstream simbad issue (it also present on the branch of #2856) Here is the votable, if that's of any help:
|
Thanks for the report and the perfect minimal example. The error is upstream indeed. This field should be unicodechar and not char. While waiting for the fix to be done on our side (might take a few days), note that you can open this votable with topcat (its parser is more permissive on types) or get the table in an other format through pyvo (fits, json and csv should work) |
this should be solved now, sorry for the delay |
Thanks @aoberto! |
some fields have changed their datatype upstream following astropy#2916
some fields have changed their datatype upstream following astropy#2916
error log:
The text was updated successfully, but these errors were encountered: