WhooTS is a small and simple wms to tiles proxy / redirect system.
Essentially it enables the use of WMS in applications that only accept Tiles (google / Openstreetmap scheme) – WMS is now in Potlatch!
How to use it?
http://whoots.mapwarper.net/tms/z/x/y/{layer}/http://path.to.wms.server
Example:
a mapwarper map:
http://whoots.mapwarper.net/tms/!/!/!/2013/http://warper.geothings. net/maps/wms/2013
viewing it in Potlatch, the OpenStreetMap editor:
Using a mapserver WMS request, with one layer:
http://hypercube.telascience.org/cgi-bin/mapserv?map=/home/ortelius/ haiti/haiti.map&request=getMap&service=wms&version=1.1.1&format=image/jpeg &srs=epsg:4326&exceptions=application/vnd.ogc.se_inimage&layers=HAITI&
Goes to:
Caveats:
Its’s quite simple, does not do any caching, it just redirects a tile url to an equivalent WMS request. It would only work with WMS servers that accept EPSG:900913 projections, and at the moment, it outputs OSM / Google Tile scheme, not a proper TMS tile scheme.
It’s written in Ruby with the Sinatra micro web application framework. The code is available on GitHub too. http://github.com/timwaters/whoots
Officially, there is no EPSG:900913, and EPSG:3857 should be used for the popular web mapping projecton (a.k.a. spherical mercator).
At least mapserver-based WMS-s which work nominally in EPSG:4326 (a.k.ka WGS-84, very popular among WMS-s) can do internal implicit reprojection to EPSG:3857, if you just make request in decimal degrees. Actually your telascience mapserver request relays on this feature.
Pingback: weekly 252 – 12.05.–18.05.2015 | weekly – semanario – hebdo – săptămânal – haftalık – 週刊 – týdeník – edisi
Hi Tim,
Interesting. Could we use similar approach in following scenario:
MapQuest used to have a Tile service which has been deprecated. Now they only have a Static API which expects Lat, Lng instead of ${x} ${y}. Could we make a middleware which exposes TMS interface and uses MapQuest Static API internally ?