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

Support for Google Protobufs (PBF) Tile layers / overlays? #32

Closed
nevvkid opened this issue Jul 26, 2024 · 8 comments
Closed

Support for Google Protobufs (PBF) Tile layers / overlays? #32

nevvkid opened this issue Jul 26, 2024 · 8 comments

Comments

@nevvkid
Copy link

nevvkid commented Jul 26, 2024

I have to admit that I am not only a big fan of gpx.studio but also the Gravel Overlay by @mjaschen which are part of the bikerouter.de experience.

I would be a nice feature to be able to use that overlay with gpx.studio.
Adding the custom overlay works - and it looks like the tiles are actually served.
I am not sure why I can not see them.

The URL I tried for testing purposes is the following: https://tiles.bikerouter.de/services/gravel/tiles/{z}/{x}/{y}.pbf
(not knowing if it would be ok to just use it long term without asking / making a donation)

To get an idea how this would look like on the OpenStreetMap Basemap here is a screenshot:
image

Here is a post about the Gravel Overlay 2.0 by the creator: https://www.marcusjaschen.de/blog/2022/gravel-overlay-brouter-bikerouter/

@nevvkid
Copy link
Author

nevvkid commented Jul 26, 2024

image image

@vcoppe
Copy link
Contributor

vcoppe commented Jul 31, 2024

The website already supports vector layers. However, you need a Mapbox style JSON to specify how to style the data contained in .pbf files. I have seen on bikerouter.de that this information is hardcoded there. If you know this project well, maybe you can contact its owner to ask whether it would be okay to include this layer here?

@vcoppe
Copy link
Contributor

vcoppe commented Aug 29, 2024

Any news?

@nevvkid
Copy link
Author

nevvkid commented Aug 30, 2024

I got following response from the creator of the overlay.

The style for the Gravel-Overlay can be found here: https://github.com/mjaschen/gravel-overlay.

The tiles themselves can be accessed at https://tiles.bikerouter.de/services/gravel/. This URL must be included in the style.json under sources.openmaptiles.url (the version in the GitHub repo contains the local development URL).

I cannot undertake integration into third-party services, nor do I provide any guarantees regarding the availability or consistency of the tileserver URLs. However, since I have just set up the tileserver for the Gravel Overlay, the URLs should be stable for a while.

Maybe the layer could be made available as an optional layer? If it sees a lot of demand maybe there is a solution for hosting the overlay - pretty sure Í know someone who could help with infrastructure support.

@vcoppe vcoppe closed this as completed in 0cb7811 Aug 31, 2024
@vcoppe
Copy link
Contributor

vcoppe commented Aug 31, 2024

That's very nice of him!

I have managed to add the layer to the website, but had to break many things to make it work.
Custom layers need to be refreshed to work (just by clicking on "Update layer"), and overall the website needs some testing to make sure it still works as before.

@zod
Copy link

zod commented Aug 31, 2024

This is a feature that I'm currently missing in brouter-web (nrenner/brouter-web#775) so I'm very happy that it's supported by gpx.studio. I've just done a quick test and it seems to work just fine :)

@vcoppe
Copy link
Contributor

vcoppe commented Sep 2, 2024

This is a feature that I'm currently missing in brouter-web

Since the Gravel Overlay 2.0 vector overlay layer is displayed on https://bikerouter.de (which is based on brouter-web), it seems technically doable.

@zod
Copy link

zod commented Sep 2, 2024

Yes, in brouter-web it's supported for "built-in" layers, but not for custom layers.

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

3 participants