"Vector tile source does not use vector tile spec v2 and therefore may have some rendering errors"

[robhawkes]

I'm currently serving the exported MBTiles from tilemaker using tileserver-gl-light and visualising everything in Mapbox GL JS. I noticed that Mapbox GL JS spits out warnings for each tile along the lines of Vector tile source does not use vector tile spec v2 and therefore may have some rendering errors.

After digging around I found that this is because the tiles generated by tilemaker have their spec version number hard-coded to 1 causing Mapbox GL JS to get angry. If I change that hard-coded version number to 2 then the warnings disappear.

Now this is enough for me as Mapbox GL JS seems to be happy that the tiles are using version 2 of the Mapbox Vector Style Spec. However it's probably worth discussing how tilemaker can be officially brought inline to support version 2 of the spec.

Has this been looked into yet?

[systemed]

Would be happy to make this a configurable option, probably in the .json file (and defaulting to 2 if not specified). Does anyone know (@pnorman?) whether there would be any other implications for us, or is v2 really just a tidying/formalising of the more informal v1 spec?

[robhawkes]

That would be amazing as right now I'm hard-coding a work around. I'm unsure of the state of the spec in the past but version 2 looks pretty formal and well documented now. That link in my first post should hopefully describe the spec in enough detail to see how it differs from the current implementation in tilemaker. For what it's worth, changing the version number to 2 stopped the Mapbox GL JS warnings so just having a config option for that would be a quick win aside from full v2 support.

[pnorman]

Would be happy to make this a configurable option, probably in the .json file (and defaulting to 2 if not specified). Does anyone know (@pnorman?) whether there would be any other implications for us, or is v2 really just a tidying/formalising of the more informal v1 spec?

The winding order stuff is made more explicit

[systemed]

I've just added this as a configurable option in the JSON file (mvt_version), defaulting to 2. Could you check and see if it works for you?

[freeExec]

MBTiles with spec v2 of the Mapbox does not accept.

Vector Tile Layer has no extent

With setting mvt_version=1, it's okay.

[systemed]

Note to self: mapbox/mapnik-vector-tile#184 looks like something worth following up.

[systemed]

I've added support for writing the extent field required by Mapbox GL (JS/Native) when reading MVT v2 files (even though the .proto still calls it "optional"... hey ho).

[systemed]

Closing as I believe this is fixed now, but let me know if not.