Skip to content

Changes to column mapping post-UR #2680

Description

@Ben-Hodgkiss

Following user testing, we want to make the following changes to the column mapping feature prior to it going live:

  • Improve the prominence of the guidance for column mapping - @paris-dp to provide updated design
  • Within the guidance, include a link to the relevant guidance document for that provision. This is stored in default.yaml for each dataset. @paris-dp and @oli-rose-mhclg to discuss guidance.

One to consider....

  • For geography datasets, if we can't automatically map geometry data, we should scan the first line of actual data to see if any of the columns start with "POINT", "POLYGON" or "MULTIPOLYGON". If so, we should automatically create a column mapping for these - i.e. "POLYGON"/"MULTIPOLYGON" -> geometry; "POINT" -> point. As usual, if we have a column mapping for one of the above, we shouldn't show the other field as a missing column to map against.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

Status
Done - This Period

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions