As stated here
http://devblog.mapquest.com/2016/06/15/modernization-of-mapquest-results...
we need to load the API in OL

Provide configuration options in MapQuest sources to enter a MapQuest API key, similar to the way we do it in the Google sources.

We may also want to change the default map that is displayed in /admin/structure/openlayers to something other than MapQuest - because an API key will not be entered automatically.

See attached screenshot of the default map without an API key. We can't have that be the first thing people see in this module.

CommentFileSizeAuthor
#2 Screenshot from 2016-07-12 14:33:08.png402.76 KBm.stenta

Comments

cimo75 created an issue. See original summary.

m.stenta’s picture

m.stenta
he/him
Primary language English
commented
Title: Mapquest direct tile access july 11 » Provide MapQuest API configuration
Component: Code » OL UI
Category: Bug report » Feature request
Priority: Critical » Normal
Issue summary: View changes
StatusFileSize
new Screenshot from 2016-07-12 14:33:08.png402.76 KB
m.stenta’s picture

m.stenta
he/him
Primary language English
commented
Related issues: +#2764999: Use OpenStreetMap for default UI map

Created a separate related issue: #2764999: Use OpenStreetMap for default UI map

mikestratton’s picture

mikestratton commented
Category: Feature request » Bug report
Priority: Normal » Critical

Thousands of systems have become partially or completely unusable as a result of Mapquests change. I have updated this to a Bug with Critical status.

pol’s picture

pol
the/that
Location Brussels
commented

Hi,

We (dev) are not responsible for this [INSERT_ADJECTIVE_HERE] change from MapQuest.

Support for MapQuest will be removed from the module soon until further notice, see changelog here.

I'm aware that this is a critical situation for everyone using those tiles. Have you another idea in mind ?

mikestratton’s picture

mikestratton commented

Hello Pol,

Thanks for all your hard work.

This was an [INSERT_MULTIPLE_ADJECTIVES_HERE] horrible change from MapQuest. I agree with the idea that support for MapQuest should be removed.

This presents an even bigger problem for those using Cartaro as part of there installation, as Cartaro is stuck on OL v2. Cartaro also has no plan to upgrade until maybe the end of this year. I placed a lot of weight in a (geops) project that is not even mildly supported.

Any chance that you can make the removal for support of MapQuest retro back to OL v2? Please and thank you? If you can't, maybe I will try my hand at applying a patch based off of the changelog you listed.

They are making it so that every little click, map drag, partial render, etc., etc. is counted as a transaction. I can see a half dozen intense users of any GIS system wiping out 10,000 transactions in a day or even a few hours.

I was working on a release of a custom GIS app for later today ... until mapquest [INSERT_MULTIPLE_ADJECTIVES_HERE] decided to make the change.