Only map levels up to 11 are properly retrieved from MapQuest for some locations about rviz_satellite HOT 5 CLOSED

Fun stuff, just tested in simulation and now get this:

It seems this is a bigger problem with MapQuest that could require some major changes.

from rviz_satellite.

Here's the blog post: http://devblog.mapquest.com/2016/06/15/modernization-of-mapquest-results-in-changes-to-open-tile-access/

tl:dr: One needs to register now to still be able to access tiles. 15000 monthly transactions are free.

from rviz_satellite.

These tile URLs worked as a quick fix for me (not satellite, but better than nothing):
http://tile.stamen.com/watercolor/{z}/{x}/{y}.jpg
http://tile.stamen.com/toner/{z}/{x}/{y}.png
http://a.tile.thunderforest.com/landscape/{z}/{x}/{y}.png

from rviz_satellite.

Did a quick investigation into this. Seems like even w/ the MapQuest key, the old tile URL does not work anymore. They do still provide tile access through the Leaflet/JavaScript API, documented here.

However, upon further inspection, the access point for their JavaScript API (listed as MapQuest JavaScript SDK) simply converts the key into a MapBox access token and returns a wrapper script that queries MapBox. Apparently MapBox now backs all the tile requests for MapQuest.

No point in going through MapQuest anymore. With a MapBox account (mine is currently free trial) I am able to access the satellite imagery w/ the URL:

http://a.tiles.mapbox.com/v4/mapbox.satellite/{z}/{x}/{y}.jpg?access_token=<TOKEN>

where <TOKEN> is my public access token, accessible from the API Access Tokens section of the account page.

Let me know if that works for you and we can update the documentation.

from rviz_satellite.

Thanks for the update! I can confirm things work for me using the URL with the access token at the end.

from rviz_satellite.