Conisdering adding Geospatial source input
Nobody has claimed this yet.
- Dominant language
- Common Lisp
- Stars
- 6.5k
- Forks
- 613
- Avg merge
- 3h 46m
- Merged PRs (30d)
- 1
Description
Thinking out loud here, adding support geospatial sources could be nice.
On top of my mind, allow imports from Shapefiles, Spatialites, KML, Oracle, MySQL
Shapefile components are basically:
.shp - The geometry store
.shx - The geometry index
.dbf - The dBASE file that stores the attributes
That said, there already are tools for this (shp2pgqsl, ogr2ogr) so the effort
might not be worth it. Though might be fun to pit them against pgloader and
see who's faster ^-^ Definitely low priority.
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Begin by mapping how pgloader currently accepts source types, then assess Shapefiles, SpatiaLite, KML, Oracle, and MySQL imports against the existing tools mentioned. Done would require a defined scope and acceptance criteria before implementation can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100