-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
3rd Party External PBF Vector Source (doc & example?) #866
Comments
|
no, the actual domain si not domain.com and it resolves, we have some test tiles on http://domain.com/vectiles2/{z}/{x}/{y}.pbf |
Oh, I see the issue now. If you supply a
|
Thanks, that works! That defiantly was not clear from that doc/spec document. My goal is to try and load pre-generated tiles from a local source (eventually on mobile), rather than http url. Is it possible to load the tiles from a local source, the most simple being file:// I guess. |
Hi @canadaka - I hit the same issue as you on this. The call to load the tiles is executing this method: https://github.com/mapbox/mapbox-gl-js/blob/master/js/util/browser/ajax.js#L23 You might want to explore overloading that function to do what you want there? |
I'm hosting pbf tiles generated using tippecanoe on S3 and I can't seem to get tiles to render. The tiles seem to be loading in the network panel but nothing renders. This tileset works perfectly with OpenLayers 4. I sometimes get this error when panning around the map but nothing outside of that.
|
I am unable to get MVT/PBF vector tiles working from an external http:// source. I don't see any documentation or examples of this.
The sources docs page only mentions topoJSON and doens't actually give any info or example of using a 3rd party url: https://www.mapbox.com/mapbox-gl-style-spec/#sources
I created a very simple Style JSON file that includes:
Along with trying to specify a source in the JS
Nothing loads and the Chrome console log has errors:
Line #5433
GET http://domain.com/%7Bz%7D/%7Bx%7D/%7By%7D.pbf net::ERR_NAME_NOT_RESOLVED
Line #2618
Uncaught #
The text was updated successfully, but these errors were encountered: