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

Mapquest tiles no longer available without API key #218

Closed
ehcloninger opened this Issue Sep 6, 2016 · 4 comments

Comments

3 participants
@ehcloninger

ehcloninger commented Sep 6, 2016

I enable maps on my theme (show_map = True), which activates MapQuest tiles (pin in upper right of image). In the themes, this is written in themes/*/templates/index.html during function init_maps(). As of 2016/07/11 the Mapquest tile server is no longer available for open public use without an API key.

According to their announcement, an API key can have 15,000 accesses per month. I imagine you want to set the templates up to require the user to get their own API key or else link to someone else's map tiles.

http://devblog.mapquest.com/2016/06/15/modernization-of-mapquest-results-in-changes-to-open-tile-access/

screen shot 2016-09-06 at 4 23 04 pm

@saimn

This comment has been minimized.

Owner

saimn commented Sep 7, 2016

Thanks for reporting this. What are the alternatives ?

@saimn

This comment has been minimized.

Owner

saimn commented Sep 7, 2016

So, first option, the Mapquest plugin for Leaflet, which requires a key:
https://developer.mapquest.com/documentation/leaflet-plugins/maps/

@153957

This comment has been minimized.

153957 commented Oct 16, 2016

There are many alternative tile server providers, pick one (without an api key) you like:
https://leaflet-extras.github.io/leaflet-providers/preview/

saimn added a commit that referenced this issue Oct 23, 2016

@saimn

This comment has been minimized.

Owner

saimn commented Oct 23, 2016

Thanks @153957 , let's use leaflet-providers to give users the choice.

@saimn saimn closed this Oct 23, 2016

@saimn saimn added this to the 1.3.0 milestone Oct 23, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment