Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a set of tiles that I was given via disk (So no way to recreate them, they are already generated/cached). There is a clear pattern/style to the naming of the tiles (zoomLevel-x-y.gif). The bounds are actually configured the same way that "Google" organizes their tiles(from top left, not bottom-left. ugh). More information on this specific format and how I request them in OpenLayers can be found

My question comes into play as I want to provide these tiles via Geoserver. I have a client who is only able to access data and layers via wms calls (don't ask). The file system fetching that openlayers uses won't work for him (as well as being able to use a top-left origin instead of bottom-right).

So, from my limited knowledge of geoserver, it seems like it should be able to front these tiles to the users via a WMS server, where it takes the request, translates it to a file path/url, and goes from there. Sort of a proxy functionality. Am I completly off base here? And if not, how can I even start to go about this?

edited for clarity, and a bit more background information


share|improve this question

This is denfinately not out-of-the-box geoserver material. One thought is to get GeoWebCache to read your tiles, and then do some magic with the "recombine and rescale" feature:

Or, you could try asking on the geoserver mailinglist.

share|improve this answer
Not exactly an answer, but at least a point in the correct direction. If no other answer is submitted within a week, I'll accept this as the answer. – J Jones May 3 '12 at 12:48

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.