Skip to content

What should the Euclid Q1 tables be called in the parquet schema? #430

@troyraen

Description

@troyraen

Twelve Euclid Q1 tables have been combined into one in the parquet product. Some of the original column names overlap, so it is necessary to add a table identifier (name) to those column names for technical reasons (column names need to be unique) and also for provenance/understandability. For example, 'DECLINATION' -> 'MER_DECLINATION'. It was decided that the best option is to add a table identifier to all column names other than OBJECT_ID and TILEID (which are not table-specific). The remaining question is, what should those table names be?

Our naming criteria includes:

  • [Required] A user who is familiar with the Q1 tables ought to be able to figure out which table is being referred to based on the name only.
  • [Desired] Short names, since they will be prepended to all column names and many column names are already quite long.
  • [Desired] Consistency with IRSA services.

For reference, here is the section of the demo notebook (irsa-tutorials/pull/108) that introduces the tables and their names:

Euclid Q1 tables and docs

The Euclid Q1 HATS Catalog includes the following twelve Q1 tables[*], which are organized underneath the Euclid processing function (MER, PHZ, or SPE) that created it.
Links to the Euclid papers describing the processing functions are provided, as well as pointers for each table.
Table names are linked to their original schemas.

See also:

[*] Euclid typically calls these "catalogs", but this notebook uses "tables" to avoid any confusion with the HATS Catalog product.

Metadata

Metadata

Assignees

Labels

HATS CatalogsAnnounce available HATS catalogs and discuss features

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions