-
Notifications
You must be signed in to change notification settings - Fork 32
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
Conquer the world #49
Comments
Update, as of #28 import folium
import xyzservices.providers as xyz
tiles = xyz.CartoDB.Positron
folium.Map(
location=[53.4108, -2.9358],
tiles=tiles.build_url(),
attr=tiles.attribution,
) |
Holoviews also support tiles and has them hard-coded in their source code https://github.com/holoviz/holoviews/blob/master/holoviews/element/tiles.py |
BTW, any chance for supporting WMS services as well? A lot of WMS services can be found at https://apps.nationalmap.gov/services |
@giswqs Thanks! Is there anything you'd like to see to support it in your packages that is not in yet? For the use in
What do you need for that? It is just an URL, name, and attribution as it is with XYZ, right? I think it makes sense to add it to the mix, together with some attribute storing the service type. The same actually applies to vector tiles (where it may be a bit more complicated due to styles but doable as well). |
@martinfleis Let me do some testing and will provide feedback here later. Thanks. |
Adding https://github.com/SciTools/cartopy/blob/master/lib/cartopy/io/img_tiles.py |
https://github.com/heremaps/here-map-widget-for-jupyter now also uses providers from Note: I will do the release soon. |
I think that plotly currently does not support custom XYZ tiles in any form, only mapbox styles, so there's no place for us at the moment. |
Greppo now supports xyzservices for its base_layer 🚀 |
@krish-adi nice! Thanks for letting us know! |
Once
xyzservices
is relased and has a stable API, it would be great to see it adopted as the one-stop shop for XYZ services in Python. Opening this ticket to brainstorm on which for which packages we would love to adopt the library, and what we could do to make adoption easy and smooth.So far:
contextily
: version 1.2 will swap its currentproviders
submodule forxyzservices
under the hood, adding deprecation notices. This means thecontextily
user will be able to pass a tile provider to, say,add_basemap
and it'll magically use that without any attribution, URL, etc. being passed. -> REF: Outsource providers to xyzservices contextily#183geopandas explore
: first release will rely directly onxyzservices
for tile providers. The user will be able to pass aTileProvider
object to specify the basemap to be usedIt'd be great to also get on board:
folium
: the user would be able to pass aTileProvider
object and avoid specifying URL, attribution, etc. arguments -> ENH: support xyzservices python-visualization/folium#1498; folium will depend on xyzservices from 0.16 -> use xyzservices instead of templates python-visualization/folium#1827ipyleaflet
: the user would be able to pass aTileProvider
object and avoid specifying URL, attribution, etc. arguments. Conversations have started over atcontextily#153
. -> Refactor basemap module on top of xyzservices jupyter-widgets/ipyleaflet#854leafmap
: the user would be able to pass aTileProvider
object and avoid specifying URL, attribution, etc. arguments -> Refactor basemap module on top of xyzservices opengeos/leafmap#91holoviews
-> Support xyzservices TileProvider objects in hv.Tiles holoviz/holoviews#5057geoviews
-> Support xyzservices for tile management holoviz/geoviews#517here-map-widget-for-jupyter
-> Added support for external basemaps heremaps/here-map-widget-for-jupyter#27bokeh
has similar machinery as Holoviews. Could support TileProvider as input or depend on us directly when specifying metadata. (https://docs.bokeh.org/en/latest/docs/reference/tile_providers.html#bokeh-tile-providers) -> [FEATURE] Support xyzservices in basemap tiles bokeh/bokeh#11500 and Outsource tile management to xyzservices bokeh/bokeh#11512plotly
is another one but I am not sure about their implementationa lot of edits by @martinfleis
The text was updated successfully, but these errors were encountered: