MerginMaps / MerginMaps/geodiff
Extent update is ignored
Open
Nobody has claimed this yet.
bug
wontfix
- Dominant language
- Python
- Stars
- 183
- Forks
- 21
- Avg merge
- 9d 11h
- Merged PRs (30d)
- 2
Description
gpkg_contents table contains extent of the data. There are no geopackage triggers to modify extent, but it is done manually by OGR.
ATM we are handling extent conflicts similar to any other conflicts in database, which means sometimes it could lead to invalid extent.
see #29
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 issue #29 and the existing extent-conflict handling in the geodiff repository; no file or test is named in this report. Determine how gpkg_contents extents are reconciled and add coverage showing valid extent updates after conflicts; done means conflicting extents no longer produce invalid results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100