Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pbf output results in "Error: Unimplemented type: 3" errors across clients #793

Closed
tvogt opened this issue Sep 15, 2019 · 8 comments
Closed

Comments

@tvogt
Copy link

tvogt commented Sep 15, 2019

using

tippecanoe -e routes (mydata.geojson)

to generate a directory of *.pbf files results in "Error: Unimplemented type: 3" error messages in both openlayers and leaflet.js

the same datasource turned into *.pbf using maptiler works just fine, so it's not the data.

@tvogt
Copy link
Author

tvogt commented Sep 15, 2019

from openlayers:

Error: Unimplemented type: 3 2 index.js:191
skip index.js:191
readFields index.js:41
Hg MVT.js:306
readFields index.js:39
readFeatures MVT.js:252
onload featureloader.js:86
self-hosted:1003

@tvogt
Copy link
Author

tvogt commented Sep 15, 2019

@tvogt
Copy link
Author

tvogt commented Sep 15, 2019

even in Mapbox GL it errors out:

{…}

message: "Unimplemented type: 3"

stack: ""

: Object { … }
evented.js:136:20
fire evented.js:136
fire evented.js:130
fire evented.js:130
_tileLoaded source_cache.js:251
a vector_tile_source.js:148
process actor.js:148
onmessage throttled_invoker.js:21

@tvogt
Copy link
Author

tvogt commented Sep 16, 2019

Figured out after much searching that this is probably indicating a zipped pbf file. That kind of should at least be mentioned somewhere.

@e-n-f
Copy link
Contributor

e-n-f commented Sep 30, 2019

Tippecanoe generates gzipped tiles by default because that is what Mapbox uploads and clients expect. You can use --no-tile-compression if you don't want compression.

@e-n-f e-n-f closed this as completed Sep 30, 2019
@tvogt
Copy link
Author

tvogt commented Oct 1, 2019

As mentioned: This should be described better and/or the error message adapted. It took me a lot of searching to figure that one out.

@e-n-f
Copy link
Contributor

e-n-f commented Oct 1, 2019

Thanks. I'll add a reference to that error message in the README.

@e-n-f
Copy link
Contributor

e-n-f commented Oct 1, 2019

#800

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants