Note that the world is projected using the Mercator projection (see Wikipedia) with the left (west) side of the map corresponding to -180 degrees of longitude and the right (east) side of the map corresponding to 180 degrees of longitude. See the graphic below or the map tiler site for exact values.) We don’t use Latitude/Longitude though, because it is unprojected, and this will cause map distortions.įrom the google api docs for TileOverlay: (roughly -20037508m to 20037508m in both directions using Web Mercator. We know the bounds of the entire map which is square. The x, y, zoom parameters provide us enough information to figure this out, but we have to do a little bit of math. It seems simple enough, but the problem is that the signature of getTileUrl which is getTileUrl(int x, int y, int zoom) provides tile indexes (x and y) and a zoom level, but WMS requires that we provide a bounding box (xmin, ymin, xmax, ymax) in the request URL. We override this method to compose the right URL, and the Android mapping SDK does the rest for us. The API to UrlTileProvider is its getTileUrl method. The v2 API provides the UrlTileProvider class, a partial implementation of the TileProvider class which allows developers to pull in map tiles by composing a URL string. Release Spring 2013) showing WMS technique described in the article. After downloading the google play SDK and setting up the library make sure you can view the TileOverlayDemo ($ANDROID_SDK_ROOT/extras/google/google_play_services/samples/maps) This article assumes a working v2 setup with the sample code running without error. With Google’s v2 mapping API for android, it is now relatively straightforward to build Android apps that combine WMS tiles with Google’s base maps and other data such as vector shapes and map markers.įor basic getting started info for v2 Maps, see the Google Developer’s site for the v2 API. In the past, this data has been consumed by web applications using a client library such as Leaflet or OpenLayers. Some set of geo-referenced data, typically shape files or data stored in a PostGIS database, are returned as raster map tiles. WMS is used to serve map tiles over HTTP by back end frameworks like GeoServer. It is intended as a reference to help someone trying to get WMS tiles (IE from GeoServer) onto an Android map. This brief article documents some early exploration into using WMS (Web Map Service) with the new Google Maps V2 API. Implemented Using a Google Maps Android API v2, TileLayer Intro

Get the right wms url from geoserver