-
-
Notifications
You must be signed in to change notification settings - Fork 84
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
Change the default basemap from Stamen #220
Comments
Hey @martinfleis, I'm one of the cofounders of Stadia Maps. Funny enough, my sister is doing a data science project right now and is using contextily, which missed our pass through the major FOSS projects using the Stamen tiles 😂 The Stamen styles will still be available (with updated data coming in the next week or so!) via Stadia Maps, but will require a (free with generous limits for non-commercial use) API key. It looks like you already have an integration for our other styles, so it shouldn't be too difficult to add more. We've put together a migration guide here: https://docs.stadiamaps.com/guides/migrating-from-stamen-map-tiles/. I'd be happy to take a whack at a PR if that'd be helpful. Either way, I totally understand setting the default to a provider which doesn't require an API key; that makes for a better dev experience. The Carto styles are great in my experience, and you can see the influence of Stamen's cartography both in some of their styles and our own Alidade Smooth. |
@ianthetechie Yes, we do have the full support of Stadia tiles already, including Stamen once I cut a release of xyzservices, we just need the default to "just work". |
contextily now uses Stamen Terrain as a default. With Stamen deprecating their tiles, this will need to change. Any preference? I think the feasible options are OpenStreetMap tiles or some Carto tile. cc @darribas
The text was updated successfully, but these errors were encountered: