OvertureMaps / OvertureMaps/data
Quality and consistency checks
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 47
- Avg merge
- 3h 42m
- Merged PRs (30d)
- 1
Description
This blog post https://overturemaps.org/blog/2023/april-overture-release/ mentions "We put the data through several validation checks".
First question: What are the current quality and consistency checks? Is there documentation about this somewhere? If not, can you mention some checks here?
Second question: In case of OSM as source, are the issues found directly corrected in OSM (if yes: under which accounts) - or at least reported back to the OSM community, e.g. to OSMCha?
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
Start with the linked Overture Maps release blog post and investigate where the current quality and consistency checks are described or implemented. Document the checks, then determine how issues from OSM are corrected or reported, including any OSM accounts or OSMCha references; done means these answers are documented clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- data, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100