CartoDB / bigmetadata

BSD 3-Clause "New" or "Revised" License
43 stars 11 forks source link

Australia 2016 metadata problems #608

Closed javitonino closed 5 years ago

javitonino commented 5 years ago

There are several tables with columns with the same name but different data. Since we treat them with the same column id, we get inconsistent data. An example:

The column P_Tot_Tot (total population) is available in several tables. Let's look at three examples:

As you can imagine, these numbers are very different. Since for us, this column is the same, we have a mixup of data. In particular, the column that we offer depends on the database order of rows when generation obs_meta, so we are not even consistent. Denominators are also crazy because of this, as you can imagine.

We need to review the generation data so:

juanignaciosl commented 5 years ago

This issue will also close CartoDB/Geographica-Product-Coordination/issues/24

In addition to this, we should review the names for the geometries (see CartoDB/Geographica-Product-Coordination/issues/52). For some levels, names are mixed. Example:

    "SA1": {
        "name": "Statistical Area Level 1",
        "weight": 13,
        "region_col": "SA1_7DIGIT",
        "proper_name": "STATE_NAME"
    },

Levels SA1, SA2, SA3, SA4 and MB should be reviewed. If there's a meaningful name for them, it should be used. If there isn't, the id should be used as name.

alrocar commented 5 years ago

Levels SA1, SA2, SA3, SA4 and MB should be reviewed

Here's an extract of metadata and sample data in each file

alrocar commented 5 years ago

Closing since this is already merged and deployed to staging. I've left the PR in the backend kanban in "pending deploy".