MerginMaps / MerginMaps/db-sync
Problem syncing MultiLineStringM geometries
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 53
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
It looks like there may be some issues when trying use a GPKG with MultiLineStringM geometry column - syncing to PostgreSQL fails...
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 by reproducing the reported failure when syncing a GPKG containing a MultiLineStringM geometry column to PostgreSQL. Trace the synchronization path for that geometry type and confirm that the same data syncs successfully once the issue is fixed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100