Support for MapQuest's Licensed Data APIs

[jasonbouffard]

The MapQuest provider only provides access to the the Open Data APIs via the class constants. I suggest we update the MapQuest provider with a Open/Licensed switch in the constructor. The only difference would be the ENDPOINT_URL constants used to execute the queries. One provider could support both Open and Licensed APIs. The other option would be to create a new MapQuestLicensed provider in order to differentiate.

http://developer.mapquest.com/web/products/open
http://developer.mapquest.com/web/products
http://developer.mapquest.com/web/tools/getting-started/platform/licensed-vs-open

[toin0u]

Why not ?

Open data:

• http://developer.mapquest.com/web/products/open/geocoding-service
• http://open.mapquestapi.com/geocoding/

Licensed data:

• http://developer.mapquest.com/web/products/dev-services/geocoding-ws
• http://www.mapquestapi.com/geocoding/

[willdurand]

If both are the same, then we could introduce a new optional parameter to support licensed API.

What does the licensed API imply? Paying a license? What is the gain?

[jasonbouffard]

The open data is sourced from OSM. The licensed data is MapQuest's proprietary data. And yes there is a payment involved with the licensed data. See http://developer.mapquest.com/web/tools/getting-started/platform/licensed-vs-open for more information.

[willdurand]

alright. So I'd go for an optional parameter.