Mapquest has made changes to their API for Open Data

[Stefan-v-Oudenaarden]

Due to changes made by mapquest to their licensing structure and API the mapquest geocoding is currently broken. Requests run into a key unauthorized for request page.

See here for information on the license change: http://devblog.mapquest.com/2014/11/17/are-you-a-community-edition-licensed-data-user/

[Stefan-v-Oudenaarden]

Since no response is forthcoming I'm just going to add that you can force the mapquest geocoder to use the open data api manually which is a fine solution for now.

UseOSM = true;

[chadly]

Thanks for reporting this and the workaround. I haven't had time to look into the changes to their API yet. If some kind soul would like to send a pull request to fix it, I would be grateful.

[ronin1]

I will attempt to fix this since I was the original contributor for OSM & MapQuest :) haven't had the need to use this lib in a while. Hopefully I get sometimes in the next week or so.

[AdalyatNazirov]

Could you describe the problem?
It seems to me that MapQuest Commercial Api working fine, but not OSM. I've set UseOSM = true and got 4 tests failed, when MapQuest Commercial Api passed them (Just got an API Key with Free Plan).

[NickStrupat]

Is this issue relevant with version 4.0.0?

[vdachev]

Is this issue relevant with version 4.0.0?

I've tested geocoding with MapQuest's API today and it seems to work. However, I filed an issue with not getting correct results when using non-ASCII characters.