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 xyzservices for tile management #517

Closed
martinfleis opened this issue Aug 7, 2021 · 0 comments · Fixed by #654
Closed

Support xyzservices for tile management #517

martinfleis opened this issue Aug 7, 2021 · 0 comments · Fixed by #654

Comments

@martinfleis
Copy link

Is your feature request related to a problem? Please describe.

With the @geopandas team, we have built a new package called xyzservices to serve as a unified place for XYZ tile management. The idea behind this is that other packages will depend on that instead of having their own system and list of supported tiles hard-coded.

I have opened an issue about the support of xyzservices in holoviews -> holoviz/holoviews#5057 but it seems that the base map tile support in geoviews is using another implementation? If that is true, I'd suggest implementing the same support I have outlined in the holoviews issue.

I'll leave the details out (see the linked issue for more), so just quickly for the sake of completeness:

Describe the solution you'd like

  1. support xyzservices.TileProvider as an input of gv.WMTS and/or gv.Tiles (not sure about the difference, sorry).
  2. refactor tile management to map providers to the xyzservices objects and remove hard-coded metadata.

Additional context

holoviz/holoviews#5057

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

Successfully merging a pull request may close this issue.

1 participant