Unable to use with uncompressed vector tiles

Open
#142 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
backend

Research direction

Start at backend.js line 113 and inspect how makevtile handles uncompressed PBF input. Determine how the issue’s proposed header or URI parameter would signal uncompressed vector tiles, then verify the rendering path handles them without requiring recompression. Done means uncompressed vector tiles work correctly through tilelive-vector.

Written by the indexing model from the issue text.

Description

Even though makevtile() supports uncompressed PBF data, the code at https://github.com/mapbox/tilelive-vector/blob/master/backend.js#L113 only allows compressed data to be treated as vector tiles. There are several cases when vector tile gets uncompressed and processed by other layers, and they have to be re-compressed just so that tilelive-vector handles it correctly.

Should there be a header or a URI parameter to allow for this?

Dominant language
JavaScript
Stars
72
Forks
42
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mapbox/tilelive-vector

All issues in mapbox/tilelive-vector

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.