In issue #2911 it was shown that the Gaia class launch_job returns the upper case column name DESIGNATION.
This came from that fact that IDs are used instead of the names in the votable.
Recently, the votables returned by gaia has been updated in order to include the datalink "Service Descriptors", so these votables contain a few new ID, where their corresponding values are capitalized. Therefore, this implies that the column names will be changed when the votable are read from astropy: they would be shown as uppercase names. We need to keep generating astropy tables that returns column names as lowercase names, based on the names and not on the IDs. This is an example:
>>> job = gaia.launch_job("select top 1 solution_id,source_id,designation from gaiadr3.gaia_source order by source_id")
>>> print(job.get_results())
solution_id SOURCE_ID DESIGNATION
------------------- ------------------- ----------------------------
1636148068921376768 4111834567779557376 Gaia DR3 4111834567779557376
Could you give us some support to carry out this change in gaia? Could we make use the parameter use_names_over_ids=True at the time the votable is read? Where could we make this change?
cc @esdc-esac-esa-int
In issue #2911 it was shown that the Gaia class launch_job returns the upper case column name DESIGNATION.
This came from that fact that IDs are used instead of the names in the votable.
Recently, the votables returned by gaia has been updated in order to include the datalink "Service Descriptors", so these votables contain a few new ID, where their corresponding values are capitalized. Therefore, this implies that the column names will be changed when the votable are read from astropy: they would be shown as uppercase names. We need to keep generating astropy tables that returns column names as lowercase names, based on the names and not on the IDs. This is an example:
Could you give us some support to carry out this change in gaia? Could we make use the parameter use_names_over_ids=True at the time the votable is read? Where could we make this change?
cc @esdc-esac-esa-int