maplibre / maplibre/maplibre-java
How continue with this repository?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 21
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Hey guys!
As the Kotlin Multiplatform PR is now canceled because `maplibre/spatial-k` is now available as multiplatform, we should discuss about how to continue with this repository/library.
spatial-k provides us the geometry models, and also a lot of (better and more) turf tools.
From my perspective we have following solutions:
1. Keep this library and continue working on
2. Keep this library, but remove the turf module
3. Move the GeoJson part to maplibre-native (like in iOS)
4. Use spatial-k's geometry objects instead of this library in Maplibre native for Android (maybe later also for iOS?)
5. .... something else?
Note: *With removing I mean a secure way to don't use this anymore in future. Deprecation, breaking changes and so on are important!*
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 reviewing the repository's current GeoJson and turf responsibilities alongside the available spatial-k library. Compare the listed continuation options, including migration and deprecation implications, and document the maintainers' chosen direction. Done means the repository path and any required transition plan are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kotlin
- Domain
- mobile
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100