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

Protobuf.skip unimplemented types #15

Closed
demiurg opened this Issue Jan 16, 2015 · 8 comments

Comments

Projects
None yet
5 participants
@demiurg

demiurg commented Jan 16, 2015

I'm interested in rendering MVT from TileStache Vector provider:
http://tilestache.org/doc/TileStache.Goodies.VecTiles.mvt.html

However, I'm getting the Error('Unimplemented type: ' + type) for type 3, 4, 6, 7

Should I assume these are same types as those listed here, double, int64, etc?
https://github.com/mapbox/vector-tile-spec/blob/master/1.0.1/vector_tile.proto

I'm not sure about that, because the JS source code has:
Protobuf.Int32 = 5;
but the mvt spec:
optional uint64 uint_value = 5;

So, these must be different?

What seems to be the problem, do you have any suggestions on what I should do?

@apollolm

This comment has been minimized.

Show comment
Hide comment
@apollolm

apollolm Jan 17, 2015

Member

Hello - I'm wondering about the compression you're using with your tiles? I've seen similar errors before, and it usually meant that our server had not compressed the .pbf file correctly.

I've also seen this problem when I pass bogus .pbfs into the decode library: mapbox/vector-tile-js#5

Also check this out: mapbox/vector-tile-js#15

...And this: mapbox/vector-tile-js#3

...or this: mapbox/vector-tile-spec#27

A few months back, Mapbox Studio (TileMill 2) switched from using deflate to using gzip.
Older versions of TileMill2 used deflate, whereas Mapbox studio uses gzip.

Map box created a server side library to help identify which type of compression is being used. (Can't find it right now).

Do you have an example file you can attach?

Member

apollolm commented Jan 17, 2015

Hello - I'm wondering about the compression you're using with your tiles? I've seen similar errors before, and it usually meant that our server had not compressed the .pbf file correctly.

I've also seen this problem when I pass bogus .pbfs into the decode library: mapbox/vector-tile-js#5

Also check this out: mapbox/vector-tile-js#15

...And this: mapbox/vector-tile-js#3

...or this: mapbox/vector-tile-spec#27

A few months back, Mapbox Studio (TileMill 2) switched from using deflate to using gzip.
Older versions of TileMill2 used deflate, whereas Mapbox studio uses gzip.

Map box created a server side library to help identify which type of compression is being used. (Can't find it right now).

Do you have an example file you can attach?

@demiurg

This comment has been minimized.

Show comment
Hide comment
@demiurg

demiurg Jan 17, 2015

It looks like TileStache is using zlib to compress:
https://github.com/TileStache/TileStache/blob/master/TileStache/Goodies/VecTiles/mvt.py

I'll check out these links, thanks!

Here is an example tile: http://yellow.ags.io/192.mvt

demiurg commented Jan 17, 2015

It looks like TileStache is using zlib to compress:
https://github.com/TileStache/TileStache/blob/master/TileStache/Goodies/VecTiles/mvt.py

I'll check out these links, thanks!

Here is an example tile: http://yellow.ags.io/192.mvt

@springmeyer

This comment has been minimized.

Show comment
Hide comment
@springmeyer

springmeyer Jan 17, 2015

last time I checked the tiles produced by TileStache are a completely difference format as the work predates the Mapbox Vector Tile Spec. So don't use or expect TileStache to work unless you add a backend to produce tiles in the Mapbox spec.

springmeyer commented Jan 17, 2015

last time I checked the tiles produced by TileStache are a completely difference format as the work predates the Mapbox Vector Tile Spec. So don't use or expect TileStache to work unless you add a backend to produce tiles in the Mapbox spec.

@demiurg

This comment has been minimized.

Show comment
Hide comment
@demiurg

demiurg Jan 17, 2015

Thanks, that resolves a lot of confusion for me :)

demiurg commented Jan 17, 2015

Thanks, that resolves a lot of confusion for me :)

@demiurg demiurg closed this Jan 17, 2015

@hallahan

This comment has been minimized.

Show comment
Hide comment
@hallahan

hallahan Jan 18, 2015

Contributor

Give PGRestAPI a try. This is what we use to pump out vector tiles.

https://github.com/spatialdev/PGRestAPI

Contributor

hallahan commented Jan 18, 2015

Give PGRestAPI a try. This is what we use to pump out vector tiles.

https://github.com/spatialdev/PGRestAPI

@relet

This comment has been minimized.

Show comment
Hide comment
@relet

relet Mar 2, 2015

@springmeyer There also seems to be a version over at mapzen that has a mapbox vector tile backend.

relet commented Mar 2, 2015

@springmeyer There also seems to be a version over at mapzen that has a mapbox vector tile backend.

@demiurg

This comment has been minimized.

Show comment
Hide comment
@demiurg

demiurg Mar 2, 2015

I've been using the Migurskis .mvt format, since I understood what it is, it fit my needs to dynamically style and output multiple formats from same cached file.

Looking at the mapzen version: "import mapbox_vector_tile", seems like this key file is not in the repo?

demiurg commented Mar 2, 2015

I've been using the Migurskis .mvt format, since I understood what it is, it fit my needs to dynamically style and output multiple formats from same cached file.

Looking at the mapzen version: "import mapbox_vector_tile", seems like this key file is not in the repo?

@relet

This comment has been minimized.

Show comment
Hide comment
@relet

relet commented Mar 2, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment