MerginMaps / MerginMaps/geodiff
API call to check for geodiff compatibility
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 183
- Forks
- 21
- Avg merge
- 9d 11h
- Merged PRs (30d)
- 2
Description
Some features in sqlite are not currently supported and geodiff will not work correctly, e.g.:
- custom triggers (#48)
- foreign keys (#39)
It would be good to have a function that would go through the geopackage content and report any problems.
Original idea from @PeterPetrik
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, tests, or entry points are named. Start by reviewing the existing geodiff API and the referenced compatibility limitations in issues #48 and #39; the work is done when a function reports unsupported GeoPackage features, including custom triggers and foreign keys.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sqlite
- Domain
- api, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100