Patch to solve issue #3282 (MiriadeClass)

[bcarry]

IMCCE base URL was changed from
http://vo.imcce.fr
to
https://ssp.imcce.fr

The columns from the Miriade/ephemcc service have changed on the new server, and the documentation adapted

[bsipocz]

Many of these are already done in #3286, but that PR got stuck on upstream issues.

[bcarry]

the automatic checks are failing, but I don't see what can I do for these.
Any ideas? Help please :-)
Thanks

[mkelley]

@bcarry it looks like a few issues. You can follow the links on each check to see a log of the tests which should help identify the failures:

• Edit CHANGES.rst to include a summary of these changes following the format of the other entries.
• Remove the whitespace on line 397 of core.py: astroquery/imcce/core.py:397:1: W293 blank line contains whitespace
• Line 316 of core.py is trying to rename a "date" column to "epoch", but "date" does not exist.

[bcarry]

Thanks @mkelley !

• white space removed
• info added on CHANGE.rst (my bad for not having done it)
• I don't understand the date->epoch point:
  • Miriade VOTable output reports the epochs as a date column (https://ssp.imcce.fr/webservices/miriade/api/ephemcc/#examples)
  • I run the patched version in a new env locally, and the QTable retrieved from the WS has a date column (as expected)

[mkelley]

Ah, it is the offline tests that are failing in astroquery/imcce/tests/test_miriade.py. They rely on the votable files in astroquery/imcce/tests/data Can you regenerate these files with the new service? They look like they were generated for 3552 for a single date, only varying coordtype according to the file name. The date doesn't seem to matter to the tests.