Improve `Geometry` encoding precision behaviour when converting to `SpatialDataset`
Open
enhancement
geo
- Dominant language
- Kotlin
- Stars
- 744
- Forks
- 27
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
* Now it's constant;
* Consider this parameter setting.
Contributor guide
Research direction
Start by locating the Geometry encoding path used when converting to SpatialDataset. The issue does not identify files, tests, or the intended precision behavior, so first clarify whether precision should remain constant or become configurable; done means the expected setting is defined and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100