Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
votable parsing issue resulting `object` dtyped Table columns
See original GitHub issuefrom astroquery.alma import Alma
payload = {'target_name':'M100', 'dataproduct_type':'cube'}
payload_query = Alma.query(payload=payload, public=True, science=True)
payload_query.write('m100.fits')
Throws ValueError: Illegal format object.
Possibly related to astropy/astropy#7480.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
votable parsing issue: datatype="char" casted as object dtype ...
I downloaded a table from the Gaia science archive using astroquery, and tried to write it to a FITS file: from astroquery.gaia import...
Read more >VOTable XML Handling (astropy.io.votable) — Astropy v5.2
Table object to an astropy.table.Table object, you can specify whether to give preference to name or ID attributes when naming the columns.
Read more >vo.table API documentation - stsdas
Parses a VOTABLE xml file (or file-like object), and returns a VOTable object, ... it is used for the column name in the...
Read more >Pyvo TAP result to csv (via astropy.Table?)
I have a TAP table in a VO service that I want to dump to csv. ... suspect this could rather be a...
Read more >STIL - Starlink Tables Infrastructure Library
7.4.1 Generic table output; 7.4.2 Single VOTable output ... Every object in the column described by that metadata should be an instance of ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Welcome to Astropy 👋 and thank you for your first issue!
A project member will respond to you as soon as possible; in the meantime, please double-check the guidelines for submitting issues and make sure you’ve provided the requested details.
GitHub issues in the Astropy repository are used to track bug reports and feature requests; If your issue poses a question about how to use Astropy, please instead raise your question in the Astropy Discourse user forum and close this issue.
If you feel that this issue has not been responded to in a timely manner, please leave a comment mentioning our software support engineer @embray, or send a message directly to the development mailing list. If the issue is urgent or sensitive in nature (e.g., a security vulnerability) please send an e-mail directly to the private e-mail feedback@astropy.org.
This is not an astroquery issue, but very likely a votable parsing issue, which belongs to the core package. I would expect this to be basically a duplicate of https://github.com/astropy/astropy/issues/7480.
Here the difference is that there is an added layer of pyvo in the middle which does the communication with the TAP service. I would say this is a pyVO issue, it’s responsible for parsing the votable return of the server into an astropy Table.
here is some debug info from L242 of
pyvo/pyvo/dal/query.pycallingfrom astropy.io.votable import parse as votableparsethat may help to identify the underlying parsing issue, this time with datatype=char and either"adql:TIMESTAMP"or"adql:REGION"as xtype