mapbox / mapbox/tilelive-vector
Find out why vtile.getTile returns "Tile does not exist"
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 72
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
#125 adds the EMAPNIK eror code within the `source.profile()` method so that errors can be handled properly in mapbox-upload validate (refs https://github.com/mapbox/mapbox-upload-validate/blob/master/lib/validators/tm2z.js#L19).
NOTE: I think this is a stopgap to a deeper mapnik bug. The style added here was valid in mapnik 3.4.17, but invalid in 3.5.6 because of a `Tile does not exist` error. This smells like something else is afoot, and while that PR fixes the missing code and should be merged, we should solve the underlying issue asap.
cc/ @GretaCB @flippmoke @springmeyer @mapsam
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 reproducing vtile.getTile's "Tile does not exist" error with the style that worked in Mapnik 3.4.17 but failed in 3.5.6. Read source.profile() and the referenced mapbox-upload-validate validator at lib/validators/tm2z.js; done means identifying and fixing the underlying Mapnik-related cause rather than only adding the EMAPNIK error code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100