[Geoserver-users] ProjectionException: Latitude is too close to a pole when seeding GeoWebCache

GeoServer GeoServer User
1

(Forgive me if my terminology is a bit off - I’m quite new to using GeoServer and new to GIS).

When attempting to seed a layer in GeoWebCache (the version built into GeoServer 2.5.2), I’m getting the following:

ProjectionException: Latitude 97 01.8’S is too close to a pole.

This is part of a rather large list of exceptions that I get when I attempt to seed a layer. (I’d be glad to post the entire dump, in case anyone wants to see it).

I’m working on a project with 2,000+ layers, and we are trying to get better performance. We figured one of the best ways of doing this is to get GeoWebCache working. The particular exception I’m seeing happens when attempting to seed a layer with the EPSG:4326 Grid Set. Even if I set a bounding box and restrict the Zoom Start to 10 and Zoom Stop to 12, I still see this exception in the GeoServer log. If I attempt to seed the same layer with the EPSG:900913 Grid Set, it seems to successfully seed, as indicated in the GeoServer log.

I’ve done a bit of searching around on what is causing this, but haven’t been able to nail it down. The layers that I’m working with do not contain any data near the poles, and are fairly small geographically - perhaps several square miles each.

Does anyone have an idea of what might be causing this, and how I can go about correcting it?

Also, on the topic of performance, I’m wondering what else I can be doing. I’ve been through the GeoServer documentation and have checked the following:

  • We are using the Oracle 7 JRE
  • I’ve attempted to get JAI working, but it looks like it hasn’t been updated since 2006 (unless the dates here are wrong: http://download.java.net/media/jai-imageio/builds/release/1.1/), and doesn’t play well with Java 7.
  • We’ve set the JVM to use as much memory as we dare, by setting -Xmx and -Xms parameters in Java.
  • We’ve set logging to SPEED.

Other than that, it seems like GeoWebCache is the next thing we can do to get more performance, but then we ran into the too close to a pole" issue. If anyone has any idea how to fix this, or any other thoughts on how we can get more performance out of GeoServer, it would be much appreciated.

  • Joel