More support for GEOMETRY type
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 466
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
Super nice work on the ui! I am a big fan and already thankful for another great tool built on top of the best db engine 🦆 🍰
I see that the GEOMETRY type is somewhat supported in the UI, but I would love to see more meta data like you give for the non Spatial types.
There is some discussion around the meta data that can be associated with a geoparquet file in the duckdb-spatial repo, perhaps this is relevant.
https://github.com/duckdb/duckdb-spatial/discussions/484
Thanks again for the great work!
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
Start by reading the issue and the linked duckdb-spatial discussion to identify which GEOMETRY metadata should be supported. Trace the existing UI handling for GEOMETRY and compare it with metadata shown for non-spatial types; done should mean the agreed spatial metadata is displayed consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- databases, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100