MerginMaps / MerginMaps/qgis-plugin
Check that non-empty vector layers do not have empty extent
Open
Nobody has claimed this yet.
enhancement
validation
- Dominant language
- Python
- Stars
- 44
- Forks
- 20
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 5
Description
We had a case where a table in GeoPackage had a couple of features, but it had empty extent for some reason - due to that, various things like rendering or object identification did not work correctly.
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 file, test, or entry point is named. Start by tracing how the plugin handles GeoPackage vector layers and calculates or reads their extents, then review the related MerginMaps/input issue 1124. Done means a non-empty layer cannot retain an empty extent and the behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100