OvertureMaps / OvertureMaps/schema
[Proposal] Consider removing columns that are populated with little to no data from the "core" schema
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 213
- Forks
- 22
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 31
Description
Type
Task
Scope
Multi-theme or Platform
Skillset
None
Description
There are several columns in the schema that are populated with little to no data, including booleans that have pass-through NULL values. Let's assess these columns and consider removing them from core. Some of them might be excellent candidates for extensions.
Note: The metrics below capture the percentage of non-null values in each column. A non-null column could include a struct that has null values (see: brands on places).
Transportation
| column | type | completeness |
|---|---|---|
road_flags |
< 3% | |
rail_flags |
< 1% | |
width_rules |
< 2% | |
level_rules |
< 2% | |
prohibited_transitions |
< 1% | |
destinations |
< 1% |
Buildings
| column | type | completeness |
|---|---|---|
level |
< 1% | |
min_floor |
< 3% | |
roof_direction |
< 3% |
Divisions
| column | type | completeness |
|---|---|---|
norms |
< 1% | |
perspectives |
0% |
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.
Research direction
No files or tests are named. Start by locating the core schema definitions and examining the listed Transportation, Buildings, and Divisions columns; done when each candidate has a documented removal or extension decision based on its usage and completeness.
Written by the indexing model from the issue text.
Assessment
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100