OvertureMaps / OvertureMaps/schema
Class column NULL vs matching subtype
Open
@vcschapp is already working on this.
Since Jan 30, 2026.
- Dominant language
- Python
- Stars
- 213
- Forks
- 22
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 31
Description
I've noticed that the different themes are inconsistent in how the class column is handled. In some layers there are no nulls in the class field and it mirrors subtype when there is not a more specific value. E.g. when subtype = 'civic' then class can also be 'civic'
However, Divisions and Transportation seem to not have this mirroring and instead allow null values for class. The Buildings theme currently has a mixture of both situations.
We should have a consistent standard for how this field is populated.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.