use sharp instead of mapnik
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Currently, in order to do the final blending/cropping of Static Tiles, this library uses [node-mapnik](https://github.com/mapnik/node-mapnik/). This is a pretty beefy dependency to include solely for that purposes, it would potentially be better to use something written primarily for the purpose. After a bit of research, I would be happy with porting it to [sharp](https://www.npmjs.com/package/sharp), which has comparable features and is a bit lighter weight.
cc/ @tristen
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 locating the Static Tiles blending and cropping code and the node-mapnik dependency in the repository. Review sharp's comparable image-processing features and the existing behavior before assessing the required migration. Done means the library uses sharp instead of node-mapnik for the final blending and cropping without losing supported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- backend, computer-graphics
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100